ProcessX

On this page

ProcessX creates a separate profile for a game or program and applies it when the corresponding process starts. A profile can contain Windows priorities, logical processor selection, compatibility settings, and additional actions on launch and exit.

ProcessX eliminates the need to repeatedly configure processes manually via Task Manager. It reproduces the actions you selected every time the process starts. This does not provide an automatic FPS increase.

Why ProcessX was introduced

Changes made through Task Manager often apply only until the program is closed. On the next launch, you have to select the priority, affinity, or efficiency mode again. Along with the game, a launcher, recording application, browser, synchronization, and other background processes may start.

ProcessX saves a profile for a specific executable file and reacts to its launch and termination. This does not require a third-party driver or a constantly running ProcessX monitor in the background.

For new configurations, ProcessX is recommended instead of GameModeX. GameModeX remains running to accompany the gaming session and contains legacy Windows 10 features, whereas ProcessX is intended for standard process profiles on supported Windows 11.

How to add a profile

To add a process, choose one of the following methods:

select a game found among installed libraries;
select an already running process;
specify the executable file manually.

Automatic search may not find all executable files of a game. The launcher, the game itself, and its anti-cheat may use different processes. Before configuring, verify the path and name of the selected file.

What can be configured

Section	Capabilities
Process parameters	Disabling Fullscreen Optimizations and High DPI compatibility mode
Priorities	CPU, I/O operation, and memory page priorities; ready-made profiles for background CPU and I/O tasks
Affinity	All logical processors, one thread per physical core, skipping the first thread, only P- or E-cores on a hybrid CPU, manual selection
On launch	RAM cache cleanup, power plan selection, and a sequence of actions applied to other processes
On exit	Power plan selection, restoring the saved state, and other assigned actions
Reuse	Copying the entire profile or individual groups of settings between processes

Compatibility settings apply to the selected executable file. Disabling Fullscreen Optimizations should not be enabled automatically for every game. More details about the differences between display modes and measurement boundaries are provided in the FSO and FSE research.

Process priorities

Windows selects the next thread to execute based on its scheduling priority. Raising the priority class gives a thread an advantage over competing threads, but does not create additional CPU resources.

For most games, it is recommended to leave the values at “Default”. High priority can take processor time away from audio, input, drivers, and the game’s background components. Microsoft separately warns that REALTIME_PRIORITY_CLASS can preempt even critical system processes and make the mouse or the system unresponsive.

The “Background CPU tasks” and “Background I/O tasks” profiles are intended for rendering, compilation, encoding, downloads, backups, and synchronization when their impact on the active program needs to be reduced. They are not gaming presets.

Logical processor selection

Affinity limits the set of logical processors on which Windows can execute the program’s threads. ProcessX displays the topology of the available CPU and, when supported by the system, allows selecting P- and E-cores separately.

Without measurements, leave “All cores”. Microsoft generally recommends against limiting affinity manually: a rigid mask can prevent the scheduler from distributing threads efficiently and reduce performance. Limiting affinity can be useful for diagnostics or for a specific program with a confirmed issue, but the result cannot be transferred to another game or CPU model.

Some games first launch an intermediate process and create worker threads later. For such cases, ProcessX allows setting a delay before applying affinity. If the selected mask is not retained after launch, first try increasing the delay while keeping the selected set of cores.

Actions on launch and exit

For each profile, you can define a sequence of actions applied to other user processes:

launch or close a program;
suspend or resume a process;
apply efficiency mode;
change priorities and affinity;
switch the power plan;
restore the saved state when the main process exits.

When launching a program, you can specify a delay, arguments, and a minimized window. Before adding multiple actions, configure and test each one separately.

State restoration

Restoration must be configured separately: it is not added automatically to all actions. If changes are needed only while the game or program is running, add a restoration action on exit. Separately select the power plan that should be activated after termination.

Exit actions are executed only if Windows has registered the process termination and launched the ProcessX script. An unexpected computer shutdown, corruption of system components, or manual removal of service elements can prevent restoration. After such an event, check the active power plan and the state of the affected programs manually.

Efficiency mode

Efficiency mode is suitable for a background program that does not require maximum responsiveness. Windows uses QoS and power throttling to shift such work toward energy efficiency and reduce heat generation. Do not apply this mode to a game, capture application, audio processing, or any other latency-sensitive process without separate testing.

RAM cache cleanup

Before launch, you can clear the RAM cache as a separate action. Windows uses free memory to cache data, so after cleanup the game and the system may need to read it from the storage drive again. This can cause additional latency and stutters. More free memory does not by itself speed up the system.

Leave cleanup disabled unless tests confirm that it helps with your issue.

Security

By default, ProcessX restricts the selection of critical system processes. In normal mode, the most dangerous priority levels are unavailable. Other actions also need to be verified before applying.

Closing a process may result in the loss of unsaved data. After the specified timeout, the application may be terminated forcefully.
A suspended process stops executing until it is resumed. Do not suspend Windows components, drivers, anti-cheat software, or security software.
Do not close the launcher if the game uses it for authentication, updates, or network connectivity.
Do not assign the same actions to two profiles that may run simultaneously until you have verified their execution order.
After updating a game, check whether the executable file name and path have changed.

Antivirus warnings

ProcessX automatically responds to program launches and can manage other processes. Such behavior sometimes triggers heuristic analysis warnings from antivirus software.

Use only the official version of BoosterX. Do not disable your antivirus and do not add broad exclusions solely for ProcessX. If the official file is detected as a threat, update your antivirus definitions and send the detection name to BoosterX support for review.

Recommended first profile

Add a regular user application, not a system process.
Leave the priorities at their defaults and select all logical processors.
Add only one straightforward action, such as launching a helper program.
Start the main process and verify the result.
Close it normally and confirm that the on-close action was executed.
Only after that should you add priorities, affinity, or management of other processes.

Sources and limitations

This description is accurate as of the verification date. To determine whether FPS increased, latency decreased, and stuttering disappeared, test the profile on your own system.

Last verified: 2026-08-24.