Aquesta és una versió anterior. La versió actual és la 1.131.0. SysManager 1.131.0 · Data de publicació:
Fitxers d’instal·lació 1.130.27
| Arquitectura | Tipus | Àmbit | Mida del fitxer | Baixa | SHA256 |
|---|---|---|---|---|---|
| 64 bits | Portable | — | — | github.com | VirusTotal |
L’enllaç i l’SHA256 provenen del manifest comunitari del Gestor de paquets del Windows. Convé comparar el hash del fitxer baixat abans d’executar-lo.
Notes de la versió
[1.130.27] - 2026-10-21
Traceroute shows the route of any host it traces, and stopping auto-trace stops tracing its host.
Fixed
- A trace of a host that is not a Ping target showed nothing. The Hops table and the chart listed Ping targets
only, so tracing any other host, the very thing the tab offers, ended "Done — 14 hops" with "No route traced yet"
still on screen. A Ping target typed in another letter case was dropped the same way. The route of the host traced
last now appears beside the targets', until another host is traced. Since Traceroute was added (0.3.0).
- A host auto-traced once was traced until SysManager closed. Start auto-trace added its host to the loop and
nothing took it out, so each new host added one more trace every round, whichever tab ran the loop. Stopping
auto-trace, on Traceroute or on Ping, now takes the host out, and starting it on another host replaces the last one.
Since auto-trace of a typed host was added (0.21.6).
- Tracing 0.0.0.0, or a name too long to look up, raised the error dialog. In auto-trace, the same host ended the
loop for every target while the tab still said auto-trace was running. Such a host now gets a message saying it
cannot be traced, and the loop goes on with the others. Since 0.48.11, when the trace stopped counting every error as
a hop that timed out.
Verify the download
Get-FileHash .\SysManager-v1.130.27.exe -Algorithm SHA256
Expected SHA256: 737D0A3500042C990F72A19FE068C2CD64EAEEC9AD4120A4BC075D77A58FC352
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.130.27.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.130.27.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.https://github.com/laurentiu021/SystemManager/releases/tag/v1.130.27
