Lataa SysManager 1.64.1

[1.64.1] - 2026-08-12
A rare crash that could happen if you closed the window while the Resource History tab was loading
its charts.
Fixed
- Closing the window while Resource History was loading could crash the app. The tab reads your recorded history from disk in the background and then redraws five chart lines. If you closed SysManager during that read — which is easy to hit, because the read starts on its own when you open the tab, when you change the time range, and when you press Refresh — the finished read tried to redraw charts whose drawing resources had already been released during shutdown. There were three separate ways it could fail, including one that turned a clean shutdown into an error. The loading path now checks whether the tab is still there before touching anything and stops quietly if it is not. Same kind of problem as the Bandwidth Monitor crash fixed in 1.63.1: after that fix every other tab was checked for the same pattern, and this was the one that had it. Only the Resource History tab was affected, and only at the moment of closing.
Verify the download
Get-FileHash .\SysManager-v1.64.1.exe -Algorithm SHA256
Expected SHA256: A2A30C0606593A17788DF16CD8A264B15E4087B8C2EC42AEF194AF261AC9DFEA
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
Free code signing provided by SignPath.io, certificate by
SignPath Foundation. Team roles, the release-approval process
and the privacy policy are documented under Code signing
policy.
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.64.1.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.64.1.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.