Pakua SysManager 1.136.71

[1.136.71] - 2026-11-02
Starting and stopping a service on Services no longer freezes SysManager, a service that stops at once says so straight away, and the filter counts keep up.
Fixed
- On Services, Stop and Start froze SysManager's window while Windows worked: stopping a service stops each running
dependent first and waits for it, and starting one waits until its program is up, and both waited on the thread that
draws the window. They run in the background now. This was there since 0.13.0.
- A service that stopped as soon as it started kept the tab waiting the full 30 seconds, then was said to be maybe
still starting. It now reads "started and then stopped" at once, the way services.msc puts it. This too was there
since 0.13.0.
- After Start, Stop, Disable or Enable, the Running and Stopped chips kept their old counts until the list was
filtered again. They follow every change now. This was there since 1.61.10, when those chips were added.
Verify the download
Get-FileHash .\SysManager-v1.136.71.exe -Algorithm SHA256
Expected SHA256: C821EE26F9B86053629E7D93A0CADC1D1F9B60671CAD78CCA1869D8F59454191
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.71.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.71.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.