Process Lasso is a Windows process scheduler and rule manager. It watches running programs, records their CPU activity, and can apply temporary or persistent scheduling decisions when a matching executable starts. These decisions can change priority, preferred processors, power behavior, or instance handling. Process Lasso does not make a slow processor faster and does not add memory; it decides how existing Windows resources compete when several programs want them at once.
ProBalance lowers offenders
ProBalance watches for a background process that consumes enough CPU to interfere with interactive work. When its conditions match, Process Lasso temporarily moves that process to a lower priority class. The process keeps running, and the original priority returns after the contention passes.
This is different from a CPU cap. A restrained job can still use the processor when higher-priority work does not need it. If ProBalance acts on a wanted workload, the log records the action and the process can receive an exclusion. Changing advanced thresholds before observing the default behavior can make the rule either silent or overly active.
Priorities are relative
A priority class changes which ready thread Windows favors during contention. Process Lasso can remember a priority rule for future launches. Raising one program does not reserve new CPU capacity; it pushes competing work behind that program.
Real-Time and High priorities can starve services or input work that the chosen program itself needs. The documented safer approach is to lower unimportant background work rather than raise everything considered important. A rule should solve a measured conflict, not decorate every process in the list.
Affinity limits cores
CPU affinity restricts a process to selected logical processors. This can keep a background job away from chosen cores or hold a program within one cache domain. It can also reduce the total compute available to that process.
Some games react badly when affinity changes during startup, so a persistent rule can wait before applying. Anti-cheat protection may block the change entirely. A rule shown in Process Lasso does not prove that a protected game accepted it; verify the active affinity after launch.
CPU Sets stay softer
CPU Sets express preferred processors without creating the hard boundary of affinity. Windows may schedule outside the set when thread load or power management requires it. This makes CPU Sets useful when the scheduler needs room to adapt.
The softness is also a limitation. A CPU Set cannot guarantee that a process never touches a reserved core. Use affinity when the hard restriction matters, and use CPU Sets when a preference is enough. Applying both without a plan makes the effective result harder to diagnose.
Performance changes power
Performance Mode can activate a chosen Windows power plan while a designated program runs. The setting can keep the processor from entering a more conservative profile during a game or time-sensitive task. When the inducing process closes, Process Lasso returns to the previous power behavior.
A higher-power plan can increase heat, fan noise, and battery use. It cannot fix a network delay or a storage bottleneck. Confirm that the selected executable actually starts Performance Mode rather than assigning the mode to a launcher that exits before the main process begins.
Efficiency needs care
Efficiency Mode tells Windows that a process is not time-critical and may run at lower precedence or on efficient cores. Process Lasso can persist that state for a named process. It can also force Efficiency Mode off when Windows classifies an important workload incorrectly.
Linking Efficiency Mode to every ProBalance restraint is heavier than the normal temporary priority reduction, so the option starts disabled. A background encoder may finish later after this change even though the desktop feels smoother. Measure completion time as well as foreground responsiveness.
Logs explain outcomes
The process list shows current state, while logs and Insights record ProBalance actions and rule activity. A program that never appears as restrained did not receive a ProBalance adjustment during the recorded period. This helps separate an assumed scheduling problem from an action the program actually took.
Rules match executable identities and can affect every future launch that matches. After an application updates or changes its process layout, an old rule may target only the launcher or nothing at all. Review persistent rules when software changes rather than accumulating abandoned exceptions.
