Guides and troubleshooting

Warning: configuration file is not writable

This appears when the GUI auto-starts as a limited user and cannot write the shared config without admin rights.

1. 1

   Acknowledge safely You can check "Do not ask me again." Choosing Yes prompts for admin credentials on each start. Choosing No skips the prompt but blocks config edits until you run with admin rights.

2. 2

   Run as admin when you need to edit Use Main → Elevate Now (product menu) before changing rules if you run as a standard user.

3. 3

   Or move config paths Options → General → Configure Startup… can point config and log paths under your user directory. Avoid user-only paths on multi-user systems.

4. 4

   On Terminal / RDS servers Stop auto-starting the GUI for all users. Process Governor still enforces rules. Open the GUI only for admins when needed.

CPU affinity on Easy Anti-Cheat games

EAC blocks direct access to protected game processes. Affinity and priority can still be applied indirectly.

1. 1

   Put affinity on the launcher Create an Always CPU affinity rule on Steam.exe (or the relevant launcher). Child game processes inherit that setting.

2. 2

   Use Enforce By Registry for priorities Registry-enforced priority applies at process creation and can work when the process is otherwise inaccessible.

3. 3

   Avoid system-wide CPU Sets unless needed System Reserved CPU Sets affect the entire machine and are less precise than per-process rules.

Bitsum states Process Lasso does not cause game bans and does not read process memory. Related: FAQ on bans.

Core utilization graphs are blank

1. 1

   Confirm View menu. Make sure core graphs are enabled under View.

2. 2

   Repair performance counters. From an administrative Command Prompt, run lodctr.exe /R then restart Windows.

3. 3

   Re-open Process Lasso and check the main graph and node meters again.

Antivirus warnings and repeated scans

Because Process Lasso inspects and adjusts other processes, AV vendors sometimes classify it as suspicious. Malwarebytes has historically logged false positives on Governor and update packages. Avast users have reported aggressive rescans of processlasso.exe.

1. 1

   Confirm you installed a build whose version and SHA256 match the download page.

2. 2

   Restore quarantined files if they were known-good Bitsum binaries.

3. 3

   Add the Process Lasso installation folder (and processlasso.exe / processgovernor.exe) to your AV exclusions list.

4. 4

   If scans still thrash on every probe, exclude by process name patterns your AV supports for execute-path cases.

Rules keep disappearing (Forced Mode)

Some apps reset their own CPU affinity or priority. By default Process Lasso applies rules once at process creation (and when config changes) and may defer when the process fights back.

1. 1

   Open Options and enable Forced Mode (near the bottom of the Options menu).

2. 2

   Process Lasso will continuously re-apply your rules. Overhead is described as insignificant.

I do not see a performance boost

1. 1

   Check expectations. ProBalance acts only when needed. Idle or lightly loaded PCs will show little difference.

2. 2

   Confirm the load is CPU-bound. Disk and I/O waits are outside ProBalance's main job.

3. 3

   Use the CPUEater demo (or recreate a busy CPU loop) to feel ProBalance under deliberate stress.

4. 4

   Separate automation features. Affinities, Watchdog, and limiters only help when you configured them for a real need.

Best practices for ProBalance and real-time apps

• Leave ProBalance enabled. Defaults are the most tested path for most users.
• Do not rank every process by hand. Adjust only the ones you care about.
• For audio and real-time work, keep ProBalance on and Induce Performance Mode on your DAW processes.
• ProBalance already ignores many non-normal priority processes (common for audio apps).
• Exclude a process only if you have evidence ProBalance intervened incorrectly.