SysManager 1.75.19

[1.75.19] - 2026-09-01

The Logs tab could get stuck loading forever, with one processor core pinned at full speed and the Refresh
button greyed out. It also loads faster now, and pressing Cancel says "Cancelled" instead of pretending the
list finished.

Fixed

• The Logs tab can no longer get stuck loading with a core at 100%. Windows event logs are a rolling
  buffer, so a busy log can move underneath a read that is already in progress. When that happened, SysManager
  retried the same failed read over and over with nothing in between: the tab stayed on "Loading events…"
  forever, Refresh stayed greyed out because it is disabled while loading, and one processor core sat at full
  speed until the tab was closed or Cancel was pressed. Retrying could never have worked — Windows does not
  move on to the next entry after that kind of failure — so SysManager now stops, keeps the events it already
  read, and says the list is incomplete.
• Pressing Cancel now says "Cancelled" instead of reporting a finished list. A cancelled load was
  reported as a completed one, so a list stopped halfway through was described as "Loaded 137 events" with
  nothing to indicate it was cut short. The same wrong message appeared when switching away from the tab
  mid-load.
• A partly-read log now says so. If a read stops early, the message under the list says how many events
  arrived and that the rest are missing, rather than presenting the shortened list as everything there was.

Changed

• The Logs tab loads faster and uses less memory, especially at the larger row counts. SysManager was
  building the raw technical XML for every single event as it loaded, although that panel only ever shows the
  one row you click. With the list set to 5000 rows that was 5000 pieces of work and 5000 stored blocks of
  text nobody looked at. It is now produced for the row you select, when you select it. The panel behaves
  exactly as before.

---

Verify the download

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

Expected SHA256: 1F297E22218945C93167AEEC1DD1943E88E7BF26F21E6AFEA3D113ED3D7999DD

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