Pakua SysManager 1.66.2

[1.66.2] - 2026-08-24
Turning notifications back on while a Gaming Profile is running now sticks. Gaming Profile and the
Notifications page are two switches wired to the same setting, and when the game exited the profile put
its own version back — silencing notifications you had just deliberately switched on.
Fixed
- Gaming Profile no longer overrules a notification change you made yourself. When a profile ends it
restores the notification setting only if it is still the one the profile applied. If you changed it
meanwhile — from Privacy & Security → Notifications, which is the very same switch — your choice is
kept and the profile leaves it alone. Everything else about the restore is unchanged, including putting
an explicitly-on setting back exactly as it was rather than merely "not off".
- The two features now share one definition of that setting. The registry location was written out
twice, word for word, in two different services that both wrote to it, with neither aware of the other
— so a correction to one would silently not apply to the other. There is now a single owner, and a test
refuses any registry location that is spelled out in more than one place, which is the class of mistake
rather than this one instance of it.
Verify the download
Get-FileHash .\SysManager-v1.66.2.exe -Algorithm SHA256
Expected SHA256: F7C52E5F1141A6BC29B6503FAF7438BA158862EC60D730F740C610C15FD9BF0C
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.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.66.2.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.