Pakua SysManager 1.136.17

[1.136.17] - 2026-10-30
When an update or Go back cannot finish after SysManager has closed, SysManager opens again
and says why.
Fixed
- An update that could not replace SysManager's file after it had closed reopened the old
version with nothing said, and when the check that found the update had run in the last day,
About even read "Checked recently". The reason is now kept for the version that reopens:
About says "The update to vX could not be installed", names the reason and the version still
running, and looks for the update again at once instead of a day later. A Go back that cannot
finish says so beside its button. Present since updates were installed in-process in 1.42.11.
- A new version that failed its own checksum check, or came without one, left SysManager
closed for good: the part that installs it refused and opened nothing. It now opens the
version that was there again and says why. Present since 1.130.86.
Verify the download
Get-FileHash .\SysManager-v1.136.17.exe -Algorithm SHA256
Expected SHA256: F6AA286588B9C17038DC9645DBA493C2F364A2E82BD0A050FD98DD3C82181609
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.17.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.17.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.