Lataa SysManager 1.88.0

[1.88.0] - 2026-09-10
The Process Manager now tells you whether Windows can confirm who made each running program.
The Safety column beside it recognises a process by its name, which is the thing anything can copy:
a file called svchost.exe sitting in your downloads folder gets the same reassuring label as the
real one. The new Signature column asks the file itself, reading the certificate inside it, and says
"Verified", "Unsigned", or "Check failed" in as many words. It is the same question the Startup
Manager already answers, now on the tab where you go looking when something is eating your CPU.
Added
- A Signature column in the Process Manager, read from the running program's own certificate
rather than from anything it says about itself. Hovering explains the result in a sentence —
"Windows can confirm this really comes from Google LLC" — instead of leaving you to interpret a
colour.
- Unsigned is grey and says so kindly, exactly as on the Startup Manager: most ordinary programs
are unsigned, and so is SysManager, so a warning colour on all of them would turn the column into
noise. Amber is kept for a file that is signed and whose signature does not hold up.
- A process whose file Windows will not let us read gets no badge at all — that is most system
processes unless you run as administrator. Nothing was checked, so nothing is claimed.
- The check costs the tab nothing on an ordinary refresh. Only processes that have just appeared are
looked at, and several processes from one program are answered once, so a browser running as a
dozen processes is one check rather than twelve.
Changed
- The wording and the three states behind the Signature column now live in one place shared with the
Startup Manager, so the two tabs cannot end up describing the same certificate differently.
Verify the download
Get-FileHash .\SysManager-v1.88.0.exe -Algorithm SHA256
Expected SHA256: 82DCA188778DEFF45976E7DB8734E1734EA3783DF7DEDEB64F14BE5C36DCAA61
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.88.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.88.0.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.