SysManager 1.113.15 download

[1.113.15] - 2026-09-25
winget's results now say what actually happened. Most of the codes winget reports were described with
another code's sentence, so a download that did not match read as "No applicable update found", and the
Bulk Installer counted an app that was already installed as a failure.
Fixed
- App Updates, Dashboard, Bulk Installer: winget's result codes get the right sentences. Seven of the
nine codes App Updates translated carried a neighbouring code's sentence. A download that did not match
what winget expected read as "No applicable update found", a command that needed administrator as
"Cancelled", and an update the user cancelled as "App is running". The Bulk Installer called the same
hash mismatch "cancelled". Each sentence is now on the code winget uses for it, and the numbers are
written in one place, beside winget's own names, with a test pinning each one to the value winget
defines. Present in App Updates since v1.46.0, and in the Bulk Installer since v1.57.3.
- Bulk Installer: an app that is already installed is not a failed install. winget turns an install of
an installed app into an upgrade, which ends with "no applicable update" when nothing newer applies. The
row read "Failed — No suitable installer was found for this app". It now reads "Already installed", and
the summary counts it on its own. Counted as a failure since the tab was added in v1.2.0.
- Bulk Installer, Uninstaller: winget's own failure codes are explained, and shown in hex. A failed
installer or uninstaller ends with winget's own result code, and the installer's code is only printed.
Those codes had no sentence, so the fallback printed them as signed decimals such as "-1978335184". The
common ones now have a sentence, and any other winget code is shown in hex. The Uninstaller has shown
the decimal since v0.12.2.
Verify the download
Get-FileHash .\SysManager-v1.113.15.exe -Algorithm SHA256
Expected SHA256: B64AB6041E869ADBD0149FE387B7F789F537B0142DC494376A0687B5ED1E9EA9
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.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.113.15.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.