Preuzmi SysManager 1.64.9 za Windows

[1.64.9] - 2026-08-12
Closing the Performance Mode tab in the middle of applying a tweak can no longer throw away the
saved settings that "Restore all" needs. Closing the Bandwidth Monitor mid-load no longer risks an
error on the way out.
Fixed
- Closing Performance Mode while a change was being applied could leave that change with nothing to undo it. Before touching any Windows setting, SysManager saves a snapshot of how things were, so "Restore all" can put them back. Closing the tab clears that snapshot — but it did so without waiting for a change that was still in progress, so in the moment between "saving your original settings" and "applying the new one", closing the tab could take the snapshot away from the very operation that was relying on it. The result would be a setting changed with no recorded way back. The tab now waits for any in-progress change before clearing anything, and an attempt to apply a change to a tab that is already closing is refused outright instead of going ahead unprotected.
- Closing a tab mid-operation could log an error on an otherwise clean exit. Eleven parts of the app take an internal turn-taking lock so two operations cannot run over each other. Six of them — the Bandwidth Monitor, Performance Mode, and the DNS, network-repair, speed-test-history and system-fix helpers — released that lock on shutdown without checking whether it had already been packed away, which reports an error during what is otherwise a normal exit. The other five already did this correctly; all eleven now behave the same way, and a new automatic check stops a twelfth from being added with the old pattern.
Verify the download
Get-FileHash .\SysManager-v1.64.9.exe -Algorithm SHA256
Expected SHA256: 177AD815E083789E7EB7C5096634283252AA49CD051AB9AC41818867A922B245
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.64.9.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.9.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.