Pakua SysManager 1.65.21

[1.65.21] - 2026-08-24
If you drive Windows by voice, 41 buttons and tick boxes could not be pressed by saying what is
printed on them. They now answer to their own labels.
Fixed
- 41 controls could not be activated by voice. Windows Voice Access and similar tools listen for
the words a control is announced by and match them against what you say. On these 41 the announced
name had been reworded rather than extended — the button printed "Export CSV" but announced "Export
logs to CSV", "Clear History" announced "Clear alert history", "Empty Recycle Bin" announced "Empty
the Recycle Bin". Saying the printed label matched nothing, and the failure was silent: a screen
reader read the announced wording out perfectly well, so nothing looked wrong unless you tried to
speak to it. Each name now begins with the words printed on the control and adds any extra detail
after them, which is what the other 209 controls already did.
- The check meant to prevent this had been accepting them. It asked only that the label's words
appear in order somewhere in the announced name, which "Clear alert history" does. It now asks for
them as one unbroken phrase, so a name may still add detail but can no longer reword the label.
Verify the download
Get-FileHash .\SysManager-v1.65.21.exe -Algorithm SHA256
Expected SHA256: 3448E25CC9155BA33EAA07360C842546B4CFCB90D3D2D9AED81847C8998C6AE6
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.65.21.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.65.21.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.