Pakua SysManager 1.114.22

[1.114.22] - 2026-09-28
Camera/Mic/Location now names any device whose history could not be read. It used to leave that device out
without a word, or say that nothing had been recorded at all.
Fixed
- Camera/Mic/Location: a history that could not be read is named, not skipped. When Windows did not let
SysManager read a device's access history, that device was left out without a trace.
- With all three unreadable, the tab said "No camera, microphone, or location access has been recorded yet."
It now says the history could not be read, and a Refresh that reads nothing keeps the previous list.
- With one unreadable, the tab listed the others as if every device had been checked. It now adds, for
example, "Could not read the camera history.", and the empty state names only what was read.
Present since the tab was added in v1.32.0.
Verify the download
Get-FileHash .\SysManager-v1.114.22.exe -Algorithm SHA256
Expected SHA256: 7930373A631A8CB7AEB54B1D942F478C20BEBDC4ACC7EDE2A983DB857BFBAE68
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.114.22.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.114.22.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.