Sækja SysManager 1.136.84

[1.136.84] - 2026-11-02
Standby List Cleaner's auto-purge watches free memory instead of purging every 2 seconds under pressure, and the command line reports what a purge released.
Fixed
- Standby List Cleaner's auto-purge compared its threshold with available memory, which counts the standby list, and a
purge only moves that list's pages to the free list, so available memory stays where it was. It fell below the
threshold only once the standby list was almost empty, so under memory pressure it purged every 2 seconds, freed
next to nothing and threw away the cache Windows had just rebuilt, while with a large standby list and little free
memory, the case it exists for, it never fired. It now purges when free memory is below the threshold and the
standby list holds at least 1 GB, at most once every 30 seconds, and its switch says free RAM. This was there since
the tab was added in 1.42.0.
- --purge-standby --json reported freedMB as the change in available memory, about zero, and when the second
reading was a few bytes lower the unsigned subtraction wrapped to 17,592,186,044,416. It now reports what the
standby list released, with its size before and after, as signed figures.
Verify the download
Get-FileHash .\SysManager-v1.136.84.exe -Algorithm SHA256
Expected SHA256: D625E2E8E5813EC804D6D883AB5677AD4F7D1528DE771CA95E731D0B8FF4D69B
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.84.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.84.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.