Pakua SysManager 1.136.129

[1.136.129] - 2026-11-06
SysManager no longer reads and rewrites the whole Resource History file as it starts.
Fixed
- The history sampler pruned its file as the app started, before its first sample: it read and parsed every line,
about 260,000 at the 30-day window, and wrote the file again for whatever had expired since the last prune. On my
PC a prune of a 30-day file took 824 ms and wrote 19 MB, and it ran in the first second of every launch. The
sampler's first look at the prune comes a minute in now, reads one line, and prunes only once a sample is a day
past the window, as its hourly look does. Since 1.47.0.
- A crash or a power cut in the middle of writing a sample could leave the file's last line without its ending, and
the start's prune was what dropped that line. The first sample written after a start now begins on a line of its
own when the last line was cut short, so it is not lost with it.
Verify the download
Get-FileHash .\SysManager-v1.136.129.exe -Algorithm SHA256
Expected SHA256: 3A8D4565F21BC378900B81AB67CC66228415EF70C446C6BD7AC8FBBC4F05E905
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.129.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.129.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.