Pakua SysManager 1.128.5

[1.128.5] - 2026-10-10
Removing a ping target, or an app's sound ending in Volume Control, leaves keyboard focus on the row now in its
place (#2650).
Fixed
- Ping and Volume Control keep keyboard focus when a row goes. Removing a custom target in Ping takes its row out
of the list, and so does an app's sound session ending in Volume Control. A button or slider focused in that row
took keyboard focus with it, which left focus on the list as a whole, so someone using the keyboard or a screen
reader had to find their place again. These lists now keep focus the way the lists that refresh have since 1.127.14:
it moves to the same control in the row now in the removed one's place, or in the last row when the last one went.
The console's output and the sidebar's search results, which are emptied and refilled, do the same. This had been
so for each list since it was added.
Verify the download
Get-FileHash .\SysManager-v1.128.5.exe -Algorithm SHA256
Expected SHA256: 52584786CB61D8059F28EAC12EBE8C616CD437C2E33464380583FBC8EB92F905
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. 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.128.5.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.128.5.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.