SysManager 1.76.4

[1.76.4] - 2026-09-03

Volume Control no longer claims to know which speakers or headset an app is playing through when it does not.
The picker beside each app used to always show your default device, even for an app you had sent somewhere
else, so it could tell you an app was on the speakers while Windows was sending it to a headset.

Fixed

• The output-device picker stops naming a device it is only guessing at. SysManager can send an app to a
  specific device, but Windows does not report which one an app is currently using — that read is not
  implemented. The picker filled the gap with your default device anyway, which looked like a fact and was
  frequently wrong: pick a headset for an app, restart the app, and the picker went back to saying "Speakers"
  while the headset override was still in force. It now shows "Choose a device" until you choose one, and its
  tooltip says why. Choosing still works exactly as before, and choosing your default device still clears the
  override. The same applies when an app is routed to a device that has since been unplugged: that reads as
  unknown too, rather than as your default.

---

Verify the download

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

Expected SHA256: 35420D6A8652CBEF343265381135111F4F8AAFF85FD560B9D9548725DC7E9D7A

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