Pakua SysManager 1.136.48

[1.136.48] - 2026-10-31
Pausing Windows updates for a number of days now pauses them for that long, the way Windows
Settings does.
Fixed
- Windows Update's Pause wrote its pause into the Windows Update policy, in a form the policy
does not define. The policy has only a start date, and a pause there lasts 35 days from it
whatever length you chose, so either nothing was paused, or updates stayed paused for up to 35
days while the tab said they had resumed. The pause now uses the same values as Pause updates
in Windows Settings: it ends when you chose, and Windows Settings shows it and can resume it
early. Restore default, and the next pause, also clear a pause an earlier version left in the
policy, and the tab shows one set there as lasting 35 days from its start. This was there since
the pause was added in 1.30.0.
Verify the download
Get-FileHash .\SysManager-v1.136.48.exe -Algorithm SHA256
Expected SHA256: 4E8307AFC91A3148CC9AA1352AC3E6A9BC0640807C7A4B7C5BD3472D3FE1F95C
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.48.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.48.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.