SysManager 1.111.3

[1.111.3] - 2026-09-21

The Dashboard's "critical events in Event Log" button opened the wrong page. It said how many critical
events Windows had logged in the last week, and its button took you to System Health, which does not list
them. It now opens the Logs tab, where the events are. The line that sent you to the right place was there
all along — it had been written twice, and the second copy won.

Fixed

• The Event Log alert opens the Logs tab. NavTargetId was assigned twice in a row with two different
  tabs, so the first assignment was dead. Both were real tabs, which is why the existing check that every
  navigation id resolves to a real page was satisfied either way.
• A guard now rejects any value that is assigned twice in a row. The compiler does not warn about it for
  a property, because a setter can do work. The assignment also happens inside a dispatcher callback that
  does nothing outside a running window, so a test exercising the alert would have passed while proving
  nothing. The check reads the source instead, across the whole app, and excludes the two shapes that are
  legitimate: a discarded result and a value built up in steps.

---

Verify the download

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

Expected SHA256: 57420B0314412B5B2FAC138E81B4148C111D7D67F34433E31A9CF9282306DD4A

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