Lataa SysManager 1.56.13

[1.56.13] - 2026-08-04
Fixed
- Your Windows user name is now removed from every line of the diagnostic log. The app already had a helper for this, but only 15 of the 75 places that log a file path actually called it — so whether your account name ended up in the log depended on which part of the app happened to run into trouble. The removal now happens where the log is written, so it covers every existing message, every future one, and paths that appear inside error text (which no per-message fix could reach). Log files stay local and are never uploaded; this matters for a log you choose to share yourself, for example when reporting a problem.
Verify the download
Get-FileHash .\SysManager-v1.56.13.exe -Algorithm SHA256
Expected SHA256: 4CA29DAE9A324258AB69F0F392AA58ECD66D5FBFEC5728E71EC5800FCACE55A1
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.56.13.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.56.13.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.