SysManager 1.81.1 aflaai

[1.81.1] - 2026-09-09
Custom colours could make the app unreadable, and there was no way back. If you set a dark background with a
light panel colour, the text ended up white on a white card — and because your colours are saved and restored
every time the app starts, an unreadable theme stayed unreadable. There is now a "Reset to default theme"
button in the Appearance menu, and a panel colour that leaves no room for readable text is nudged until it
does.
Fixed
- Custom themes no longer produce unreadable panels. Background and Surface are separate values, so they
could sit on opposite sides of light and dark. The correction that keeps text legible only measured the text
against the Background, so a near-black Background with a near-white Surface walked the text toward white
and put it on a white card at 1.04:1 — and cards, rows and panels are most of what the window shows. The
panel is now nudged toward the background until the text this mode produces can be read on it, measured at
every position of the background-shade slider. The twelve built-in themes are untouched: their surfaces sit
near their backgrounds by design, and a test asserts the correction leaves all of them exactly as they were.
Added
- "Reset to default theme" in the Appearance menu. Custom mode was the only setting in the app with no
undo. The only way out of a theme you could not read was deleting a file in %AppData% — which the person
this app is written for will never find. The button restores the shipped dark theme and the default
background shade, and it survives a restart. No confirmation dialog, deliberately: someone reaching for it is
probably looking at a screen they cannot read, and the action changes nothing they cannot set again.
Verify the download
Get-FileHash .\SysManager-v1.81.1.exe -Algorithm SHA256
Expected SHA256: E3E8AB1EE2A2248A8EF798472469AC509D7A0B2F1DD0CF128E48EA81593FA78D
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.81.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.81.1.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.