Shkarko SysManager 1.114.54

[1.114.54] - 2026-10-01
Gaming Profile now ends game mode when the game closes while it is starting. Start can take many seconds,
and a game that closed in that time left game mode on until you pressed Stop. Game mode now ends at once and
puts your settings back, as it does whenever the game exits, and the tab says so.
Fixed
- Game mode stayed on until Stop when the game closed while it was starting. Start sets up the watch on the
game last, after the restore point, which can take many seconds, the snapshot and every change. A game that
closed in that time could not be found, or another program had been given its ID, and the session stayed on
with nothing watching for the game's exit.
- Start now ends game mode before it finishes, putting the settings back as the game's exit would have, and
says the game closed while game mode was starting. A setting that could not be put back is named, as after
Stop.
- A game that exits just as the watch is set up, the one case that was handled, now ends the same way. Its
session used to end after the tab had already announced that game mode was on.
- Present since v1.52.38, when Gaming Profile was added.
- A Start that changed nothing still watched the game. Starting again replaced that watch without letting it
go, so the first game's exit could end the second session. A Start that changes nothing now watches nothing.
Present since v1.52.38.
Verify the download
Get-FileHash .\SysManager-v1.114.54.exe -Algorithm SHA256
Expected SHA256: DE020841FBDA374FEB40C46147209B97C08C98F4813EAE6FA4B6ED25353E6A15
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.54.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.54.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.