[1.75.5] - 2026-08-27 Tune-Up's temp cleanup was reaching into SysManager's own working files. That could make a perfectly clean run report errors, and in the worst case stop a feature working until you restarted the app. Fixed

• Cleanups no longer sweep the folder SysManager is running out of. Because the app ships as a single file, Windows unpacks part of it into your temp folder while it runs, and both temp cleanups — Tune-Up's and Deep Cleanup's "Temporary files" — walked temp without knowing to leave that alone. Files the app had open refused to delete and were counted as errors, so a cleanup could report failures it caused itself. Files it had unpacked but not opened yet were deleted for real, which could break a feature later in the same session — the per-app bandwidth view was the most likely one, since it loads its extra components only when you start it. Both cleanups now skip that one folder and nothing else, so everything they used to remove is still removed. Verify the download Get-FileHash .\SysManager-v1.75.5.exe -Algorithm SHA256 Expected SHA256: 917A6A8239F2D1763DA3595EF975833DD8D8B9B76C421A82CF456CCCC101831D 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.5.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.5.sbom.json, a CycloneDX inventory of every dependency resolved for this build.