SysManager 1.114.53

[1.114.53] - 2026-09-30

Gaming Profile now acts only on the game you picked. If the game closed after the list was read and Windows
gave its process ID to another program, Start game mode changes nothing and says the game had already closed,
and neither raising, restoring nor waiting for the game reaches that program.

Fixed

• Gaming Profile's game mode could raise, restore and wait for a program other than the game you picked. Like
  File Lock Detector and CPU Core Affinity before 1.114.52, it acted on the game's process ID alone, taken from a
  list that can be minutes old, and Windows gives a closed process's ID to the next one started.
  • Start game mode checks that the game is still the process that was listed before it changes anything. If it
    has closed, nothing changes, the tab says so, and the list is refreshed.
  • Raising the priority, pinning the cores and putting both back when game mode ends pass the game's start
    time with its ID, so a program that has since been given the ID is left alone. A session can last hours, and
    by the time it ends the ID may belong to another program.
  • Auto-revert watches the process only while it is still the game. Watching whatever had the ID could end game
    mode when an unrelated program exited. A game Windows will not let SysManager check is not watched, and game
    mode stays on until Stop.
  • A refresh keeps the selected game only if it is the same process.
  • Present since v1.52.38, when Gaming Profile was added.

---

Verify the download

Get-FileHash .\SysManager-v1.114.53.exe -Algorithm SHA256

Expected SHA256: D3DB8419B1C74C3CA97E789305031964B7A68BFD4C9EB67F7D11686C2106F188

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.53.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.53.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.