SysManager 1.113.3

[1.113.3] - 2026-09-24

If SysManager could not reach GitHub when it started, it then told you it had "checked recently" for
the rest of the day. The startup check runs at most once every 24 hours, and a check that failed was
starting that clock anyway — so a single launch with the network down left you with no version
information and a message saying there was no point looking again. Only a check that actually got an
answer starts the clock now.

Fixed

• A failed startup update check no longer uses up the day's one check. The timestamp was recorded as
  soon as the two calls came back, without asking whether they had come back with anything — so an
  offline launch spent the entire 24-hour allowance on nothing, and the next launch said "Checked
  recently. Use Check for updates to look again." That is the one message that is wrong in that
  situation: it says looking again is unnecessary when in truth nothing had been looked at, and the
  version on screen was blank. The recording is now conditional on the check having succeeded, so the
  next launch simply tries again. Failing to load the release-notes list deliberately does not block it —
  the version answer is what the 24-hour limit exists to protect, and the notes come back with Refresh
  without waiting out a day.

---

Verify the download

Get-FileHash .\SysManager-v1.113.3.exe -Algorithm SHA256

Expected SHA256: 2C72CDDF863CFF9FEEC3E15E3D7E6A9D8D3B369525B2C57BDC02103ED0E0D7E8

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.113.3.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.113.3.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.