Pakua SysManager 1.132.0

[1.132.0] - 2026-10-28
Dashboard quick actions can now be cancelled mid-run, System Logs and Disk Analyzer put an actual
button next to their admin-rights messages instead of only naming the problem, and copying a path or
revealing a file that is no longer there now says so instead of doing nothing.
Added
- A Cancel button beside the Dashboard's quick-action progress bar, for as long as the action runs,
wired to Escape the same way every other cancellable operation is. None of the four (Quick Cleanup,
Update All Apps, Check Windows Updates, Run Speed Test) could be stopped before this short of closing
the tab; Update All Apps passes the token through to each package so it stops between apps rather
than mid-download.
- A "Run as administrator" button on the Security log's elevation notice in System Logs, and on a Disk
Analyzer folder Windows refused to list. Both used to only name the problem, with nothing on the page
to act on it.
Fixed
- Quick Cleanup, Update All Apps and Check Windows Updates only ever reported two fixed milestones, not
real progress, so their bar showed fake progress instead of being indeterminate; Run Speed Test keeps
its continuously updating percentage.
- "Show in Explorer" on Large Files, Duplicate Finder and Disk Analyzer did nothing, silently, for a
file or folder that had been moved or deleted since the scan, with no way to tell that from the
window simply opening behind another one. All three now say so.
- "Copy path" and every other "Copy" button in the app (About, System Health, System Report, the CLI,
System Logs, Large Files, Duplicate Finder, and the shared console five tabs use) swallowed a busy
clipboard without telling you, or told you in a different sentence on every tab. They now share one
wording through a new ClipboardFeedback helper, and Browser Cleaner's extension-page copy, which
only caught one of the three documented clipboard failures, now catches all three.
Verify the download
Get-FileHash .\SysManager-v1.132.0.exe -Algorithm SHA256
Expected SHA256: 6CDAFF77873FC78D96F3FBE32FB422070C77AFEFB9BEE914DE44983CA454AD4D
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.132.0.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.132.0.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.