SysManager 1.136.162 download

[1.136.162] - 2026-11-10
Removing what an uninstall left behind checks again what is installed by then, so the folders and settings of an
app you installed again since are kept.
Fixed
- The Left behind card stays until it is dismissed, so an app can be installed again, or another app into one of the
listed folders, before Remove ticked… is pressed. The removal checked each folder's location and links again and
nothing else, so the install folder, the AppData folder and the settings key of an app installed again since went
to the Recycle Bin or were deleted. Every item is now held to the search's rules again, against what Windows lists
as installed at that moment: nothing an installed app lives in, inside or around; nothing left by an app of the
same name that is installed again; and nothing found by a name an installed app answers to. While the list of
installed programs cannot be read whole, only the install folder can go, as in the search.
- Just before a folder goes, it is walked again for links inside, and that check read a walk it had not finished as
"no link". A folder inside that SysManager could not open was skipped, and a Cancel during the walk ended it early;
either way the folder went to the Recycle Bin with part of it never looked at. A folder the walk cannot list all
the way through is now neither offered nor removed, and a Cancel during the check stops before that folder.
- A folder refused by two of the searches was reported once by matching the start of the sentences already written,
which also matched another folder whose name starts the same way: once "Acme Notes" was refused, the refusal of
"Acme" was never shown. Each refusal is now kept by the folder's own path.
Verify the download
Get-FileHash .\SysManager-v1.136.162.exe -Algorithm SHA256
Expected SHA256: 85BF176E8EFFB23BEFAAD55D6DE0198E24F704819E647CAA25C3202041C2E06E
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. Two checks
run on their own when SysManager starts: the version check against the GitHub Releases
API, at most once a day, and the Dashboard's app-updates alert, which asks winget. The
About tab can switch off either. Everything else that uses the network runs only when you
use 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.136.162.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.136.162.sbom.json, a CycloneDX inventory of
every dependency resolved for this build, and THIRD-PARTY-NOTICES.txt, the
licenses and notices of the open-source components the exe carries, which About
also opens from the exe itself.