SysManager 1.131.10

[1.131.10] - 2026-10-28

Privacy & Telemetry, Camera/Mic/Location, Notification Blocker and Scheduled Maintenance now change
your own account's settings when SysManager is elevated with a different administrator's password,
not that administrator's.

Fixed

• Elevating with a different administrator's password sent per-user changes into that
  administrator's profile instead of yours. "Run as administrator" on a standard account runs the
  elevated copy AS the administrator whose password was given — its own HKEY_CURRENT_USER, its own
  account. Nothing compared that account with the one actually signed in, so applying a Privacy &
  Telemetry switch, reading your own webcam/microphone/location history, muting a notification
  sender, or registering Scheduled Maintenance all read and wrote the administrator's profile while
  the tab reported it as applied to you. On the common family-PC setup — a standard account with a
  parent's administrator password — every one of those changes silently never reached the person who
  made them.
• SysManager now detects the mismatch and redirects these four to your own account's hive
  (HKEY_USERS\<your SID>, loaded for as long as you are signed in) instead, falling back to the
  administrator's own hive — logged, not silent — only on the rare failure to resolve or open it.

Performance Mode's Xbox Game Bar switch has the same gap and remains open, tracked on #2826, since it
needs a different fix shape (static methods rather than a constructor-injected registry root).

---

Verify the download

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

Expected SHA256: 7091B274F69457725A3385B91E2A229B2E1953978D964EA65BCA880F739A3252

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