Lataa SysManager 1.123.2

[1.123.2] - 2026-10-08
Deep Cleanup now finds the Delivery Optimization cache, and empties it the way Windows does. It looked in a
folder current Windows no longer uses, so the bucket always read 0 bytes.
Fixed
- Deep Cleanup: the Delivery Optimization cache always read 0 bytes (#2602). The bucket looked only in
C:\Windows\SoftwareDistribution\DeliveryOptimization\Cache, which current Windows 10 and 11 do not have. The
cache is in the Network Service profile,
C:\Windows\ServiceProfiles\NetworkService\AppData\Local\Microsoft\Windows\DeliveryOptimization\Cache, and the
bucket now reads its size there, and in the old folder on a Windows that still uses it. Present since 0.5.0, when
the bucket was added.
- It is emptied through Windows' own Delete-DeliveryOptimizationCache rather than file by file, because the
files belong to the service that keeps them. Files a download in progress is using are kept, and the total freed
counts only what actually went.
- If Windows refuses, or has no such command, the result says so for that bucket, and SysManager deletes nothing
there itself.
Verify the download
Get-FileHash .\SysManager-v1.123.2.exe -Algorithm SHA256
Expected SHA256: D82EA780AAB50EE8DFCAA395794B3390CEC705370686E73B016A873948523DD1
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.123.2.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.123.2.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.