Skip to content

IFEO Manager manages advanced launch parameters for selected executable files: debugger, global flags, mitigation options, silent process exit monitoring, dump creation, priority and affinity.

This is an expert diagnostic tool. An incorrect setting can completely block the launch of the selected program or change its behavior until manual recovery.

The “Show IFEO Manager” card is enabled on the app’s “Settings” page. Open Tools → IFEO Manager; the search is performed by .exe name, and the “Hide default exe” filter removes system processes from the list. For each file, the following is configured:

Section What it does
Debugger Replaces the process launch with the specified command; there is a “Block launch” preset
GlobalFlag Diagnostic flags: verbose loader log, heap checking, stacks and other checks for the selected .exe only
Mitigation Options DEP, ASLR, CFG and other mitigation mechanisms; the “Audit only” mode checks the policy without blocking
Silent Process Exit Exit monitoring: “Enable monitoring”, dump folder, timeout and reaction — a notification or a command launch on exit
Priorities Windows priority class and affinity for the process launch

The “Preview changes” button shows “Before” and “After” prior to applying.

  1. Launch the crashing application and find out the exact name of its process, for example via Task Manager.
  2. In IFEO Manager, find this .exe by search; select exactly it, not the launcher and not a system process.
  3. In the Silent Process Exit section, enable “Enable monitoring” and specify the “Dump folder”.
  4. Check the free space on the disk with this folder: dumps of heavy applications take gigabytes.
  5. Launch the application and wait for the monitoring to trigger on exit.
  6. Analyze the dump, then remove the setting (see below).

How to completely clear the settings of one .exe

Section titled “How to completely clear the settings of one .exe”
  1. Select the entry of the required .exe in the list.
  2. Open “Preview changes” and make sure which parameters are active.
  3. Click delete configuration and confirm: the tool will report “Entry deleted”.
  4. Launch the application and confirm that it starts as it did before diagnostics.

For individual actions, a rollback is available with the message “Previous state restored”.

Do not assign a random debugger and do not apply parameters to critical processes of Windows logon, shell, security or update. Aggressive heap checking flags greatly slow down the process. Do not publish personal data that could have ended up in the dump from the process memory.

Last checked: 2026-09-19.