Lataa SysManager 1.70.1

[1.70.1] - 2026-08-25
Settings Watchdog could show a setting as unchanged while it had in fact changed. The page read your
live settings twice — once to work out what had drifted, once to fill in the list of what it watches —
and anything that moved between those two reads appeared in the list with its new value but without
being flagged. Now both come from a single read, so the two halves of the page can no longer disagree.
Fixed
- Settings Watchdog: the drift list and the watched list now come from one read. This was most
likely to bite in exactly the situation the tab exists for — the catalog watches settings that
Windows Update flips back underneath you, so a change arriving mid-refresh is the expected case,
not a rare one. The baseline file was also being loaded twice per refresh; now once.
Verify the download
Get-FileHash .\SysManager-v1.70.1.exe -Algorithm SHA256
Expected SHA256: FDC7F3AC20E5560FB7A96EE06643983680EBF0257C6AA87340724E523552AC98
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.70.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.70.1.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.