Last ned SysManager 1.136.100

[1.136.100] - 2026-11-03
Turning a Privacy & Telemetry switch off puts back what the setting held before.
Fixed
- Turning a Privacy & Telemetry switch off did not put back what the setting held before SysManager first changed
it. A policy you had set yourself, the required diagnostic data level through Group Policy or another tool for
example, was gone after turning the switch on and off again. SysManager now keeps a copy of what each setting held
before its first change, and turning the switch off puts that back, with its own kind of value, removing the value
only when there was none. A setting only an administrator can change gets back only a value it is known to take,
because the copy is a file in your own profile. A setting changed before this version has no copy, so turning it
off removes the value, as before. From 1.5.0 turning a switch off wrote the opposite value, and from 1.52.12 it
removed the value.
- When that copy cannot be saved, the switch is not changed, and when it cannot be read, the setting is not changed
back; Apply says which, rather than that they need administrator rights. A write Windows refused while SysManager
runs as administrator is no longer said to need administrator rights either.
Verify the download
Get-FileHash .\SysManager-v1.136.100.exe -Algorithm SHA256
Expected SHA256: 904A16C33F700F9D7D23A7A33462A4367688D413C0DF8E16CFBAA281F87019F9
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.100.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.100.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.