Aquesta és una versió anterior. La versió actual és la 1.130.86. SysManager 1.130.86 · Data de publicació:
Fitxers d’instal·lació 1.112.1
| 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.112.1] - 2026-09-21
The system report no longer carries your network card's permanent serial number. The report is what the
app tells you to attach to a bug report, and all three export formats included each adapter's hardware (MAC)
address and full local IP address, with nothing anywhere saying so. A MAC address does not change when you
reinstall Windows, and it cannot be taken back once it is in a public thread. Those two fields are now left
out or shortened in every format, including on screen.
Fixed
- The MAC address is gone from the text, HTML and JSON exports, and from the report shown in the tab. A
redacted variant already existed and was used only by the diagnostics bundle, so the four export commands
and the on-screen report still carried the full values. Redaction now happens once, where the report data is
gathered, so no format can miss it — including any format added later.
- The local IP address is shortened to 192.168.x.x rather than removed. The network half is the part
that answers a "no internet" question: whether the address is private, static, or a 169.254 self-assigned
one. The host number answers nothing anyone has asked.
- On-screen too, not just on export. The tab shows the same text an export writes, so a screenshot of the
System Report tab published the MAC exactly as attaching the file did. That route is closed by the same
change.
- The HTML report's footer described the wrong thing. It read "no data leaves this machine" — true of the
application, and beside the point printed at the bottom of a file whose purpose is to be sent to somebody.
It now says what is true of the file: that it lists your hardware and not you.
Verify the download
Get-FileHash .\SysManager-v1.112.1.exe -Algorithm SHA256
Expected SHA256: 51B3C60F8D12A5854D4EFDFDCF37369370202E93427A083FDCB75B581D8C71BC
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.112.1.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.112.1.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.https://github.com/laurentiu021/SystemManager/releases/tag/v1.112.1