Lataa SysManager 1.131.9

[1.131.9] - 2026-10-28
Uninstaller's leftover search now protects a user folder moved to a drive root, refuses a link it
cannot fully verify instead of offering it, and stops widening what it offers when the list of
installed programs could not be read whole.
Fixed
- A user folder moved to the root of a drive protected nothing beneath it. Documents, Downloads
and the other user folders are never offered — but the comparison that enforces it could not match
anything below a drive root, so moving one of those folders to D:\ (a common choice on a second
drive) meant nothing on that drive counted as inside it any more, and a removed app's leftover
folder there could be offered ticked.
- A link to a network share, or one whose real location could not be read, was offered instead of
refused. The guard against a link above the candidate only refused when it could resolve the link
fully; either failure case — a share, or a path it could not read at all — let it through instead,
and the folder was then measured across the network and sent to the Recycle Bin, which a network
location does not have.
- An uninstall list that could not be read in full counted as "nothing else is installed." When a
whole registry key could not be read, a publisher folder or another app's install folder could be
offered as the leftover of the app just removed, because the list that would have refused it is the
one that failed to read. Now only the removed app's own install folder is offered when that happens;
everything else waits for a read that can be trusted.
Verify the download
Get-FileHash .\SysManager-v1.131.9.exe -Algorithm SHA256
Expected SHA256: D3A5887A8129FBB1F684CD1B43D0655CFACF5A3701172AE77BDCD463C9869D5C
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.9.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.9.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.