SysManager 1.88.4

[1.88.4] - 2026-09-10

The Process Manager opens straight away again. Checking who signed a program takes Windows about a
fortieth of a second, which is nothing once and about four seconds across everything running — and the
tab was doing all of it before showing you anything, on the one page you open because something is
already wrong. The list now appears first and the Signature column fills in behind it over the next
couple of seconds. Same answers, and you can read, sort and search the list while they arrive.

Fixed

• Opening the tab no longer waits for the signature checks. The list is on screen in well under a
  second instead of after three and a half to four; the badges then appear in small groups rather than
  all at once at the end.
• Refreshing while the badges are still arriving no longer starts the work over. A program that starts
  while the checking is still going is picked up by the pass already running.
• Leaving the tab abandons any checking still outstanding, rather than carrying on for a list nobody is
  looking at.
• The per-second refresh is unaffected, as it was before: only programs that have just started need
  checking, so a routine refresh does no signature work at all.

---

Verify the download

Get-FileHash .\SysManager-v1.88.4.exe -Algorithm SHA256

Expected SHA256: CAC19733D61377B800BFFDA3777161914603D9D9588F2C1FF7C239B0212BEB6A

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.4.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.4.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.