Skip to content

SysManager 1.52.97

Choose a tag to compare

@github-actions github-actions released this 10 Jul 23:26
· 691 commits to main since this release
6fb3f01

What's new for you

The Performance tab is now safer to click around in. Its actions — switching power plan, reducing visual effects, Game Mode, Xbox Game Bar, GPU mode, processor state, plus Restore All, Trim RAM, Create Restore Point and Toggle Hibernation — used to be able to run on top of each other if you clicked quickly. In a rare timing case that could scramble the safety snapshot the app keeps so it can undo your changes. Now only one of these runs at a time: if something is already working, the tab tells you which one and asks you to wait a moment, and nothing on your system is touched until it's your turn. Your ability to Restore All back to the original settings is protected.

Nothing you do changes on the outside — same buttons, same one-click undo, just no way for two changes to collide.


[1.52.97] - 2026-07-11

Fixed

  • The Performance tab's system-mutating actions weren't serialized against each other, so "Restore All" could run while an "Apply" was still in flight and corrupt the reversible snapshot. Every Apply command (power plan, visual effects, Game Mode, Xbox Game Bar, GPU, processor state) plus Restore All, Trim RAM, Create Restore Point and Toggle Hibernation is async and awaits real system work (registry writes, powercfg, EmptyWorkingSet across all processes). Nothing prevented a second command from starting mid-flight: the snapshot's own SemaphoreSlim only guards the load-modify of the _snapshot field, not the full apply→revert sequence. In the worst case, pressing Restore All while an Apply's registry write was still running let Restore All null _snapshot and delete the persisted baseline, leaving a tweak applied with nothing left to revert it (and other tabs that mutate the same system state — Tweaks, Cleanup's SFC/DISM — could interleave too). Every one of these ten commands now acquires the app-wide OperationLockService SystemModification lock (the same lock SFC/DISM and the Environment Variables editor already use) right after its confirmation dialog; if another system-modification operation is running, the command reports "Cannot start — is already running." and bails before touching the system. Toggle-based commands re-sync their toggle from the live profile on that early return so the UI doesn't show a change that wasn't applied.

Verify the download

Get-FileHash .\SysManager-v1.52.97.exe -Algorithm SHA256

Expected SHA256: 0BF2F11D2086A23F3F2432E2B7F62AE77556E827A76E9F4FDF695CA900FB4A81