Pakua SysManager 1.136.16

[1.136.16] - 2026-10-30
Go back names the version it returns to, and is no longer offered once SysManager was updated
some other way.
Fixed
- After an update made in SysManager and a later one through winget or a manual download, Go
back was still offered as "the version you had before the last update", and pressing it
installed what the update made in SysManager had replaced, older than that. The kept copy now
records its own version and the version of the update that kept it, and Go back is offered
only while that version is the one running. The button and its question name the version,
which nothing on screen did before. Present since Go back arrived in 1.61.0.
- Go back froze the window, with nothing shown, while it checked the saved version against its
checksum, a file the size of the app. The check now runs in the background, and the tab says
"Checking the saved version…" meanwhile. Present since 1.64.2.
Verify the download
Get-FileHash .\SysManager-v1.136.16.exe -Algorithm SHA256
Expected SHA256: 49FB1401AA2B5DE7677016C3194F9E71BC75A6A348E1925B41FBF92E14440FFA
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.16.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.16.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.