SysManager 1.88.2

[1.88.2] - 2026-09-10

The Signature column was telling you almost every program on your PC had failed its check. It was
supposed to be the rare warning; instead it was the normal answer. On this machine it confirmed one
signed program out of forty-eight and put an amber "Check failed" on the other forty-seven — File
Explorer, Outlook, Windows Terminal, Windows Settings among them. All of those are properly signed by
Microsoft. The column now asks Windows for its verdict instead of working it out itself, and gets the
same answer you would see in a file's own Properties window: forty-six confirmed, and the one remaining
warning is a genuine expired certificate.

Fixed

• The Signature column now agrees with Windows. It uses the same check that sits behind the
  Digital Signatures tab in a file's Properties, so the two can no longer disagree — and if you
  want to double-check anything the column says, that dialog is the second opinion.
• Nothing is accused for being unreadable. A file the app cannot make sense of now reads as
  unsigned, because that is what Windows says about it. Previously our own reader failing to parse a
  file produced a warning about the file, which was blaming the wrong party.
• The warning colour is back to meaning what it says. On a normal PC it should now appear rarely, and
  when it does it is worth the look.
• No network request is made, on either tab. That was already the intent and the previous approach
  could not actually deliver it — a certificate check that cannot reach the internet also cannot
  finish, which is a large part of why every answer came back as a failure.

Known limitation, stated rather than left to be discovered

• Windows signs many of its own components through a separate catalogue file rather than inside the
  program, and that kind of signature is not read yet. Those show as Unsigned. It understates them
  instead of accusing them, and it is the next thing to fix on this column.

---

Verify the download

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

Expected SHA256: F99E3F6C25EC93830A8A6784AC6130AD3B6748117B94AF326E893C3E598DF720

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