Pakua SysManager 1.136.105

[1.136.105] - 2026-11-05
Uninstaller removes apps installed on another drive or for one user in Roaming AppData, and Cancel stops the search for what an uninstall left behind.
Fixed
- Uninstaller started an app's own uninstaller only from Program Files, the Windows folder, ProgramData or Local
AppData, so an app installed on another drive, or for one user under Roaming AppData, as some apps install, could
not be removed: the row said "outside trusted directories". Uninstalling runs only while SysManager is not running
as administrator, with your own rights, the same as Windows Settings, so the folder protected nothing. An
uninstaller anywhere on the PC's drives is started now; a script, or one on a network folder, still is not. The
folder list was there since 0.48.28.
- An uninstall command with an "&" or a ";" anywhere was refused, a folder name such as "Smith & Sons" included,
since 0.48.24. The characters are checked only where a command interpreter could read them, in the arguments; the
uninstaller's own path is started as a file.
- An uninstaller SysManager does not start says to remove the app from Windows Settings ▸ Apps, and why, instead of
ending "Refusing to run for security."
- Cancel showed while Uninstaller looked for what an uninstall left behind, and while it removed what you ticked,
but stopped neither, since the Left behind card first shipped, in 1.124.0. It stops both now. The card shows what
the search found before it stopped, and a stopped removal says what went, with the rest still on the list.
Verify the download
Get-FileHash .\SysManager-v1.136.105.exe -Algorithm SHA256
Expected SHA256: FA01E56D1F4B127162C88F20615FD8FA62064648AE6F0C438B1788F5E59B5CDA
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.105.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.105.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.