Sækja SysManager 1.136.11

[1.136.11] - 2026-10-30
Defender's scan exclusions can no longer cover a whole drive, the Windows folder or your own
files.
Fixed
- The exclusion check accepted any rooted path without wildcards, and C:\ is one. The folder
picker offers a drive, so one confirmation turned off scanning for the whole system drive, and
the Windows folder, Program Files, Users, your own folder or Downloads were as easy. Refused
now, with the reason on the status line and before any confirmation: a whole drive or network
share, the Windows folder and anything in it, and a folder that is or holds Program Files,
Program Files (x86), ProgramData, the Users folder, your own folder, Documents, Desktop,
Downloads, Pictures, Music, Videos or your temp folder. A folder inside them, such as one game's
folder in Program Files, is still allowed. C: and \Windows, which are rooted but mean
"wherever the current folder is", are refused too. The tab and the service share the one rule,
and the tab adds only that the folder must exist.
Verify the download
Get-FileHash .\SysManager-v1.136.11.exe -Algorithm SHA256
Expected SHA256: 90EB2F9999DC52783976F65CA0D0806069DA3C313BB2D546DF3CAE9CC66E8F8E
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.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.136.11.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.