SysManager 1.109.0

[1.109.0] - 2026-09-15

"Large Files" is its own tab now, next to Disk Analyzer and Duplicate Finder. It used to sit at the
bottom of Deep Cleanup, underneath a list of things to tick and delete — which made it hard to find and
easy to mistake for part of the deleting. It is not: it only ever shows you which files are biggest, and
it cannot delete anything even with administrator rights. All three tabs in Storage & Files now answer the
same question — where did my disk space go? — and none of them removes a thing. Deep Cleanup keeps doing
exactly one job: listing what is safe to remove, and removing what you tick.

Changed

• Moved "Large files finder" out of Deep Cleanup into its own "Large Files" tab in the Storage & Files
  group, between Disk Analyzer and Duplicate Finder. Same scan, same locations, same read-only results with
  "Show" and "Copy" — it just has room of its own and a name you can find.
• Deep Cleanup's description now says what the tab actually does, and points at Large Files for the
  other question. Its own list of what to clean also got the missing "nothing scanned yet" message, so
  before your first scan the page explains itself instead of showing a heading over blank space.
• Large Files has its own status line and its own Cancel, rather than sharing Deep Cleanup's.

---

Verify the download

Get-FileHash .\SysManager-v1.109.0.exe -Algorithm SHA256

Expected SHA256: D1A7FB512EBDA76CD389B41257B71AFF937F4C10C8738C9B6F4FBC41FB4D2AA2

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.109.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.109.0.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.