Lataa SysManager 1.76.10

[1.76.10] - 2026-09-04
The "can be freed" and "in Recycle Bin" figures on the Cleanup tab could stop counting partway through a
folder, and could count files that live outside the folder they claim to describe. Both are now measured the
same way the cleanup itself works, so the number matches what pressing the button would actually free.
Fixed
- The Cleanup tab's size estimates stop under-reporting. Both figures walked their folders with a method
that gives up entirely the moment it meets one folder Windows will not let it open — so on most machines the
total stopped early and reported less than was really there, with nothing on screen to say so. They now use
the same walker the cleanup uses, which skips what it cannot read and keeps going.
- The Recycle Bin figure no longer counts files that are not in the bin. The old walk followed folder
shortcuts, and deleting a folder shortcut puts one in the Recycle Bin — so a single deleted shortcut could
add every file it pointed at, live data included, to the "in Recycle Bin" total. The new walker never follows
them.
- "Can be freed" no longer promises space Clean TEMP will leave alone. Since 1.76.8 the temp cleanup skips
the folder running programs unpack themselves into. The estimate did not, so it counted bytes the cleanup
would correctly refuse to delete. It now applies the same two exclusions.
Verify the download
Get-FileHash .\SysManager-v1.76.10.exe -Algorithm SHA256
Expected SHA256: D05FC402B4C8936DF88AE0A779E2F1A9B28C76215B1FA1125DA0EB5E8909A772
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. 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.76.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.76.10.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.