SysManager 1.61.0

[1.61.0] - 2026-08-11

If an update ever leaves SysManager not working, you can now go back to the version you had
before with one click.

Added

• A way back from a bad update. Until now, installing an update replaced the old SysManager permanently. If a new version turned out to have a problem — and this app has shipped two releases that wouldn't start — your only option was to work out on your own that you needed to find an older release on GitHub and download it by hand. The app now keeps the version you were running before the last update, and the About tab shows a "Go back to the previous version" button when there's something to go back to. It asks first, explains that anything the newer version fixed will come back too, and leaves your settings alone. Only one older version is kept, so this doesn't quietly fill your disk with copies of the app — and if there's no room to keep one, the update still installs as normal rather than failing.

---

Verify the download

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

Expected SHA256: 90FFA0EDE6E40D03CCAE98A0F36268DF069689DBD0115CC6D601ACEDCB9EAEC0

This build is not code-signed, so Windows will warn on first launch. That is
expected for a small independent app: see what the warning says and what to
click.

Verify where this binary came from

This exe was built by GitHub Actions from this public source, and the build is
recorded in the Sigstore public transparency log. With the
GitHub CLI:

gh attestation verify .\SysManager-v1.61.0.exe --repo laurentiu021/SystemManager

That proves which commit and workflow produced this exact binary, something the
SHA256 file cannot show, since it is published alongside the exe it describes.
Each release also ships SysManager-v1.61.0.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.