Pakua SysManager 1.114.1

[1.114.1] - 2026-09-25
The Uninstaller no longer calls an app removed through winget before its uninstaller finishes. The
check v1.113.12 added now covers the apps winget manages too.
Fixed
- Uninstaller: the "still installed" check covers apps winget manages. v1.113.12 stopped reporting
"Removed" while Windows still lists an app, because some uninstallers hand over to a copy of themselves
and exit at once. That check ran only when SysManager launched the uninstaller itself. For an app winget
manages, winget runs the same uninstaller, waits only for the process it started, and never looks at the
uninstall list again, so the row still read "Removed" and left the list. The check now runs on both
paths. The message now says the uninstaller may still be running, because through winget it runs without
a window. The winget path has decided on the exit code alone since the tab was added in v0.11.0;
v1.113.12 fixed only the direct path.
Verify the download
Get-FileHash .\SysManager-v1.114.1.exe -Algorithm SHA256
Expected SHA256: 2973F2273FF26F4A845EB859FBC853EEF096B163F8E9FF450F2285453EFE90F7
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.1.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.1.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.