Scarica SysManager 1.85.0 per Windows

[1.85.0] - 2026-09-09
The Startup Manager now tells you whether Windows can actually confirm who made each program that
runs at boot. The Publisher column beside it has always come from the file's own version
information — a label the program writes about itself, which anything can set to "Microsoft
Corporation" — so it looked like a trust badge with nothing behind it. The new Signature column
checks the file's certificate instead, and says "Verified", "Unsigned", or "Check failed" in as many
words.
Added
- A Signature column in the Startup Manager, checked against the file's certificate with the same
chain validation the in-app updater uses. Hovering it explains the result in a sentence — "Windows
can confirm this really comes from Google LLC" — rather than leaving you to interpret a badge.
- Unsigned is grey and says so kindly. Most small utilities are unsigned, and so is SysManager
itself, so a warning colour on all of them would turn the column into noise you learn to ignore.
Amber is kept for a file that is signed and whose signature does not hold up, which is the one
case here worth a second look — and even then the label reads "Check failed" rather than accusing
the program, because an out-of-date certificate store on your PC produces the same result.
- Entries whose command does not point at a readable file get no badge at all, instead of a grey
verdict on a program nothing was able to inspect.
- The column sorts, so you can bring everything unverified to the top.
Changed
- The signature check runs offline, against certificates already on your PC. Opening the tab
never waits on the network, and it behaves the same on a laptop with no connection. The trade is
deliberate: a certificate revoked in the last few days may still read as verified, which is the
right call for a column that informs and the wrong one for the update check, where the same code
still verifies online.
Verify the download
Get-FileHash .\SysManager-v1.85.0.exe -Algorithm SHA256
Expected SHA256: 0DA74A133B848E1E35FE120FAB86BBA4C6EA16E2740EE7420923BF809E19DF72
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. 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.85.0.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.85.0.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.