Lataa SysManager 1.127.4

[1.127.4] - 2026-10-09
Settings Watchdog's Restore changed now says which settings it cannot put back, and waits while Privacy & Telemetry
is changing the same settings (#2594, #2595).
Fixed
- Settings Watchdog: a setting that was not set when you saved the baseline is no longer reported as a failed
write. Putting "Not set" back would mean deleting the value, which Restore changed never does, so it never wrote
one. It was still counted in the confirmation, and the result said it "could not be written (try running as
administrator)", which running as administrator does not change. Now the confirmation and the result say it is
left as it is, the status line says how many of the changes Restore cannot put back, and Restore changed is off
when that is all of them. Running as administrator is suggested only when a write was refused in a session that is
not elevated already.
- Settings Watchdog: Restore changed waits for other changes to Windows settings. Several of the settings it
watches are ones Privacy & Telemetry writes, and Privacy & Telemetry's Apply first waits for a restore point. A
Restore changed in that wait was written over a moment later, so each tab could show a state that was no longer
true. Restore changed now takes the same lock as Apply: while another change is at work it says "Cannot start —
is already running" and writes nothing.
- Both had been so since Settings Watchdog arrived in 1.48.0.
Verify the download
Get-FileHash .\SysManager-v1.127.4.exe -Algorithm SHA256
Expected SHA256: 2B4929679C0BC10EAAED5BBEDF7030BACDE875FBA9C9B59C727EC2EC063B5EAC
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.127.4.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.127.4.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.