Pakua SysManager 1.57.8

[1.57.8] - 2026-08-06
Fixed
- The log file can no longer grow big enough to be unusable. SysManager keeps a diary of what it does, and that file is what you attach when reporting a problem. It had no size limit — one day's file was allowed to reach a gigabyte, which is far past what you could upload anywhere. Each file is now capped at 10 MB and a fresh one is started when it fills, keeping at most two weeks of them, so the diary stays small enough to send and takes a predictable amount of disk.
- The Volume Control tab no longer floods that log. If an app's audio could not be read, the tab wrote the same complaint twenty times a second for as long as it stayed open — filling the file with one repeated line and pushing out everything actually worth reading. It is now noted once, and again only if something genuinely changes.
Verify the download
Get-FileHash .\SysManager-v1.57.8.exe -Algorithm SHA256
Expected SHA256: AE472675F081159CA4C80384CF34592EDDEC3BEE7627B1D763452B1742279D40
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.
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.57.8.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.57.8.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.