SysManager 1.136.12

[1.136.12] - 2026-10-30

Without administrator rights, Defender Tweaks now says so before you change anything, instead of
telling you to turn off Tamper Protection.

Fixed

• Every Defender change needs administrator rights, but reading Defender's status does not, and
  on a default install that read says Tamper Protection is on. So without them, each change asked
  you to confirm, tried for a restore point, failed, and then blamed Tamper Protection and told
  you to turn it off in Windows Security. Turning it off changed nothing. PUA protection,
  Controlled Folder Access, adding an exclusion and removing one now stop first, before the
  folder picker or any confirmation, and say they need administrator rights, as App Blocker and
  DNS & Hosts already did. The tab has done this since it was added in 1.39.0.
• With administrator rights, a change Windows did not apply while Tamper Protection was off was
  put down to missing administrator rights. It now says Windows did not apply it.

---

Verify the download

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

Expected SHA256: 4404C21D849F33AB1DBE19445E7D760D20158BF33B0AA746AB8730768B53E944

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