SysManager 1.131.11 download

[1.131.11] - 2026-10-28
Process Manager and Startup Manager now check where a "Windows" program actually runs from, not
just what it is named, before trusting it or telling you ending it is safe.
Fixed
- Process Manager's kill rules and the safety chip's tooltip both checked a process's name alone. A
program merely named svchost.exe, csrss.exe, MsMpEng.exe or any other name in the boot-critical
or high-consequence lists, running from a user's profile folder instead of the System folder, could
inherit the real one's refusal or warning — and conversely the chip's tooltip told every "Windows"
row that ending it "will not crash your PC", which was never true for the names Process Manager
actually refuses to end. Both now verify the running image's path under %SystemRoot% as well as its
name, through one shared ProcessCriticality helper read by the kill tiers, the tooltip, and
ProcessDescriptionService's database lookup, which now downgrades a "System" match to unrecognised
when the path disagrees. Startup Manager's enrichment passes the full path through the same check.
(#2792)
Verify the download
Get-FileHash .\SysManager-v1.131.11.exe -Algorithm SHA256
Expected SHA256: 565E8A0B8BB9022B8FE7D01399555ABDAE72808AB5D9852A8D8030B7CBE316D1
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.11.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.11.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.