Last ned SysManager 1.114.15

[1.114.15] - 2026-09-28
Closing SysManager no longer cuts off a repair or an install without warning. While a repair, an install, a
clean-up or another long job is still running, every way out now names it and asks first.
Fixed
- Every exit asks first while something is still running. Closing SysManager cancels whatever its tabs are
doing, and a cancelled repair or install is ended part-way: a DISM repair, a Windows feature being turned on,
a Windows Update install. Depending on timing it could instead be left running with nothing watching it, and
the next launch did not know. No exit said so. Now each of these names what is running and asks:
- closing the window;
- Exit in the tray menu, which also brings the window back first, so the question is not missed;
- Run as administrator on any tab, before the elevated copy starts;
- About → Install and About → Go back to the previous version.
When nothing is running, none of them asks anything new. SysManager already tracked what was running, for
the "already running" refusals, but no exit read it. Present since v0.48.15, when closing began disposing
every open tab.
- About → Install asks before it closes SysManager. It started the new version and closed half a second
later with no confirmation at all, unlike going back to the previous version, which always asked. It now
names the version, says SysManager will close and reopen, and asks. Declining leaves the checked download
ready to install. Present since the one-click install was added in v0.40.1.
Verify the download
Get-FileHash .\SysManager-v1.114.15.exe -Algorithm SHA256
Expected SHA256: E66D5D0893710E50EF83C5337FD6A387454AA0F3B6E2CD97CA305C043FB742E0
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.114.15.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.114.15.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.