Pakua SysManager 1.131.5

[1.131.5] - 2026-10-28
File Shredder no longer follows a link given to it directly, and a write error partway through an
overwrite no longer leaves a half-destroyed file behind.
Fixed
- A link given directly to File Shredder was followed through to its target. Shredding a folder
already refused a link at the folder's root, but a single file or shortcut selected directly had no
equivalent check: the overwrite passes landed on the link's target, the link itself was deleted, and
the real file was left behind truncated to zero bytes outside the location you actually selected. A
link is now refused outright, the same way a link folder already was.
- A write error partway through an overwrite (a full disk, a removed drive) left a half-overwritten
file under its original name. Once the first byte of a pass was replaced, the original data was
already gone — but a write failure after that point used to escape before the file was truncated and
removed, so what remained on disk was neither the original file nor a securely erased one, and a
folder shred reported it as "left in place" when it was, in fact, partly destroyed. The file is now
truncated and removed the same way a cancellation after the first byte already was, and File Shredder
says plainly that a write error stopped it rather than reporting the file as untouched.
Verify the download
Get-FileHash .\SysManager-v1.131.5.exe -Algorithm SHA256
Expected SHA256: F7A0942DA88098E2EBB03140DAA9110F66D82C208CF57B4A934FA413C357CED9
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.5.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.5.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.