SysManager 1.114.40

[1.114.40] - 2026-09-29

Settings Watchdog no longer replaces a saved baseline it could not read without asking. A baseline that
could not be read looked like no baseline at all, so saving a new one replaced it at once.

Fixed

• Settings Watchdog: a saved baseline that cannot be read is no longer replaced without a word. When the
  baseline file could not be read or did not parse, the tab said "No baseline yet", and Save baseline wrote
  over it without the confirmation an overwrite gets.
  • The tab now says the saved baseline could not be read, so nothing is compared with it.
  • Save baseline asks before replacing it, and keeps the old file as settings-baseline.json.unreadable
    rather than deleting it. If the old file cannot be moved aside, nothing is replaced, and the tab says the
    baseline was not saved.
  • A baseline file that Windows refuses to let SysManager read now counts as one that could not be read,
    instead of leaving the tab half-loaded.
    Present since Settings Watchdog was added in v1.48.0.

---

Verify the download

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

Expected SHA256: FF049388D596AF8ABDFFF2662E4BF1361CEFEAE031BA71CFCD13D63794F13F19

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