Pakua SysManager 1.136.118

[1.136.118] - 2026-11-05
On Windows Update, drivers and feature upgrades get their pills on Windows in any language, and the history's KB column is filled in.
Fixed
- The Driver and Feature upgrade pills were decided by the English names of Windows Update's classifications and by
English words in the title. Windows Update names both in the display language, so on German, French or Romanian
Windows a driver or a feature upgrade got the plain "Update" pill, and, ticked like every other row, looked like
any other update. The pill now comes first from the classification's ID and the update's type, which are the same
in every language. Since the tab started reading Windows Update directly, in 1.18.0.
- Update history's KB column was empty on every row. It read KBArticleIDs, which only an update in a scan has;
PSWindowsUpdate keeps a history entry's number in KB. It reads that now, and the KB number in the title when
that is empty. On my PC, 21 of the 30 entries now show their number. Since the history first had a table, in
0.28.0.
Verify the download
Get-FileHash .\SysManager-v1.136.118.exe -Algorithm SHA256
Expected SHA256: 1A18E4E5D8FDB0B620A2989ACEA873AF4132BEF2816091F6C45FC5DAAEB4FD85
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.118.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.118.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.