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.3
| 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.3] - 2026-09-22
Charts drew on top of their own "nothing here yet" message. On a PC with no temperature sensors, Resource
History's Temperature chart showed overlapping axis labels, a row of identical 01-01 00:00 timestamps, and the
"No temperature data" message tangled up with the legend. Reported by @smoutsio, with a screenshot, against
1.112.2 — thank you.
Fixed
- An empty chart now hides instead of drawing behind its message. The message and the chart deliberately
occupy the same space, so the explanation appears where the chart would be — but only the message was being
hidden and shown. The chart carried on drawing its axes, gridlines and legend underneath it.
- Three charts had this, not one. The same mistake was in Resource History's Usage chart and in Bandwidth
Monitor's throughput chart. Only the temperature one was reported because it is the only one whose empty
condition is common: most PCs expose no readable temperature sensors, while a PC with no usage history at all
is rare.
- No more 01-01 00:00 on a time axis. With nothing to plot, the chart invented a range starting near
zero, and a value of a few ticks is a date in the year 1 — which is what that label is. A time label now
renders only for a value that could actually be a sample.
Verify the download
Get-FileHash .\SysManager-v1.112.3.exe -Algorithm SHA256
Expected SHA256: 3ABE37A0A1E42BDCC9A44F8D3DCF9B2E39AAAED35A6F43B41B80E7A24EE0C17C
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.3.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.3.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.https://github.com/laurentiu021/SystemManager/releases/tag/v1.112.3
