Λήψη SysManager 1.136.28

[1.136.28] - 2026-10-30
Game mode's record of your own settings can no longer be written over or lost.
Fixed
- After SysManager closed while game mode was on, pressing Start in Gaming Profile started a new
session over the old one. It took the leftover gaming settings for your own and wrote over the
record of the ones you had, so Stop put the gaming power plan, the reduced visual effects, the
paused search indexing and the silenced notifications back. Start now offers to revert the
leftover changes first, and starts nothing until they are back.
- Game mode saved its record of your settings only once every change had run, and an elevated
start waits up to 30 seconds for search indexing to stop after the power plan has changed.
Closing SysManager in that time, or a crash, left the PC on the gaming power plan with nothing to
put it back from. The record is now saved before the first change, and game mode does not start
when it cannot be saved. Both were present since Gaming Profile was added in 1.52.38.
Verify the download
Get-FileHash .\SysManager-v1.136.28.exe -Algorithm SHA256
Expected SHA256: 9CB1F65E1426B8060A46FD60C3BE109F9F82923DF8BDF45DB367FE81DCC3D387
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. Two checks
run on their own when SysManager starts: the version check against the GitHub Releases
API, at most once a day, and the Dashboard's app-updates alert, which asks winget. The
About tab can switch off either. Everything else that uses the network runs only when you
use 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.136.28.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.136.28.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.