Pakua SysManager 1.136.83

[1.136.83] - 2026-11-02
A scripted or scheduled command-line run now writes a log, so a cleanup that failed or skipped a folder says why.
Fixed
- A command-line run, from a script or from Task Scheduler, wrote no log at all: the log was set up only for the
window and the updater, so everything a --cleanup, --health or --purge-standby logged was dropped, as was a
fault the run itself caught, and the handlers that record a crash were never wired. A run from Task Scheduler has no
console, so a failed or partial scheduled cleanup left nothing to read. It now logs to the same folder as the
window, with the user name removed the same way, and notes the command and its exit code. This was there since the
command line was added in 1.49.0.
Verify the download
Get-FileHash .\SysManager-v1.136.83.exe -Algorithm SHA256
Expected SHA256: 766B6B1B2326AC40AA5690E44A783EFF38E54AC4EA0886711FF3D770FDE180A6
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.83.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.83.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.