Descarcă SysManager 1.130.82 pentru Windows

[1.130.82] - 2026-10-23
The Dashboard says when the processor's temperature needs the PawnIO driver instead of losing it after a restart
as administrator, Hottest Core is a core's own temperature, and the background history no longer queries every
disk every 10 seconds.
Fixed
- Running as administrator took the processor's temperature away instead of adding it. The sensor library
SysManager uses reads the processor and the motherboard through PawnIO, a driver other monitoring tools install
and SysManager does not. Without it, the Temperatures card asked you to run as administrator for the processor,
and after the restart the processor row was gone without a word. The row now says "Requires driver" whenever
PawnIO is missing, as administrator too, and the card says why. The button reads "Run as admin for more
sensors", the administrator banner no longer says every sensor has full access, and Resource History's empty
chart names the driver too. Since 1.17.0.
- Hottest Core could show a distance instead of a temperature. With PawnIO installed, an Intel processor also
reports, for each core, how far it is below its maximum temperature, and the card took the highest of those
together with the real readings: a processor at 38 °C showed 62 °C, and Resource History's processor line never
dropped below that. Some first- and second-generation Ryzen processors report a fan-control value 10 to 27 °C
above the real temperature beside it, and the card showed that value. Only the cores' own temperatures are read
now, and Hottest Core names the core. Since 1.17.0.
- The background history queried every disk every 10 seconds while SysManager ran as administrator. It records
no disk temperatures, but every disk was asked for its readings before they were thrown away, also with the
window hidden. The disks are left alone now unless the Dashboard asks for them. Since 1.47.0.
Verify the download
Get-FileHash .\SysManager-v1.130.82.exe -Algorithm SHA256
Expected SHA256: C1AFDD79CA4CB463D703451C6A9D547813E3970ED6D7705282B47A02CDAFD039
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.82.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.82.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.