Pakua SysManager 1.136.112

[1.136.112] - 2026-11-05
Resource History's CPU readings are the average over each 10 seconds again while the Dashboard is open, and the Dashboard's CPU figure no longer jumps every 10 seconds.
Fixed
- Every CPU reading measured the time since anyone's last reading, since the Dashboard, Resource History and the tray
icon shared one starting point. With the Dashboard open, which is the tab SysManager opens on, each Resource History
point was the CPU use of the last fraction of a second rather than of its 10 seconds, so a short burst was stored as
a 10-second value and a spike could be missed. The other way round, each Resource History or tray reading cut one of
the Dashboard's 300-millisecond readings short, which put an odd number on its CPU figure every 10 seconds. Each of
them measures over its own interval now, and Resource History takes its first point 10 seconds after SysManager
starts, so that one covers 10 seconds as well. Since 1.76.24.
- A test refuses a tab or service that shows the CPU load without measuring it over its own interval.
Verify the download
Get-FileHash .\SysManager-v1.136.112.exe -Algorithm SHA256
Expected SHA256: 28B63A9C330BBB05B840D4F4EA48CD054E908C32DE1F070547046252EDBFA4C0
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.112.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.112.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.