Lataa SysManager 1.101.2

[1.101.2] - 2026-09-14
System Health no longer forgets which drives you ticked. Refreshing the page — pressing F5, or the
Scan button — rebuilt the drive list and silently put the tick back on C:, throwing away whatever you had
chosen. So if you unticked C: and ticked D: because D: was the one you wanted checked, then refreshed,
"Run chkdsk on selected" ran a long disk check on C: instead. Nothing on screen said your choice had been
discarded. Your selection now survives a refresh, including having deliberately unticked everything.
Fixed
- The drive selection on System Health is preserved across a refresh. C: is still ticked by default, but
only the first time the list is built, when there is nothing to preserve.
- Unticking every drive is honoured rather than treated as "nothing chosen yet" and reset to C:.
- A drive that appears between refreshes — a USB disk plugged in — stays unticked, since it was never
chosen.
Verify the download
Get-FileHash .\SysManager-v1.101.2.exe -Algorithm SHA256
Expected SHA256: 5AEBE15D845B1DC0B1FD94915B1C98FE1B118492C06BF90DC6CFF3ADDCBBF0DC
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.101.2.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.101.2.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.