SysManager 1.136.127: prenos za Windows

[1.136.127] - 2026-11-06
Resource History no longer rewrites its whole history file every hour, and the Resource History and Bandwidth Monitor charts read only the part of their file they show.
Fixed
- On a PC where SysManager runs all day, Resource History rewrote its whole history file every hour. An hour of
samples had always expired by then, so each hourly prune read, parsed and wrote again about 60,000 lines at the
7-day window and 260,000 at 30, with a flush to the disk, 24 times a day. On my PC a prune of a 30-day file took
824 ms and wrote 19 MB. It now looks at the oldest sample each hour, in under a millisecond, and rewrites the
file only once that sample is a day past the window, so at most once a day. The file can hold up to that day
more, and the charts never show it. Since 1.47.0.
- Showing a range in Resource History or Bandwidth Monitor read the whole history file first, so the last hour of a
30-day file read all 260,000 lines: 132 to 152 ms and 72 MB of memory on my PC. Both now read from the end of the
file back to the start of the range, and that last hour takes a few milliseconds. Since 1.47.0 for Resource History and
1.54.0 for Bandwidth Monitor.
Verify the download
Get-FileHash .\SysManager-v1.136.127.exe -Algorithm SHA256
Expected SHA256: C2C4D98B6CB7AC637525872DB3D12E67AE3045C7A8AA546F243B41545BB7305D
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. Two checks
run on their own when SysManager starts: the version check against the GitHub Releases
API, at most once a day, and the Dashboard's app-updates alert, which asks winget. The
About tab can switch off either. Everything else that uses the network runs only when you
use 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.136.127.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.136.127.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.