SysManager 1.93.0: prenos za Windows

[1.93.0] - 2026-09-11
Deep Cleanup can now find the biggest file on a PC that has blue-screened. When Windows crashes it
writes out MEMORY.DMP, sized to how much RAM the machine has — routinely several gigabytes, and often
the single largest reclaimable file on the drive. Deep Cleanup had no bucket for it, nor for the
Minidump and LiveKernelReports folders beside it. It now does, and it is deliberately never ticked
for you: those dumps are the only record of why the machine crashed, so removing them ends any
investigation into it. The second addition is the thumbnail cache — the previews Windows keeps so folders
open quickly, whose clearing is the standard fix for thumbnails that come up blank or show the wrong
picture.
Added
- Blue-screen memory dumps as a bucket of its own: MEMORY.DMP, Windows\Minidump and
Windows\LiveKernelReports. Offered with its size and file count like every other bucket, never
pre-selected, and it needs administrator to delete — which the tab now says.
- Explorer thumbnail & icon cache, scoped to exactly thumbcache_*.db and iconcache_*.db. That
folder is Explorer's own working directory and also holds the jump lists that are your recent-files
history, so nothing else in it is counted, and nothing else in it is deleted.
Changed
- A cleanup bucket can now name a single file rather than a folder, and can restrict itself to files
matching a pattern. Both the scan and the delete read the same restriction, so the size shown is by
construction the size removed.
- The Deep Cleanup elevation notice names six categories instead of five, the dumps being the sixth.
Verify the download
Get-FileHash .\SysManager-v1.93.0.exe -Algorithm SHA256
Expected SHA256: 891CAA1625E0126B688ECA19A0FAD99733A2DB8FFB1B191CFA4F67CA25CB930A
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.93.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.93.0.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.