Lataa SysManager 1.114.17

[1.114.17] - 2026-09-28
Quick Tune-Up no longer says "All good" about checks it could not run, and the health score no longer counts
an unread battery as new. Both now leave out what was not measured, and say so.
Fixed
- Dashboard → Quick Tune-Up: a check that could not run is named, not passed. When the disk, shortcut or
memory-and-uptime check failed, its field stayed at the value that means nothing wrong: no disk rows, no broken
shortcuts, 0% memory, an uptime of zero. So with none of them checked the card said "All good" and "memory and
disks look fine, and this PC has restarted recently".
- The card now says "Not checked this time: …" in place of that line.
- The headline reads "Some checks did not run", in amber, when nothing else was found.
- "All good" and the reassurance appear only when every check ran.
- A disk read that finds no disk at all counts as not checked. A system-info failure reported as a COM error
is now caught like the other WMI failures, instead of failing the whole Tune-Up after the clean-up had run.
Present since the Tune-Up was added in v0.36.0.
- Dashboard → health score: an unread battery is left out, not scored as perfect. Without administrator
rights Windows does not give a battery's design and full-charge capacities. Such a battery scored 100 and
counted for 15% of the overall figure, so a worn battery lifted the score as if it were new. It is now left
out of the weights, as a desktop's is, and recorded as not read. A battery whose wear was read counts as
before. Present since v0.48.23.
Verify the download
Get-FileHash .\SysManager-v1.114.17.exe -Algorithm SHA256
Expected SHA256: 3B351EC7B1C169BF4E3B3E684965B4D8C39767A4584D5624E9B4114E5FD0D608
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.114.17.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.114.17.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.