SysManager 1.101.3

[1.101.3] - 2026-09-14

Deep Cleanup stops undoing the unticking it asks you to do. The scan summary says "untick anything you
want to keep" — and then scanning again, including by pressing F5, re-ticked all of it. Your choices now
survive a rescan. This is the same fault as the drive selection in the previous release, in the tab where
it mattered more, since here the ticks decide what gets deleted.

Fixed

• Unticking a cleanup category survives a rescan. Unticking every category survives too, rather than being
  read as "nothing chosen yet" and reset.
• Ticking a category that is not selected for you — a Windows.old folder, the blue-screen memory dumps —
  also survives, so choosing one of those is not undone by the next refresh.
• A category that was empty last time and has since filled up takes the default again. It was unticked by
  the scan rather than by you, so there was no choice of yours to keep.

---

Verify the download

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

Expected SHA256: AA8FAD8999067EF5539E2397B8A8BCC52505927DD18076F19EF6858D1B8CE992

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