Λήψη SysManager 1.76.7

[1.76.7] - 2026-09-03
Two things that went wrong in yesterday's last two updates. A theme you built yourself drifted a little every
time you started the app, and the Volume Control output picker went back to naming a device it had not actually
read, about ten seconds after you opened the tab. Both are fixed.
Fixed
- A custom theme no longer drifts on every restart. The app saved the theme after applying its
readability adjustments, then read that adjusted version back as your starting point the next time — so each
launch adjusted an already-adjusted theme. With the background-shade slider off centre the panels crept
lighter or darker every time; even with the slider untouched the text colour walked, a little further on each
start. It now saves the colours you actually chose. If your custom theme has already drifted, re-picking your
colours once will fix it for good.
- The output picker in Volume Control stops re-claiming a device it never read. 1.76.4 made the picker say
"Choose a device" rather than guessing your default, because Windows does not report which device an app is
using. But the app re-reads the device list every ten seconds, and that refresh treated "we do not know" as
"no preference set" — so the guess came back. It stays honest now.
Verify the download
Get-FileHash .\SysManager-v1.76.7.exe -Algorithm SHA256
Expected SHA256: 4099A04BE94C6385658988557F8AD808F85F82B027C6BCA7BC5017506970B25D
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.7.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.7.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.