SysManager 1.136.92 download

[1.136.92] - 2026-11-02
Bulk Installer's search and installed check, and the Dashboard's app update checks, each read only their own winget output.
Fixed
- Bulk Installer's installed check and its winget search kept every line winget printed while they ran, their own
and any other run's, and the tab starts the check as it opens. A search before the Installed badges appeared could
mark a searched app as installed, or list installed programs that did not match, and a search during an install
read the install's progress as results. Each now reads only what its own run printed. The installed check also
accepts winget's source agreements, as every other winget call here does: on a profile that had not accepted them
it failed, and no app was ever marked as installed. The mixing was there since the two moved onto one runner in
1.52.92, and the missing agreements since the installed check came in 1.11.0.
- The Dashboard's app update alert, Scan system and Update All Apps read winget's upgrade list the same way, and
none waits for the others, so pressing one while another was still reading could give the alert the wrong count,
or make Update All Apps skip apps, or upgrade one twice and report a failure. Each reads its own list now. This
was there since the alert read the list through the shared service in 1.52.2.
Verify the download
Get-FileHash .\SysManager-v1.136.92.exe -Algorithm SHA256
Expected SHA256: 8504297BC1305277DBB465768704641EB6B04E9F361B11DA7DE872DB8C24F673
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.92.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.92.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.