SysManager 1.112.7

[1.112.7] - 2026-09-23

Shortcut Cleaner called a shortcut broken when it simply could not reach the target. Unplug a USB stick
and every shortcut to a file on it was listed as pointing at "a program you have already removed" — ticked
for deletion, because every row in that list arrives ticked. The same for a network folder that was not
answering, a BitLocker drive still waiting for its password, and a folder this user has no permission to
read. Windows answers "no" to all four the same way it answers "that file is gone", and the tab believed it.

Fixed

• "Broken" now means the scan proved the target is gone. A target it could not reach is left alone and
  counted, rather than listed. The four ways to be alive and read as removed: a drive that is not attached, a
  UNC path whose server is asleep, a locked BitLocker volume, and a path the current user cannot look at —
  which is the everyday one, since this tab works without administrator rights.
• A network target is never called missing. An absent share and a sleeping NAS cannot be told apart
  without waiting out a network timeout for every shortcut, and "Recent Items" is one of the scanned
  locations — so a PC that has ever opened a file from a share had a list full of these. A share that answers
  is still recognised as present; only the failure is treated as undecided.
• "Your system is clean" is no longer said when the scan could not see everywhere. With unreachable
  targets, an empty list now reads "No broken shortcuts confirmed", followed by how many were left alone and
  why — a drive not plugged in, a folder not answering, or somewhere without permission to read.
• One Click Tune-Up no longer counts them either. Its card reported the total the scan looked at, so a
  machine with an unplugged drive was told it had broken shortcuts it did not have.

---

Verify the download

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

Expected SHA256: 480AB1250A0FEA699F2D4DC0D7B2737C22787B35835C0E8643B294EBC19CE613

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