Baixar SysManager 1.94.0 para Windows

[1.94.0] - 2026-09-11
Quick Cleanup can now reclaim the several gigabytes Windows keeps in its component store — and it tells
you the number before it touches anything. WinSxS is where Windows stores the older versions of its own
components, and on a machine that has been updated for a few years it routinely holds five to ten
gigabytes. It is also where the free editions of the mainstream cleaners find their biggest headline
figure, and they generally remove it on a single click without saying what it costs. "Check component
store" runs a read-only analysis and reports what Windows itself considers reclaimable; only then does
"Clean up component store" become clickable, and only behind a confirmation that states plainly what you
give up: after a cleanup, updates already installed can no longer be uninstalled.
Added
- Check component store — read-only DISM /AnalyzeComponentStore, reporting the size Windows reports
and whether Windows recommends a cleanup. "No cleanup needed" is a real answer and is shown as one,
rather than leaving a button that would spend half an hour reclaiming nothing.
- Clean up component store — DISM /StartComponentCleanup, disabled until an analysis has recommended
it, confirmed before it starts, and recorded in the activity log. /ResetBase is never used: it
reclaims a little more and permanently discards update uninstallation, which is not a trade a cleanup
button may make for you. A test makes it impossible to add by accident.
Changed
- The Repair Windows description now covers all four operations, including what cleaning up the component
store costs.
Verify the download
Get-FileHash .\SysManager-v1.94.0.exe -Algorithm SHA256
Expected SHA256: BAE4D399FABF627FB64AFD24B02DBDEFA5B708ADAFDB778314C8146E28E04EB6
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.94.0.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.94.0.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.