SysManager 1.130.73

[1.130.73] - 2026-10-22

The Dashboard says when SysManager crashed last time, its restart alert agrees with the Windows Update tab, and
its critical-event count covers exactly the last 7 days.

Fixed

• The notice that SysManager closed unexpectedly was never shown. The Dashboard raised it while the window was
  still being built, before the window listened for notices, and the record of the crash it came from was already
  gone, so it was never offered again. A notice raised that early now waits for the window. Since 1.57.2.
• The Dashboard said "No pending reboots" when the Windows Update tab said one was required. Its alert read
  only Windows Update's record, so after a Windows feature change, which leaves a restart pending, or after an
  installer asked to replace files at the next start, it stayed green. Both now make the same check, over all
  three places Windows records a pending restart. Since 1.17.0.
• The critical-event count covered the wrong 7 days. It measured the week in local time against the UTC times
  Windows keeps, so it was off by the time zone's offset: three hours short at UTC+3, five hours long at UTC-5.
  It now counts the way the System Logs tab reads. Since 1.17.0.

---

Verify the download

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

Expected SHA256: 8BB71B4A0783A74819959DC8B2A60CB2E2EDDD349538FC05AAA14A82F0EF25C8

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