SysManager 1.75.26

[1.75.26] - 2026-09-02

Cleaning temporary files could delete part of another program while it was running, which usually showed up
later as that program failing to do something it had worked fine at before.

Fixed

• Temporary-file cleanup no longer deletes pieces of other running programs. Some programs, SysManager
  included, ship as a single file and unpack the parts they need into a shared folder inside your temp
  folder while they run. SysManager already knew to leave its own unpacked parts alone — it had learned
  that the hard way — but it only skipped its own, so everything belonging to every other program in that
  same shared folder was fair game. Deleting those does not usually fail loudly: the program keeps running
  on what it had already loaded and then breaks later, when it reaches for a part that is no longer there,
  with nothing to connect the failure to a cleanup that happened earlier. Both cleanups — the "Temporary
  files" category in Deep Cleanup and the temp step in One-Click Tune-Up — now leave that whole shared
  folder alone.
• The description of that category no longer promises more than it delivered. It said anything still in
  use is skipped automatically, which is only true of files a program is holding open. It now says that,
  and adds that the folder programs unpack themselves into is skipped entirely.

---

Verify the download

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

Expected SHA256: 319813198A5042EC48F457CEF3565BE680A6131A6C0E1B3F1089805942435E5A

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