Skip to content

SysManager 1.114.11

Choose a tag to compare

View all tags
@github-actions github-actions released this 28 Sep 13:13
· 222 commits to main since this release
v1.114.11
430d66c
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

[1.114.11] - 2026-09-28

Seven tabs now say before their first change that SysManager may turn System Protection back on. Their
automatic restore point does that when protection is off, and only the Restore Points tab and Performance Mode
said so.

Fixed

  • The automatic restore point no longer turns System Protection back on without saying so. Before the first
    change of a session, Windows Features, Tweaks Hub, Gaming Profile, Privacy & Telemetry, Preinstalled Apps,
    Edge/OneDrive Remover and Defender Tweaks try to create a System Restore point. Windows cannot make one while
    System Protection is off, so SysManager turns it back on for the Windows drive first. For someone who switched
    protection off to save space on a small drive, that is a lasting change, and none of these confirmations
    mentioned it. Each now says so, in the same words as the Restore Points tab and Performance Mode. It says it
    when SysManager is running as administrator and the session's one attempt is still to come, because at any
    other time nothing is changed. Present on Tweaks Hub since v1.51.0, on Gaming Profile since v1.52.38, and on
    the other five since v1.68.0.

Changed

  • Tweaks Hub's Apply no longer mentions a restore point it will not try. It said "SysManager will try to
    create a System Restore point first (when running as administrator)" every time, and now says it only when
    the attempt is still to come. Undo makes the same attempt, and now says so too.
  • Preinstalled Apps' removal confirmation no longer ends with "Continue?" after its opening question.

Verify the download

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

Expected SHA256: 7082286FC8360AAF49C8E1AE2E2FFB123B77BA326E49545A6E5E8B26878AB2EB

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

Assets 5
Loading