SysManager 1.114.6

[1.114.6] - 2026-09-28

A saved Standby List Cleaner auto-purge now starts working as soon as SysManager opens. After a restart it
used to do nothing until you opened the Standby List Cleaner tab.

Fixed

• Standby List Cleaner: auto-purge watches from startup. The auto-purge switch and its threshold are
  remembered between sessions, so arming it once is meant to be enough. The poll that watches free memory
  and purges belongs to the tab, though, and SysManager builds a tab only when it is first opened, so after a
  restart a saved auto-purge did nothing until someone visited that tab. The tab is now built at startup, as
  the Dark Mode Scheduler already is for the same reason. It still polls only while auto-purge is on and
  SysManager runs as administrator. Present since v1.56.12, when auto-purge started being remembered.

---

Verify the download

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

Expected SHA256: BA7CA8A63CB40548196436B455DE85FCD4AF98EC12529D6E0D578D9D43CCF0FD

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