Lataa SysManager 1.130.21

[1.130.21] - 2026-10-20
The Dashboard judges a drive the way System Health does, so a healthy SSD with normal wear no longer reads as
critical.
Fixed
- A healthy SSD with normal wear was called "Disk health critical" on the Dashboard. The health score took every
point of an SSD's wear, and points for warmth from 50 °C, off the drive's score, while System Health warns only from
90% wear or 70 °C. So a drive at 41% wear, with most of its rated endurance left and reported Healthy by Windows,
scored 59: the Dashboard showed the red critical alert, the health card asked for a backup, the overall score
dropped, and System Health called the same drive Healthy. Every tab now judges a drive the same way, the System
Report's disk line included, and the backup advice names the drive that needs it. Since the Health Score card was
added (0.37.0).
Verify the download
Get-FileHash .\SysManager-v1.130.21.exe -Algorithm SHA256
Expected SHA256: E39681D80F8446D5C5BDA134E80858AF426F273763AC0A80A69340F4E04AABE2
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.21.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.21.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.