Λήψη SysManager 1.127.6

[1.127.6] - 2026-10-09
After SysManager closes with game mode on, it now asks at the next start whether to put game mode's changes back,
not only once Gaming Profile is opened (#2592).
Fixed
- Gaming Profile: a game mode session left on by a crash is offered back when SysManager starts. The question that
puts back the power plan, visual effects, paused search indexing and silenced notifications was asked only by
Gaming Profile, and that tab is built the first time it is opened. So after SysManager crashed, or was ended from
Task Manager, during game mode, those changes stayed applied until someone opened the tab or found the row on Undo
Changes. The same question now comes once the Dashboard has loaded, or when Gaming Profile is opened if that comes
first, and only once a run. A yes puts the changes back and says what was put back. The question had waited for
the tab since game mode arrived, in 1.52.38.
Verify the download
Get-FileHash .\SysManager-v1.127.6.exe -Algorithm SHA256
Expected SHA256: 74C90FD45EC64E61E401A5A45C5624545A6CA02F176EB8C402C19A3B5E495A22
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.127.6.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.127.6.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.