SysManager 1.75.4

[1.75.4] - 2026-08-27

The in-app updater could not actually install an update: clicking Install closed SysManager and
nothing came back, and Roll back could quietly stop being offered. Both are fixed, so the updater
works end to end.

Fixed

• "Install update" now replaces the running build instead of doing nothing. The updater only
  agreed to write over a file whose name matched the running program's, but the program doing the
  writing is the freshly downloaded SysManager-<newversion>.exe while the file being replaced is the
  older build — two different names, so the check could never pass and every update was silently
  refused after the app had already closed. It now identifies a SysManager build by the product stamp
  Windows keeps inside the file, which is the same across versions and survives you renaming the
  portable .exe. Downloading and installing an update now completes and relaunches.
• Roll back no longer loses its safety copy when you download a newer update. Cleaning up old
  downloads deleted the checksum file that Roll back needs to confirm the saved build is intact.
  Because that confirmation refuses to proceed without the checksum, Roll back would stop being
  offered after the next download. The checksum is now kept alongside the saved build.

---

Verify the download

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

Expected SHA256: 6503005E10622B5A835E92C6568A3A072987C63C37F49B9372FA8203AA3274AF

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