SysManager 1.131.3 다운로드

[1.131.3] - 2026-10-27
Release builds are now checked the way you actually start SysManager — without administrator rights — and a
rebuild can no longer quietly replace a download with different bytes.
Fixed
- The release gate only ever started SysManager as an administrator. The check that proves a published
build runs launched it with the build machine's own administrator rights, and start-up takes different code
without them — temperatures, PowerShell and parts of the main window all behave differently. A fault that
only happened on a normal double-click, which is how everyone reading this starts it, passed that check
every time. Each release is now started both ways, and a fault in the ordinary start stops it from being
published.
- A build was publicly vouched for before the last check that could still reject it. The signed
provenance record — the one gh attestation verify reads — was created before the step that starts the exe
and compares the version it reports. A build that step refused already had a public record claiming it was
genuine, for a file that never shipped. Nothing is vouched for now until every check has passed.
- Rebuilding a release could change the file under the same download link. The exact .NET build tools were
not pinned, so a release rebuilt on a later day could embed a newer runtime and produce a different file —
replacing the published download while the Windows Package Manager entry still carried the first file's
checksum. Anyone who had saved that checksum, which the README suggests doing, would see a mismatch they
could not explain. The build tools are now pinned exactly, and a rebuild that produces different bytes is
refused rather than published.
- The release page promised more privacy than the README does. Both say SysManager sends nothing anywhere
unless asked, but only the README added that two checks do run on their own at start-up — the update check
and the app-updates alert, either of which can be switched off in About. The release page, where people
decide whether to download at all, left that out. It now says the same thing.
Verify the download
Get-FileHash .\SysManager-v1.131.3.exe -Algorithm SHA256
Expected SHA256: 6FAD585C19A130D8805713A1B569DD3A046EB3337FCA9CC5343D55B69B5AEA20
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.3.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.3.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.