SysManager 1.76.23

[1.76.23] - 2026-09-07

Three things the app already knew and never told you. The Context menu tab worked out which menu style was
applied and then drew all three buttons identically, so there was no way to see which one you were on. "What's
new" downloaded the release notes for the newest version and displayed none of them. And the ten release cards
under it each held a link to their release on GitHub that nothing let you click.

Fixed

• The Context menu tab shows which menu style is applied. It reads the current style on every scan and
  compares it against the three presets, but the buttons were all drawn the same, so the answer was invisible
  and the only way to be sure was to apply a preset and watch the entries change. The matching button now
  carries a tick, the accent colour and its own accessible name.
• "What's new" shows the release notes it fetched. The update check downloads the full notes for the
  newest version, and the section presented only the version number and date — the notes themselves were
  fetched on every check and thrown away. They now appear under the version, scrollable when long.
• Each release card links to its release. Every entry in the release history carried the GitHub URL it
  came from and offered no way to open it, so reading a note was a dead end. Each card now has a "View on
  GitHub" link, greyed out for the rare entry whose URL came back empty.

Changed

• An unused second way to describe a drive was removed. The chkdsk drive picker built a one-line summary
  of each drive that no part of the interface asked for; the row composes what it shows from the individual
  fields. Five tests kept it alive by reading it exactly the way the missing binding would have.

Added

• A check that a view-model property nothing displays cannot ship. The three fixes above are one defect
  repeated: a property maintained by the code, verified by tests, and bound by no view. The existing sweep
  for this asked whether a property was written or shown, which every instance of the defect satisfies. The
  new one asks whether it is shown in XAML or read somewhere other than its own assignment, and it names the
  offenders rather than reporting a count.
• A check that a style trigger cannot be silently outranked. The first cut of the Context menu fix put the
  tick and the accessible name in a trigger while the buttons still set both as plain attributes — and WPF
  ranks an attribute above a style trigger, so the colours changed and the tick never appeared. Nothing else
  could see it: the property was bound, the trigger was there, the build was clean. Caught while reviewing the
  change and now pinned.

---

Verify the download

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

Expected SHA256: E48DA62A8BD04C6F96703A0932CF5FC6961EDBD8E20410B98B0CBF6A79CE1CCC

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