Lataa SysManager 1.130.50

[1.130.50] - 2026-10-21
Settings Watchdog and Camera/Mic/Location look again each time you open them, so a link that sends you to a
changed setting shows it, and "In use now" means now.
Fixed
- Settings Watchdog and Camera/Mic/Location showed what they read the first time. Both read when the tab was first
built and then only on Refresh, and SysManager can stay in the notification area for days. Undo Changes and Recent
Changes send you to Settings Watchdog because a watched setting changed, and the page still said "All watched
settings match your baseline." with Restore off. Camera/Mic/Location kept saying "In use now" for an app that had let
go of the camera long ago. Both look again each time you open them. Since 1.32.0 for Camera/Mic/Location and
1.48.0 for Settings Watchdog.
- Settings Watchdog's CSV said every change could be restored. Its "Can restore" column said "yes" for a setting
that was not set when the baseline was saved, which Restore does not put back. It says "no" for those now. Since
1.123.0.
Verify the download
Get-FileHash .\SysManager-v1.130.50.exe -Algorithm SHA256
Expected SHA256: 24BCB35EA490F6DC6AC72B9F3C05CBEF5D44B7AEA0FD9A8B3A715FBDE346C8C2
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.
Code signing is planned through the SignPath Foundation,
which provides free certificates to open-source projects, with signing performed by
SignPath.io. Until then, the SHA256 above and the build
attestation below are what establish that a download is the genuine build.
Code signing policy
This release is not code-signed. The team roles, release-approval process and
privacy policy required by the SignPath Foundation programme
are documented in advance under Code signing
policy. That
documentation is a prerequisite for applying, not evidence of a certificate. The
attribution line naming SignPath as the signing provider will appear here once a
certificate is actually issued.
This program will not transfer any information to other networked systems unless
specifically requested by the user or the person installing or operating it. Full
privacy policy.
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.130.50.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.130.50.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.