Sækja SysManager 1.131.0

[1.131.0] - 2026-10-26
GPU usage and video memory now work on Intel and AMD graphics, not just NVIDIA — the Dashboard and Resource
History read the same counters Task Manager does.
Added
- GPU usage for every vendor. The Dashboard's GPU tile and the Resource History chart read load and video
memory from the counters Windows publishes for all graphics hardware, the ones Task Manager's own GPU column
draws. On a machine with more than one card, the busiest one is shown — on a laptop with switchable graphics
that is whichever card the app in front of you actually landed on. The figure is each engine type's share
added up and then the busiest engine type, which is how Task Manager arrives at its number too, so the two
agree.
Fixed
- GPU usage read 0% on every Intel and AMD GPU. Usage and video memory came only from NVIDIA's own API, so
on any other card the Dashboard showed "GPU 0%" with an empty bar — a number that reads as an idle GPU, on
most of the laptops this app is aimed at. The card's name was shown and nothing else was wrong, which made it
look like a measurement rather than a gap.
- A GPU that cannot be measured now says "N/A" instead of 0%. "Nothing can read this" and "this GPU is
idle" are different answers, and 0% is a legible number that means the second one. A machine with no usable
GPU counters — no WDDM 2.x driver, or one between driver states — now says so.
Changed
- The GPU temperature still comes from NVIDIA cards only, unchanged, and it is still the only GPU temperature
readable without administrator rights. Giving it the same vendor-neutral treatment needs a different Windows
interface and is a separate change.
Verify the download
Get-FileHash .\SysManager-v1.131.0.exe -Algorithm SHA256
Expected SHA256: 45757B5DC0C0402660A617E0DAB4D158D3379357737604CCD82D17F67842BF30
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.131.0.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.131.0.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.