Lataa SysManager 1.113.12

[1.113.12] - 2026-09-24
The Uninstaller no longer says an app is removed while its uninstaller is still open. Some uninstallers
hand over to a second window and return at once, so SysManager used to report "Removed" before anything
had been removed — and even if you then cancelled. It now checks that Windows no longer lists the app.
Fixed
- Uninstaller: an app is "Removed" only once Windows stops listing it. For apps uninstalled through
their own uninstaller (those without a winget package), SysManager waited for the uninstaller it
started and trusted its result. Uninstallers built with NSIS, a common installer maker, copy themselves
to a temporary folder, start the copy and return straight away. The row said "Removed", the app left
the list and the batch counted it, while the uninstall wizard was still open — or, for a silent
uninstall, still running. Cancelling the wizard left the app installed and reported as removed. Now,
when Windows still lists the app after its uninstaller returns, the row says the uninstaller may still
be open, the app stays on the list, and the summary says how many are still installed. Present since
local app support was added in v0.44.0.
Verify the download
Get-FileHash .\SysManager-v1.113.12.exe -Algorithm SHA256
Expected SHA256: 571E9B5B42C651B259F0C7C30294826006B76014CB233D49516847559D5E48F9
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.113.12.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.113.12.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.