Skip to content

SysManager 1.136.18

Choose a tag to compare

@github-actions github-actions released this 30 Oct 18:55
· 173 commits to main since this release
f407f07

[1.136.18] - 2026-10-30

App Updates, Bulk Installer and the Uninstaller find winget again when SysManager is not run
as administrator.

Fixed

  • Without administrator rights, which is how SysManager starts, every winget call failed and the
    tabs said winget (App Installer) isn't available on this PC. SysManager looked for winget only
    in the App Installer's own folder, which only an administrator can list. App Updates and the
    Dashboard's app-update check sent you to the Store for an app already installed, Bulk Installer
    could not search or install, and the Uninstaller listed nothing. Without administrator rights
    winget now runs from your account's own shortcut to it, the one that runs when you type winget
    yourself; as administrator it still runs only from the App Installer's folder. Present since
    1.52.98.
  • When winget could not be started, Bulk Installer said why for an instant, then went on to fail
    every remaining app the same way and ended "Done. Installed: 0, Failed: N." with a "Bulk
    Install complete" notification. It now stops at the first app and keeps saying that winget is
    not available. Present since 1.57.3.

Verify the download

Get-FileHash .\SysManager-v1.136.18.exe -Algorithm SHA256

Expected SHA256: DCCB4427F5CE50E957B0B1076068BE1B588F88F7F4F9430236B1894BF25C00AF

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.18.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.18.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.