Pakua SysManager 1.114.41

[1.114.41] - 2026-09-29
Gaming Profile no longer leaves notifications muted after a game when SysManager cannot read its record of
your notification changes. Notifications could stay off after the game although you never touched them.
Fixed
- Gaming Profile: notifications come back after a game even when the Notifications tab's write count cannot
be read. "Silence notifications" mutes Windows notifications during a game and switches them back on
afterwards, unless you muted them yourself on the Notifications tab meanwhile. It tells the two apart by a
count that tab keeps of its own changes. A count that could not be read, when the game started or when it
ended, was taken as 0, which looked like a change you had made, so notifications stayed muted.
- A count that cannot be read is now unknown, and the profile then switches notifications back on, as it
did before the count existed.
- A mute you make during a game is still kept whenever the count can be read, including when it could not
be read at the moment you made it.
Present since the count was added in v1.75.10.
Verify the download
Get-FileHash .\SysManager-v1.114.41.exe -Algorithm SHA256
Expected SHA256: E698D78CE08ED804613C336639CED2EE402FE82991B5561B53715D9C26980D6B
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.114.41.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.114.41.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.