Pakua SysManager 1.136.125

[1.136.125] - 2026-11-06
Process Manager refreshes in a seventh of the time, measures CPU over the whole second between refreshes, and shows when every process started, the system's own included.
Fixed
- Each refresh opened every process three times, read its CPU time twice with a tenth of a second waited out between,
and built an object for every thread on the PC to count them. On my PC a refresh of about 610 processes took 121
to 148 ms and threw two exceptions. The whole list now comes from one query of the process list Windows keeps, a
process is opened only once, to find its file, when it first appears, and a refresh takes 14 to 20 ms and throws
none. CPU is the use over the second since the refresh before, rather than over that tenth of a second. Since
1.10.2.
- The Started column showed a dash for most of the system's processes without administrator rights, because the
start time was read through a process handle Windows does not give for them. It comes from the same list now, so
every process has one. Since the column was added, in 1.89.0.
Verify the download
Get-FileHash .\SysManager-v1.136.125.exe -Algorithm SHA256
Expected SHA256: 3FA65C293BE807C68F3A55F112067C23A3CF468A7F04C0B4F1D45590A2673310
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.125.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.125.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.