Pakua SysManager 1.127.7

[1.127.7] - 2026-10-09
System Health and Ping now show "—" for a figure that was not measured, instead of 100%, a bare unit or nothing
(#2600).
Fixed
- System Health: a drive that does not report its wear no longer reads "LIFE REMAINING 100%". Unknown wear counted
as none, so a hard disk, or one of the many SSDs that do not report wear, showed 100% with a full bar, as if it were
new. It now reads "—" with an empty bar. The other figures on the same card had the same fault in another form: a
drive with nothing to score read a bare "%" for HEALTH, one with no temperature read " °C", and read and write
errors it does not count read nothing. Each now reads "—". The card has shown them this way since its gauges
arrived in 0.16.0.
- Ping: a ping that got no reply no longer reads " ms". Each row's latency, and an average or jitter not measured
yet, now read "—". They had read that way since 0.19.0.
- A test now fails when any page counts on a binding's fallback value to stand in for a missing figure, which WPF
never shows, so this cannot come back on another page.
Verify the download
Get-FileHash .\SysManager-v1.127.7.exe -Algorithm SHA256
Expected SHA256: 36F3EFBB7083D4265E89888376573690BFBCB1C07A041443DCD1536E6C8AEA94
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.127.7.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.127.7.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.