I've always liked gaming on PC. Over time I kept noticing the
same thing every session: Windows, straight out of the box,
keeps a surprising amount running in the background that I
never asked for. Search indexing, telemetry, apps trying to
launch themselves, background sync, all of it competing for the
same CPU and disk a game needed right when it mattered most.
Most of the "optimizer" scripts I found online were the same
shape: a wall of registry tweaks and disabled services, no
explanation of why, no guarantee nothing you actually use breaks
along the way. So I built the version I actually wanted:
something that reads what's really slowing the machine down
before touching anything, and treats the aggressive part
(closing apps, pausing sync, pausing background services) as a
mode you switch on for a session, not a setting you're stuck
with afterwards.
That's nem0w-gameboost: diagnose first, keep the risky part
reversible, and never touch anything you didn't ask it to.
Why recovery comes first
Recovery snapshots are written before changes are applied. Game Mode tracks process priorities by PID and retains its recovery file after a partial failure, giving the next recovery attempt the information it still needs. Permanent optimizations and temporary session changes have separate recovery paths.