SysManager 1.88.1

[1.88.1] - 2026-09-10

The Event Log tab no longer collects an account identifier it never showed you. For every event it
read — up to five thousand at a time — it also picked up the Windows security identifier of the account
behind that event, and then did nothing with it: no column displayed it, no export included it, nothing
read it at all. Since the app is not going to show it, it should not be picking it up. Removed, along
with the tests that were quietly keeping it alive.

Fixed

• A per-event account SID is no longer read or held in memory. It was never displayed and never
  written to any file — the Event Log's CSV export lists its columns explicitly and this was not among
  them — so nothing left your PC before or after this change. It is simply data the app had no reason
  to be holding.
• The field also did not contain what its name said. It was labelled as a user name while holding a raw
  identifier like S-1-5-21-…, which would have needed translating before it meant anything to anyone
  reading it.

Changed

• A new build check fails if any model value is filled in and then displayed nowhere and read by
  nothing. That is this project's most persistent class of mistake — work done on every refresh and
  thrown away — and it had been caught by review rather than by the build. All 193 such values are now
  checked on every pull request.

---

Verify the download

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

Expected SHA256: FF7BA4DEDDABEE9D0445E053D0E9BE9C490D17DD41CF56A31E56DFE78AF354AA

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