Sækja SysManager 1.131.6

[1.131.6] - 2026-10-28
File Shredder now refuses a compressed, sparse or encrypted file instead of overwriting bytes that
are not the ones actually holding the data.
Fixed
- A compressed, sparse or encrypted file was told apart from an ordinary one, without actually being
overwritten in the sense the confirmation promises. NTFS keeps a file like this in a form where
changed data goes to newly allocated disk clusters before the old ones are freed, rather than being
written over the existing bytes — the same reason a dedicated tool like Sysinternals' SDelete has to
find and overwrite those clusters directly. An ordinary write handle's passes landed on the new
clusters, while the original data stayed readable in the space the old ones occupied. The tab now
refuses a file like this outright, naming why, instead of reporting it as securely destroyed.
Verify the download
Get-FileHash .\SysManager-v1.131.6.exe -Algorithm SHA256
Expected SHA256: 4B54A4ADF97A1C2363C56F73B9FA7F0CF9ED293A06EC2FC4A5C21191160DAA4F
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. Two checks
run on their own when SysManager starts: the version check against the GitHub Releases
API, at most once a day, and the Dashboard's app-updates alert, which asks winget. The
About tab can switch off either. Everything else that uses the network runs only when you
use 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.131.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.131.6.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.