SysManager 1.114.3

[1.114.3] - 2026-09-25

The Dashboard's Quick Cleanup no longer runs at the same time as another cleanup. While a disk
operation is already under way it does not start, and it says which operation is running.

Fixed

• Dashboard: Quick Cleanup takes the same disk lock as the other cleaners. It deletes temp files with
  the same sweep as the Cleanup tab's temp clean and the Dashboard's own Quick Tune-Up. It was the only
  one of the three that ran without the lock, so it could start while either of them, Deep Cleanup or a
  disk scan was running. Two sweeps of the same folders then raced: each reported only the part it
  happened to delete, so neither "Freed …" figure was the real total. It now refuses to start while
  another disk operation is running, and the card names that operation. Present since the quick action
  was added in v1.17.0.

---

Verify the download

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

Expected SHA256: F7B089790989DEED5A45A8EAD33718C1F582A150CE5F45885041D155C3952A57

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