SysManager 1.76.6

[1.76.6] - 2026-09-03

A theme you build yourself in the appearance panel is now kept readable the same way the built-in ones are.
Before, it was the one kind of theme the app applied exactly as typed, so four unlucky colour choices could
leave text you could not read — with no way back except deleting a file by hand.

Fixed

• A custom theme now gets the same readability protection as a built-in one. Every built-in theme goes
  through a step that nudges its text until it stands out from the panels behind it. A custom theme skipped
  that step entirely and was applied exactly as typed, so white text on a white background was accepted. It
  goes through the same step now. Applying a custom theme also used to throw away the background-shade slider's
  position; it keeps it.
• Green and mid-grey backgrounds no longer get the wrong warning colours. Whether a custom background
  counted as dark was decided by adding its red, green and blue values together, which treats all three as
  equally bright when the eye does not. A pure green background was called dark, so the app installed the
  colours meant for dark backgrounds and its amber warning text landed on bright green — effectively invisible.
  Mid-grey had the same problem. Brightness is now measured the way the accessibility standard measures it.

---

Verify the download

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

Expected SHA256: 7F7FDEA555E59A7D645FF3E93298EE08B0559FA1E9EBD938A7F3530DC7F53FF1

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