SysManager 1.130.16: prenos za Windows

[1.130.16] - 2026-10-20
Windows Update keeps the updates you unticked when it lists them again, and System Fixes says why a repair
stopped.
Fixed
- Listing updates again ticked every update you had unticked. Every scan shows its updates as new rows, ticked,
so List updates, F5, or a look at the history followed by List updates ticked again an optional driver or a
feature update you had unticked, and Install selected then installed it. After an install, the next list held only
the updates you had left out, all ticked again. What you untick now stays unticked across a rescan; only an update
the scan has not shown before starts ticked. Since updates could be ticked one by one (1.1.0), and with F5
since it lists updates (1.127.10).
- A repair that stopped said "see the output for details" over an empty console. Reset Windows Update and
Reinstall WinGet stop with a reason of their own, such as that App Installer is not installed, and that reason
reached neither the console nor the log. It is shown in the console and on the status line now, and logged. Since
System Fixes was added (1.26.0).
Verify the download
Get-FileHash .\SysManager-v1.130.16.exe -Algorithm SHA256
Expected SHA256: 2BBA2510DE3649D91839B577E2A1BB7F7D1BF021F184ECB167E15A25687B7773
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.130.16.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.130.16.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.