SysManager 1.75.16

[1.75.16] - 2026-09-01

File Shredder now tells you what it actually did. Before, a folder containing a shortcut to somewhere else
was reported as fully destroyed while it was still sitting on the disk, and when a file could not be shredded
the only thing shown was the word "Failed".

Fixed

• A folder holding a shortcut is no longer reported as destroyed. File Shredder deliberately refuses to
  follow a shortcut that points somewhere outside the folder you picked, because overwriting through one
  would destroy files you never selected. That refusal is right and has not changed. What was wrong is that
  nothing said so: the folder was reported as shredded, no note was written anywhere, and the folder stayed
  on the disk because the shortcut was still inside it. So you were told your files were gone while looking
  at the folder holding them. The shredder now says how many shortcuts it left alone and that the folder is
  still there. A folder with no shortcuts in it reads exactly as before, with nothing extra added.
• When a file cannot be shredded, the reason is now shown. The shredder already worked out a clear
  explanation for every file it had to leave behind — which ones they were, and why, whether locked by
  another program or sharing its contents with a file elsewhere on the disk. That explanation went only into
  the log file. On screen the file was marked "Failed" and nothing more, which for a tool whose entire job is
  destroying data beyond recovery leaves out the only part that matters: those files are still on your
  computer and still readable. The explanation now appears beside the summary at the bottom of the tab.

---

Verify the download

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

Expected SHA256: 859C1F8E2D2DAAC603342538C31B5C320AD33063EB1245F73DD9417F58F8EC81

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