Λήψη SysManager 1.61.5

[1.61.5] - 2026-08-11
Two places where SysManager told you something that was not true: the tray warning that a
perfectly healthy drive might be failing, and Cleanup reporting that it emptied a Recycle Bin
Windows had refused to empty.
Fixed
- The tray could warn that a healthy drive was failing. SysManager reads disk health from two different places in Windows depending on what the machine offers, and the second one describes a good drive as "OK" rather than "Healthy". The background check only accepted the exact word "Healthy", so on those machines it treated every drive as a problem and showed "Disk Health Warning — reports status: OK. Consider backing up important data." every four hours: a warning that contradicts itself in its own sentence, over nothing. It now recognises what each source actually says, warns for the values that genuinely mean trouble, and stays quiet when it cannot read the status at all — inventing urgency from a value it could not read would be worse than saying nothing. Drives that really are failing still warn, including the abbreviated wording ("Pred Fail", "NonRecover") that Windows uses in the second source.
- Emptying the Recycle Bin reported success even when Windows refused. Windows reports a refused empty by returning a failure code rather than by raising an error, and Cleanup ignored that code — so if the Recycle Bin was open in Explorer or a file inside it was still in use, the status read "Done" and a "Operation finished successfully" notification appeared while the bin was still full. It now says plainly that Windows would not empty it, suggests why, and records it in the log. Deep Cleanup and the One-Click Tune-Up already handled this correctly; Cleanup was the one place that did not.
Verify the download
Get-FileHash .\SysManager-v1.61.5.exe -Algorithm SHA256
Expected SHA256: 6F112FD38252C5894841CA926228F4DDEBCA941FE789393ACFF1777178C182C5
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
Free code signing provided by SignPath.io, certificate by
SignPath Foundation. Team roles, the release-approval process
and the privacy policy are documented under Code signing
policy.
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.61.5.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.61.5.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.