SysManager 1.58.1

[1.58.1] - 2026-08-10

Fixed

• A file SysManager is not allowed to read no longer breaks the job it was part of. Six places treated "the disk had a problem" and "Windows would not let me read this" as different things and only handled the first — so a single locked-down file could stop the whole operation instead of being skipped. The clearest case: exporting your settings gave up entirely if one of the files could not be read, losing the ones that could. Now the unreadable file is skipped and the rest still export. The same applies to checking a downloaded update, saving the Settings Watchdog baseline, reading the gaming-profile store, loading an app icon, and adding a file to the shredder list.

---

Verify the download

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

Expected SHA256: 8095E6C2E98BA5BE3DB3EF0D1345554952EBCD37F1C6C8F2A842F547EC77E07E

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.

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