SysManager 1.75.20

[1.75.20] - 2026-09-01

Two Dashboard tiles were telling you things SysManager had not actually checked. If your drive health could
not be read, the tile still said your drives were healthy. And the "No memory errors" tile was not looking at
memory errors at all — it was looking at how much memory was in use.

Fixed

• "All SMART indicators healthy" no longer appears when your drives could not be read. Reading drive
  health needs a part of Windows that is sometimes broken, switched off, or blocked without administrator
  rights. When that happened SysManager got nothing back — and treated nothing back as a perfect result, so
  the tile reported your drives were in good health without having looked at them. It now says the health
  could not be read and points at the System Health tab. A drive that genuinely reports a problem is
  unaffected: those wordings and thresholds are unchanged.
• The "No memory errors (30 days)" tile now actually looks for memory errors. It was deciding based on how
  much memory was currently in use, which has nothing to do with whether your memory has faulted. So a
  computer with real memory hardware errors was told there were none as long as memory use was low, and a
  perfectly healthy computer running a lot of programs was warned about "memory issues" that the System Health
  tab then said did not exist. The tile now reads the same 30-day Windows error record the System Health tab
  reads, and words the result the same way, so the two can no longer disagree. If that check itself cannot
  run, it says so rather than reporting good news.
• The overall health score no longer counts unread information as perfect. Drive health, memory and uptime
  each scored full marks when their source returned nothing, so a computer where all three failed showed a
  perfect score with no advice at all. An unread component is now scored as unknown, which is what a single
  unreadable drive was already scored — the code said so in a comment while doing the opposite one screen
  above.

---

Verify the download

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

Expected SHA256: 59771DA5AA05DACEC8BEA93800E3DFACB96A857650403D075569A97358D9DF1E

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