Lataa SysManager 1.128.4

[1.128.4] - 2026-10-10
About's release notes say GitHub could not be reached when the list arrives but cannot be read, instead of showing
an error (#2663).
Fixed
- About: a release list that cannot be read is a failed load, not an error. Reading the list of recent releases
failed in three ways the code did not name: a connection that dropped part way through the reply, and a compressed
reply, gzip or Brotli, that did not decompress. Each one escaped, so Refresh or F5 showed the "SysManager error"
dialog, and at startup the notes stayed blank with nothing saying why. The list now treats all three as it treats an
unreachable server: the notes say "Could not reach GitHub", and Refresh tries again. The update check already did,
and both now read the ways a reply can fail from one list, so they cannot drift apart again. This had been so since
0.28.17, when a catch of everything there was narrowed to three types.
Verify the download
Get-FileHash .\SysManager-v1.128.4.exe -Algorithm SHA256
Expected SHA256: E865BCE128CDA3032AFBCA2F738E87687D28BD44CBB804694BCD1BAC6F6600A9
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.128.4.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.128.4.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.