SysManager 1.61.1

[1.61.1] - 2026-08-11

Two more of the project's own tests can no longer touch your real settings: the Settings
Watchdog baseline and the dark-mode schedule.

Fixed

• Two more places where running the tests could overwrite your own files. This only affects people who build and test SysManager themselves, not normal use — but it is the same problem that was fixed for app icons in 1.60.1, and it is worth closing properly. The Settings Watchdog keeps a snapshot of your chosen Windows settings, and the Dark Mode scheduler keeps your on/off times; both were stored at a location the tests had no way to redirect, so a test that saved a baseline or a schedule wrote over yours. Both now accept a scratch folder, and every test uses one. The dark-mode schedule stays exactly where it has always been for real users, so nothing of yours moves.

---

Verify the download

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

Expected SHA256: D0207F74E8F4784BBED8EC12A851FE5B7F661E233B88388F42E560CFCB7FAEB3

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.1.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.1.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.