Sækja SysManager 1.136.65

[1.136.65] - 2026-11-02
Traceroute stops at a router that says the destination cannot be reached and shows which one, and a finished trace keeps saying Done.
Fixed
- A router that answered that it could not reach the destination, or that it refused the trace, was listed as a
hop that did not answer, and the trace went on probing up to 30 hops. That answer is where the path ends, so it
is now the last hop, with the router's address, and the status line names the router and says what it answered.
- A one-off trace could say "Tracing … hop N" again a moment after it said "Done", because the update for the
last hop was still waiting behind the window's own work when the trace ended. Updates that arrive after the end
are now dropped.
- A trace was kept under whatever the host box said when it ended, so typing another host while it ran filed the
route under the new name, or a half-typed one, and a Ping target of that name showed the other route. The host
is read once, when the trace starts, and the box cannot be changed until the trace ends.
- The chart drew a hop that did not answer at 0 ms, as if it were the fastest, and the line dropped to the floor
between real hops. It is a gap now, as a lost ping is on the chart beside it.
All four were there since 0.3.0.
Verify the download
Get-FileHash .\SysManager-v1.136.65.exe -Algorithm SHA256
Expected SHA256: 2DF5A131E7DA7F138B46532B8401CCE4163DC42BF382B33458A3EDABD2D12717
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.65.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.65.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.