SysManager 1.130.10 download

[1.130.10] - 2026-10-20
The temp cleanups leave alone what a system service unpacked into Windows' own TEMP folder, and Shortcut Cleaner no
longer calls a shortcut broken because the program it opens is installed on your other PC.
Fixed
- Cleaning TEMP as administrator could delete files a system service needed. Single-file .NET programs unpack
their libraries into a .net folder inside their TEMP folder, and the cleanups leave that folder alone because a
library unpacked but not yet loaded is not in use and deletes without complaint, breaking the program the next time
it needs it. Deep Cleanup's Temporary files, Quick Cleanup's Clean TEMP and the Quick Tune-Up also clean Windows' own
TEMP folder, which needs administrator rights, and there they left alone only your account's .net folder, not the
one a program running as the system unpacks into. The .net folder at the top of every TEMP folder they clean is
left alone now, as the Temporary files description already said. Windows' TEMP folder has been cleaned since 0.5.0,
and your own .net folder left alone since 1.75.26.
- Shortcut Cleaner could delete a working shortcut from your other PCs. Once OneDrive backs up your Desktop, which
Windows 11 offers by default, its shortcuts sync to every PC signed in to that account. A shortcut to a program
installed on only one of them has its program missing on the others, so there it was listed as broken, ticked, and
counted by the Quick Tune-Up, and deleting it removed it from every PC, including the one where it worked. A
shortcut in a folder OneDrive shares is not called broken because its program is missing here: it is left alone and
counted, and the status line says why. Since Shortcut Cleaner was added (0.32.0).
Verify the download
Get-FileHash .\SysManager-v1.130.10.exe -Algorithm SHA256
Expected SHA256: 8C8CE830DFAB5FD19AF04F3B4B990FFB70D80AED6B7CA04F7B1FB1F7C04403C2
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.130.10.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.130.10.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.