Shkarko SysManager 1.136.119

[1.136.119] - 2026-11-06
On Windows Update, an install that is cancelled or stopped by an error still says how many updates went in and whether to restart, and no row is left saying "Pending…".
Fixed
- An install cancelled between two updates, or right after an update downloaded, ended as "Cancelled." alone: the
updates already installed went uncounted, and the notice that Windows needed restarting for them never came. It
says how many went in now, for example "Cancelled. Installed 1/2 before it stopped.", and the restart notice still
shows. Since the tab started installing through Windows Update directly, in 1.18.0.
- When Windows Update failed during an install, in the search the install starts with (offline, or a WSUS server
that cannot be reached) or between two updates, the status line read "WUA error: 0x…" and every row the install
had not finished kept saying "Pending…" or "Downloading…" until the next check. Those rows say "Not applied" now,
and the status line says how many went in before the error. Since 1.18.0.
Verify the download
Get-FileHash .\SysManager-v1.136.119.exe -Algorithm SHA256
Expected SHA256: 4906834D5C5E6F30D4642FB404CF638F5910E7E02AD2D61CE59FAE5B2A66F4A5
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.119.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.119.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.