Lataa SysManager 1.127.1

[1.127.1] - 2026-10-09
SysManager no longer checks GitHub for a new version at startup when it cannot read whether you switched that
off. It went ahead as if the check were on (#2614).
Fixed
- About: when the setting "Check GitHub for a new version when SysManager starts" cannot be read, the startup check
does not run. Another program may have its file open, or the file may be damaged. The check used to run as if the
setting were on, so GitHub was asked even by someone who had switched it off. Now About says the setting could not
be read, the box shows clear, and Check for updates still works whenever you press it.
- Nothing is written over the setting, so it decides again once it can be read. A damaged one stays as it is, and
the check stays off, until you tick the box: that saves your choice and keeps the damaged file as
update-check.json.unreadable.
- With no setting saved yet, as on a first run, the check still runs.
- It had worked this way since the setting arrived in 1.58.0. 1.114.39 stopped the check from writing "on" back
over an "off" it could not read, but the check itself still ran.
Verify the download
Get-FileHash .\SysManager-v1.127.1.exe -Algorithm SHA256
Expected SHA256: AA1CE7E57B0D63A65019626E871E04DA94ADFE0B581AE205D5F59E69719403EB
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.127.1.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.127.1.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.