SysManager 1.114.8

[1.114.8] - 2026-09-28

System Logs now reports the number of events it actually loaded. It used to under-count them, and said
"Loaded 0 events" when fewer than 50 matched.

Fixed

• System Logs: the "Loaded N events" line counts every event. The tab adds events to the list in batches
  of 50, and it decided whether it could add a batch straight away by comparing the current synchronization
  context with the one it captured when it was built. WPF creates a new context for every piece of work it
  runs, so after the first wait that comparison failed even on the UI thread, and every batch was queued. The
  status line was written before the last batch had been added, so it left out up to 49 events and said
  "Loaded 0 events" when fewer than 50 matched, while the rows then appeared. A load that stopped after fewer
  than 50 events could also cover the loaded rows with the "could not be opened" message. Batches are now
  added through the app's shared UI-thread helper, which asks the dispatcher instead, and a new check keeps
  such comparisons out of the code. The count has fallen short since the tab was added; batching the load in
  v0.48.32 made the shortfall up to 49 events.

---

Verify the download

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

Expected SHA256: D02442FC10503B1EA8F49B869E2F040FCBDF2F0E4F927BBF3F5BE5964C54A215

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