SysManager 1.130.84 download

[1.130.84] - 2026-10-23
One part of SysManager now talks to the graphics card's own interface, so a graphics driver restart no longer
leaves the Dashboard showing a GPU number that has stopped changing, and the GPU readings can no longer go missing
for the rest of a session.
Fixed
- After a graphics driver restart the Dashboard's GPU percentage froze and was still shown as live. It asked
the card for a reading through a reference it had taken once at startup, which NVIDIA throws away whenever the
card or the display is reconfigured, by a driver restart (Win+Ctrl+Shift+B), a driver update, or plugging in a
monitor. From then on every reading failed silently, the number kept the last value it had read, and the log
filled with about 10,000 lines an hour, which pushes out the history a bug report needs. The reference is now
replaced two seconds after a failed reading, and until there is one the percentage reads zero instead of
standing still. Since 1.42.12.
- The Dashboard, the background history and the temperature card could each lose their GPU reading for the
session. All three set up the graphics card's interface themselves, at almost the same moment on start-up, and
that interface is not built to be set up from several places at once: whichever lost the race switched its own
GPU reading off until SysManager was restarted. One part of the app now owns that interface and the other three
ask it, so there is one set-up and nothing to lose. Since 1.47.0.
- The card was looked up again on every reading. The background history did it every 10 seconds and the
temperature card every 2, each asking the interface for the list of graphics cards before reading one. That
lookup now happens once and the result is shared, and it is repeated only after a reading fails. Since 1.47.0.
Verify the download
Get-FileHash .\SysManager-v1.130.84.exe -Algorithm SHA256
Expected SHA256: AD69605B805173A0EDA8D209391F6F0555984949A2C83606E497955E500A2D20
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.84.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.84.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.