Sækja SysManager 1.136.30

[1.136.30] - 2026-10-30
Bandwidth Monitor's precise mode no longer freezes the tab when its trace fails, and stops the
trace while the tab is hidden.
Fixed
- When the kernel trace behind precise mode failed to start with an error SysManager did not
expect, for example because other tools had taken every trace session Windows allows, the tab
froze: the list, the figures and the chart stopped, and the box stayed ticked. A trace that
cannot start now leaves the tab on the default view, unticks the box and says so.
- A trace that ended while the tab was open, stopped by another tool for example, went on being
shown as a live trace with every rate at zero. The tab now goes back to the default view and
says that the trace ended.
- The trace kept running while the tab was hidden or SysManager sat in the notification area,
receiving every send and receive on the PC with nothing on screen to use it, and its list of
apps grew with every program that touched the network. It now stops while the tab is hidden
and starts again when you come back, so the per-app totals count from then.
- A trace left running when SysManager was ended by force, by a crash or from Task Manager, kept
running with 64 MB of buffers until precise mode was next turned on. SysManager now stops it
when it starts as administrator, and the trace asks Windows for 8 MB. All four were present
since the tab was added in 1.54.0.
Verify the download
Get-FileHash .\SysManager-v1.136.30.exe -Algorithm SHA256
Expected SHA256: A9CBCB2A3D575386EB041763312F4DF68C11CB2B58C78388C44F85B1B439E189
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.30.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.30.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.