Lataa SysManager 1.64.6

[1.64.6] - 2026-08-12
Closing a tab, or closing SysManager, now actually stops what that tab was doing. Scans, cleanups and
file shredding used to keep running in the background after you closed them.
Fixed
- Work carried on after you closed the tab or the app. Every tab that runs something you can wait on — a scan, a cleanup, a speed test, shredding files, the one-click Tune-Up — is supposed to stop when you close it. Behind the scenes, SysManager was releasing the "stop" signal without ever giving it, so 28 of those operations across 23 tabs simply carried on: file shredding kept overwriting files after you closed the window, Deep Cleanup and the browser cleaner kept deleting, a speed test kept using your connection, and the Tune-Up kept changing settings. Nothing was corrupted by this — the work was real work you had started — but it continued when you had every reason to think it had stopped, and it kept your PC busy after SysManager appeared to be gone. All of them now stop when you close the tab or quit, exactly as the Cancel button already did. A new automatic check makes sure a future tab cannot be added with the same mistake.
Verify the download
Get-FileHash .\SysManager-v1.64.6.exe -Algorithm SHA256
Expected SHA256: 50C4F51678EDA4B5D70ECE63AAE67B2F687714223D660EBFD7E67BFF82E762B4
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.64.6.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.64.6.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.