SysManager 1.75.21

[1.75.21] - 2026-09-01

A drive's temperature could be shown under a different drive's name, which is worse than showing no name at
all — you could be looking at a healthy drive while worrying about the wrong one. The Temperatures readings are
also cheaper to collect now, and a machine where the sensor library will not start no longer keeps retrying it
every two seconds.

Fixed

• A temperature is no longer shown under the wrong drive's name. SysManager reads drive temperatures from
  one source and drive names from another, and it was pairing them purely by their order in each list — with
  nothing to confirm the first temperature belonged to the first name. When the two lists did not line up, and
  they do not whenever Windows cannot read one of the drives, every name after that point shifted onto the
  wrong reading. So a healthy drive's 38 °C could appear under a failing drive's name, hiding the one that was
  actually hot. Names are now only filled in where SysManager had no name of its own, and only when the two
  lists are the same length — because a different length is proof the pairing cannot be trusted. When it cannot
  be trusted, the generic "Drive 2" stays, which is honest rather than confidently wrong.
• The Temperatures card no longer goes completely blank because of one drive. Fetching drive names uses a
  part of Windows that occasionally reports a temporary error. That error was not being handled, and because
  the names are fetched before the sensors are read, it wiped out the whole card — processor, graphics card and
  motherboard readings included, not just the drive names. It is handled now, and a temporary failure is
  retried on the next reading instead of being remembered for the rest of the session.
• A sensor library that cannot start is no longer retried every two seconds. Reading processor and
  motherboard temperatures needs a low-level component that will not load on some machines — certain security
  settings block it. SysManager kept trying to load it on every reading, about thirty times a minute for as
  long as the app was open, and each failed attempt left something behind. It now tries once, and if that
  fails, stops trying and cleans up after itself.

Changed

• Drive temperatures are collected far less often when not running as administrator. In that mode — the
  normal one — each Dashboard reading was doing a full drive-health inspection, every two seconds. Drive
  temperature changes over minutes, not seconds, so the result is now reused for up to 30 seconds. That is
  roughly fifteen times less work for a number that reads the same either way. Running as administrator was
  already doing this; only the ordinary path was missed.

---

Verify the download

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

Expected SHA256: 052EF3E69DE8B1A90A57341832533C46221E675977DB1259DE28546B6273E0DB

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