הורדת SysManager 1.131.4

[1.131.4] - 2026-10-28
Browser Cleaner and Deep Cleanup now see a link planted higher up in a folder's path, not just a link at
the folder itself — so an elevated Clean can no longer be redirected to delete somewhere else.
Fixed
- A link one or more folders above a cleanup root was not detected. Both features checked whether the
folder they were about to measure or delete was itself a link, but Windows resolves a link anywhere in a
path's parent folders before reporting anything about it — so a junction standing in for an ancestor
folder (several of the folders these features look in sit under a location any standard account can
write to) read as an ordinary, readable folder. The scan sized whatever was on the other side of that
link, an elevated Clean deleted there, and nothing said a link had been involved. The check now resolves
the whole path and compares it against where it actually leads, closing the same gap in the shared file
walk every destructive feature in SysManager goes through.
- A browser's own vendor folder, or Firefox's profiles folder, being a link was shown as if the browser
were simply not installed. Browser Cleaner's extension list and profile scan carried the same
last-segment-only check; a link higher up now shows the browser as unreadable, the same way a link at
the profile folder itself already did, rather than silently leaving it out.
Verify the download
Get-FileHash .\SysManager-v1.131.4.exe -Algorithm SHA256
Expected SHA256: DCC737BFB9074B6F47E00DFAB8543FC58D11C1C83354D4C76553D7D8E6185747
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.4.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.4.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.