Skip to content

SysManager 1.126.0

Choose a tag to compare

View all tags
@github-actions github-actions released this 08 Oct 19:07
· 150 commits to main since this release
v1.126.0
09673b3
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

[1.126.0] - 2026-10-08

The Services tab no longer calls a service "Critical" just because SysManager has not rated it. Those services, most of
the list, now show a grey Not rated pill, so the red one is back to meaning "this breaks Windows". What SysManager
will and will not do with them has not changed (#1512).

Added

  • Services has a Not rated filter chip with its count, for the services SysManager has no rating for.

Changed

  • Services: a service that is not one of the 48 SysManager has rated shows a grey Not rated pill instead of the
    red Critical one, and its hover says SysManager has not rated it and will not turn it off, rather than "Unknown
    service — treat as critical until verified". It is still refused for Stop and Disable, and the status line now says
    "SysManager has not rated … so it will not stop it" instead of calling it critical. The Critical chip counts only
    the services rated Critical, so its number drops from most of the list to 15 at most.
  • Windows Features: a feature SysManager has not rated shows Not rated instead of Caution, with a hover that
    says to look it up before turning it on or off. It can still be turned on or off, as before.

Fixed

  • Services: Windows Biometric Service and TCP/IP NetBIOS Helper, which the gaming advice calls safe to disable, are
    now rated (Caution and Safe), so Disable acts on them. Since 1.20.30, when Disable began refusing the services it had
    no rating for, it refused these two while its own advice said to turn them off (#2611).

Verify the download

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

Expected SHA256: FDB3F2DAD0FF6859493AE9B75DB10EA300CE7529CDD87D88CA37B9F65426D127

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

Assets 5
Loading