Pakua SysManager 1.136.81

[1.136.81] - 2026-11-02
Large Files and System Logs describe what they read, and Large Files no longer scans a drive that is gone as an empty one.
Fixed
- Large Files' result line, its toast and its log line named the location and minimum size chosen when the scan ended,
not the ones it read, and both stay open to change while it runs: picking Documents during a scan of Downloads at
500 MB reported Downloads' files as Documents' at the new size. They name what the scan read now. This was there
since 0.5.0, when the scan was part of Deep Cleanup.
- Large Files read its list of locations once, when the tab was first opened, and the tab is kept for the whole run,
so a drive connected later never appeared, and one unplugged since stayed listed and scanned as a drive with nothing
on it, with a "Large file scan complete" toast. The list is read again each time the tab is shown, keeping the
location picked, and a location that is gone is said to be, without a scan. This was there since 0.5.0 too.
- System Logs named the log in the box in the line after a load, which the "could not be read" overlay shows too, and
in the file an export suggests, though the box stays open during a load and changing it loads nothing: switching to
Security during a System load reported System's events as Security's. Both name the log that was read now. This was
there since 0.3.0, the first version.
Verify the download
Get-FileHash .\SysManager-v1.136.81.exe -Algorithm SHA256
Expected SHA256: D4E7C2E718DCDA545306C20CAD7E14519831B681558B55D4593245490A941789
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.81.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.81.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.