[PR #145] [CLOSED] Add a reversible script to turn Process Lasso off #159

New issue

Closed

opened 2026-10-15 20:53:54 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-15 20:53:54 +00:00

Owner

📋 Pull Request Information

Original PR: https://github.com/rehan-remade/universal-modder/pull/145
Author: @Naru6780
Created: 10/7/2026
Status: ❌ Closed

Base: main ← Head: add-process-lasso-disable-script

📝 Commits (1)

e904ea8 Add a reversible script to turn Process Lasso off

📊 Changes

4 files changed (+255 additions, -0 deletions)

View changed files

➕ Disable Process Lasso.zip (+0 -0)
➕ Disable Process Lasso/Disable-ProcessLasso.ps1 (+249 -0)
➕ Disable Process Lasso/Run-Disable-ProcessLasso.cmd (+3 -0)
➕ Disable Process Lasso/Run-Restore-ProcessLasso.cmd (+3 -0)

📄 Description

What: a standalone Windows script that turns Process Lasso off completely (and back on), written while tuning CPU use for 16 FINAL FANTASY XIV clients run side by side.

Why

Process Lasso's ProBalance lowers the priority of the busiest process (in a multibox setup, usually the client being played) and its affinity/CPU-set rules override per-client core placement done by another tool. Killing it in Task Manager is not enough: its core engine runs as a Windows service and restarts it.

What it does

Disable Process Lasso/Disable-ProcessLasso.ps1 finds Process Lasso from its install folder (uninstall registry keys, running processes, default paths), then:
- stops and disables its service (the ProcessGovernor core engine),
- removes the Run registry entries, moves Startup-folder shortcuts aside, disables its scheduled tasks,
- stops whatever is still running.
Nothing is uninstalled or deleted. Every change is recorded in C:\ProgramData\ProcessLasso-disabled\backup.json; -Restore puts it all back and starts Process Lasso again. -DryRun only lists what would change and needs no admin rights.
Run-Disable-ProcessLasso.cmd / Run-Restore-ProcessLasso.cmd are double-click wrappers (the script elevates itself). Disable Process Lasso.zip is the same folder packed for sending.

Reviewer notes

This is a utility, not a skill, field note or um command; it sits at the repo root as committed. If it's wanted, it probably belongs under examples/ or as a um win subcommand instead; happy to move it, or close this if it's out of scope for the toolkit.
The zip duplicates the folder; it can be dropped.

Checklist

uv run --with pytest pytest -q tests passes (code): 77 passed
um kb index regenerated (field notes): n/a, no field note
no game files, extracted assets, decompiled code dumps or secrets
nothing that cheats other players or bypasses anti-cheat / DRM / ownership checks
versions, verification and what was NOT verified are written down: verified on Windows 11 26200 with PowerShell 5.1 by parsing the script and running -DryRun and -Restore -DryRun on a PC without Process Lasso (both report nothing to do). Not verified against a real Process Lasso install: service and task names are matched by install path and name patterns, not a fixed list.
authored by (agent + model / human): Claude Code (Claude Opus 5.5) with @Naru6780

🤖 Generated with Claude Code

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/rehan-remade/universal-modder/pull/145 **Author:** [@Naru6780](https://github.com/Naru6780) **Created:** 10/7/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `add-process-lasso-disable-script` --- ### 📝 Commits (1) - [`e904ea8`](https://github.com/rehan-remade/universal-modder/commit/e904ea846b3adad9aa7bc2d6c8b0d0ebac21a570) Add a reversible script to turn Process Lasso off ### 📊 Changes **4 files changed** (+255 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `Disable Process Lasso.zip` (+0 -0) ➕ `Disable Process Lasso/Disable-ProcessLasso.ps1` (+249 -0) ➕ `Disable Process Lasso/Run-Disable-ProcessLasso.cmd` (+3 -0) ➕ `Disable Process Lasso/Run-Restore-ProcessLasso.cmd` (+3 -0) </details> ### 📄 Description **What:** a standalone Windows script that turns Process Lasso off completely (and back on), written while tuning CPU use for 16 FINAL FANTASY XIV clients run side by side. ### Why Process Lasso's ProBalance lowers the priority of the busiest process (in a multibox setup, usually the client being played) and its affinity/CPU-set rules override per-client core placement done by another tool. Killing it in Task Manager is not enough: its core engine runs as a Windows service and restarts it. ### What it does - `Disable Process Lasso/Disable-ProcessLasso.ps1` finds Process Lasso from its install folder (uninstall registry keys, running processes, default paths), then: - stops and disables its service (the ProcessGovernor core engine), - removes the Run registry entries, moves Startup-folder shortcuts aside, disables its scheduled tasks, - stops whatever is still running. - Nothing is uninstalled or deleted. Every change is recorded in `C:\ProgramData\ProcessLasso-disabled\backup.json`; `-Restore` puts it all back and starts Process Lasso again. `-DryRun` only lists what would change and needs no admin rights. - `Run-Disable-ProcessLasso.cmd` / `Run-Restore-ProcessLasso.cmd` are double-click wrappers (the script elevates itself). `Disable Process Lasso.zip` is the same folder packed for sending. ### Reviewer notes - This is a utility, not a skill, field note or `um` command; it sits at the repo root as committed. If it's wanted, it probably belongs under `examples/` or as a `um win` subcommand instead; happy to move it, or close this if it's out of scope for the toolkit. - The zip duplicates the folder; it can be dropped. **Checklist** - [x] `uv run --with pytest pytest -q tests` passes (code): 77 passed - [ ] `um kb index` regenerated (field notes): n/a, no field note - [x] no game files, extracted assets, decompiled code dumps or secrets - [x] nothing that cheats other players or bypasses anti-cheat / DRM / ownership checks - [x] versions, verification and what was NOT verified are written down: verified on Windows 11 26200 with PowerShell 5.1 by parsing the script and running `-DryRun` and `-Restore -DryRun` on a PC without Process Lasso (both report nothing to do). **Not verified against a real Process Lasso install**: service and task names are matched by install path and name patterns, not a fixed list. - [x] authored by (agent + model / human): Claude Code (Claude Opus 5.5) with @Naru6780 🤖 Generated with [Claude Code](https://claude.com/claude-code) --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

bsakaguchi

2026-10-15 20:53:54 +00:00