SysManager 1.113.5 download

[1.113.5] - 2026-09-24
The Bandwidth Monitor now calls each program by one name, whichever mode it is in. Turning on
precise rates used to rename every row — chrome.exe became chrome — and in the default mode the
Windows kernel's own row read System.exe with a blank icon instead of System with the Windows one.
Fixed
- Each program keeps the same name in both Bandwidth Monitor modes. The default, no-administrator
mode added ".exe" to every program's name, while precise mode — like Process Manager — shows the name
without it, so switching modes relabelled the whole list and the CSV export changed with it. Both modes
now use the name without the extension. The same change fixes the kernel's own row: "System.exe" is not
a real file, so it matched neither the icon search nor the list of Windows processes and showed the
generic icon; as "System" it gets the Windows icon in both modes. Present since the tab was added in
v1.54.0.
- A program precise mode cannot name yet shows as "PID 1234", then its real name. The kernel trace
sometimes reports a network event before it knows which program sent it, and gives a stand-in name,
Process(1234), for it. Precise mode kept the first name it saw for each program, so that stand-in could
stay on the row for the rest of the session. It now waits for the real name, and shows the same
"PID 1234" the default mode uses until one arrives.
Verify the download
Get-FileHash .\SysManager-v1.113.5.exe -Algorithm SHA256
Expected SHA256: 7F18E12D16E2CE40CA19BCC17F8A95DA1E31AD4056C32081490A053DE39C2F06
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. 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.113.5.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.113.5.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.