SysManager 1.52.100

What's new for you

A safety fix for the App Blocker tab. App Blocker stops chosen programs from launching — and now it refuses to block SysManager itself. Previously, if you picked or typed SysManager's own name, blocking it would prevent the app from starting again and prevent you from unblocking it (since you need the app open to undo a block), leaving the Registry Editor as the only way out. That footgun is now closed, the same way boot-critical Windows processes were already protected.

---

[1.52.100] - 2026-07-11

Fixed

• App Blocker could block SysManager's own executable, making the app impossible to relaunch and impossible to unblock from within the app. BlockApp writes an IFEO Debugger redirection for any executable name that passes validation, and it already refuses a fixed set of boot-critical processes (winlogon.exe, lsass.exe, …) precisely because an IFEO block on those is unrecoverable — but SysManager's own executable was not protected. A user could block it trivially (the Browse button fills in the real file name of any picked .exe, or they could just type it), after which the next launch is redirected to the non-existent System32\SysManager_Blocked.exe and fails; because UnblockApp requires the app to be running, recovery then needs regedit — beyond the non-technical target user. BlockApp now refuses to block SysManager's own executable (resolved once from Environment.ProcessPath, matching both the dev name SysManager.exe and the released SysManager-vX.Y.Z.exe), enforced at the service trust boundary alongside the existing boot-critical guard.

---

Verify the download

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

Expected SHA256: F31A30E3BEEE162AB3BD995AA84A14CA2C04245F49929F9BD4E4B25B074A7922