Pakua SysManager 1.136.104

[1.136.104] - 2026-11-03
The Dashboard names the drives on its temperature card again after a disk read fails, and System Health says when it could not read the drives.
Fixed
- When a read of the drives failed, which a WMI service still starting at logon is enough for, the Dashboard's
temperature card kept the failed read as if it were the drives. Run as administrator, a drive the sensors could
not name stayed "Drive 1" until SysManager was restarted; without administrator, the drive temperatures were gone
for 30 seconds. Only a read Windows answers in full is kept now, a failed one is tried again at the next refresh,
two seconds later, and a read that keeps failing is written to the log once rather than at every refresh. The
names were kept like this since 1.52.94, the temperatures since 1.75.21.
- Run as administrator, the temperature card asked Windows for the drive models in a query Windows does not accept,
at every refresh, and logged the refusal each time. It never named a drive, so it is gone, and the card names the
drives from the list System Health reads, as it already did. It was there since 1.17.0.
- System Health's Run SMART check said "Collected 0 disk report(s)." when Windows did not answer at all. It now says
the check failed, and why, and a read that stopped partway says so after the drives it did read.
Verify the download
Get-FileHash .\SysManager-v1.136.104.exe -Algorithm SHA256
Expected SHA256: AC97F7EC46E6979787F89CBC3A70C515A3444AABD138CF7EF57AB93A4FD238DA
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.104.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.104.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.