Lataa SysManager 1.66.3

[1.66.3] - 2026-08-24
Gaming Profile and Performance Mode can no longer trip over each other. They change the same two
settings — the power plan and the visual-effects switch — and each writes down "how you had it" before
changing anything. Start one while the other is mid-change and the note it takes down is the other one's
change, so restoring later put your PC somewhere you had never been.
Fixed
- Gaming Profile now waits for Performance Mode, and vice versa. Starting a game profile while a
Performance Mode change is running says plainly which one is busy instead of starting anyway. It takes
that check before reading your current settings, not just before changing them — reading them at
the wrong moment is what recorded the wrong "original" and could leave your PC on a gaming power plan
after everything was supposedly restored.
- Undoing is never refused. If a game exits while another change happens to be running, the
optimizations are still undone. Leaving your PC tweaked because something else was busy would be worse
than the clash being avoided, so the undo goes ahead and says so in the log. The same applies to the
leftover-session cleanup that runs after a crash.
- The README no longer overstates the protection. It said the lock covers every tab that changes
system state and then omitted Gaming Profile, which was the one tab it did not cover. A test now keeps
that list honest in both directions.
Verify the download
Get-FileHash .\SysManager-v1.66.3.exe -Algorithm SHA256
Expected SHA256: 17CEFC1BBA2292D61A87DD78AC7965871C7CC25A902002228260812142A51058
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.66.3.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.66.3.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.