Last ned SysManager 1.136.24

[1.136.24] - 2026-10-30
The diagnostic log keeps error messages whole again, and no longer lets a user name through
when two paths share a line.
Fixed
- Before writing a line to the diagnostic log, SysManager replaces the folder name after
C:\Users\ with [user]. It took everything after C:\Users\ up to the next backslash, so for a
path that ended at a user's folder, as in "Access to the path 'C:\Users\Bob' is denied.", it also
removed "is denied.", the error's name on the next line and the list of where it happened, which
are what a log you share for a bug report is for. When a line held two such paths, the first
replacement could run on into the second and take its drive letter, so the second user name was
written to the log as it was. Only the folder name is replaced now, every one of them, and the
rest of the line is kept. Your own folder name is matched exactly, so one with a space or an
apostrophe in it is replaced whole. Present since 0.17.0, and on every line of the log since
1.56.13.
Verify the download
Get-FileHash .\SysManager-v1.136.24.exe -Algorithm SHA256
Expected SHA256: AC085EF3BE0370F3319DF72C17CDFC03B2BC627C027FB24A7F0786605EA8375E
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.136.24.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.136.24.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.