Pakua SysManager 1.113.9

[1.113.9] - 2026-09-24
Four more places stop reporting success for something that did not happen. The Dashboard's app update
and its Windows Update button, the Performance tab's Ultimate Performance plan and hibernation switch, and
System Fixes' Windows Update reset each said "done" without checking — now each reports what actually
happened.
Fixed
- Dashboard: a failed "Update All Apps" ends as Failed, not "✓ Done". winget exits with an error when any
one app fails to update — one that is still running, an installer that errors — and the card showed
"✓ Done" above winget's own failure message. It now shows Failed with that message. Present since the
quick actions were added in v1.17.0.
- Dashboard: the Windows Update button no longer pretends to check. "Check Windows Updates" showed a
progress bar for half a second, ended in "✓ Done" and wrote "Check initiated from Dashboard" to Recent
Activity, but it never contacted Windows Update. It is now "Open Windows Update" and takes you to the
Windows Update tab, where the check really runs. Present since v1.17.0.
- Performance: Ultimate Performance is switched on in every display language, and says so when it cannot
be. The plan was read from powercfg's English wording, which Windows translates. On Windows in other
languages the switch was skipped and the tab still said "Power plan set to Ultimate Performance". The
plan is now read by its identifier, which is the same in every language, and a PC where Windows does not
provide it is told so. When Windows lists the built-in plan itself, it is used directly instead of being
copied again. The active-plan reading was fixed the same way earlier; this path had been missed. Present
since v0.12.0.
- Performance: the hibernation switch reports failure when Windows refuses. On a PC that does not
support hibernation — many virtual machines, some firmware — turning it on failed, and the tab still said
"✓ Hibernation enabled." It now reports that the change failed, and it also checks the result rather than
trusting the request. Present since v0.13.0.
- System Fixes: Reset Windows Update fails when a cache folder cannot be cleared. The reset works by
renaming two folders that Windows Update keeps its downloads and signatures in. When one was still in
use, the rename failed without a word, and the fix still said it was done and asked for a reboot that
would change nothing. It now reports the failure with the reason, and restarts the update services
either way. Present since the System Fixes tab was added in v1.26.0.
Verify the download
Get-FileHash .\SysManager-v1.113.9.exe -Algorithm SHA256
Expected SHA256: D1155C51CD789CEFA85E2D75089B5A3D7814769B02E303085CCD86253F474E37
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.113.9.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.113.9.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.