Last ned SysManager 1.130.20

[1.130.20] - 2026-10-20
Deep Cleanup deletes exactly what its confirmation listed, and Clean selected stays off while a scan runs.
Fixed
- Deep Cleanup could clean a category its confirmation never listed. Clean selected stayed on while a scan ran,
and the confirmation stays open while SysManager keeps working. A scan that finished meanwhile replaced the list,
and the clean then ran over the new one, so a category that was empty when the confirmation was shown, and had
filled since, was ticked and cleaned without being named. The Recycle Bin is the worst case: an empty bin starts
unticked since 1.130.8, so files deleted after the last scan went with it. The clean now deletes the categories
the confirmation listed, and Clean selected is off until the scan has finished. Since the confirmation was added
(1.19.4).
Verify the download
Get-FileHash .\SysManager-v1.130.20.exe -Algorithm SHA256
Expected SHA256: 107F10A1E412E9E7E2EA4178E2A5D7D1F245AE9CCC9B5CC5193FE7E8145C5F28
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.130.20.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.130.20.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.