Shkarko SysManager 1.57.4

[1.57.4] - 2026-08-06
Fixed
- Switching the Resource History chart between ranges no longer risks an error. Picking a different period while another one was still loading could have both of them rebuild the five graphs at the same time, which could fail instead of drawing. Only one rebuild runs at a time now. This is the same problem that was fixed on the Bandwidth Monitor in 1.57.3 — Resource History had it too, and it was missed then.
- An unreadable history file no longer crashes the recorder. Both the Resource History and Bandwidth Monitor recorders handled a disk error while reading or writing their history, but not a permission error — and a locked-down or read-only file produces the second, not the first. Because the recording runs quietly in the background, that surfaced as the app failing over something the user never started. Both now log it and carry on with an empty chart, exactly as they already did for a disk error.
Verify the download
Get-FileHash .\SysManager-v1.57.4.exe -Algorithm SHA256
Expected SHA256: 68981C6D11BADEA58AD66BBF93C0028087E7850D79539A232663CC03E31B1CFB
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.
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.57.4.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.57.4.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.