SysManager 1.128.0

[1.128.0] - 2026-10-09

Volume Control can now send an app to another output device, and shows which device each app plays through
(#2584, #2088).

Added

• Volume Control shows where each app plays. The Output picker in each app's row now reads the device Windows
  sends that app to, instead of "Choose a device" because it could not tell. It reads it when the app appears and
  again every ten seconds, so a change made in Windows' own sound settings shows up too, and a route set before a
  restart is still shown after it. When Windows cannot say, the picker still says "Choose a device" (#2088).

Fixed

• Volume Control: moving an app to another output device works. The check that decides whether an app can be
  routed asked the wrong Windows object, so it always answered no and every row showed "Choose output device…",
  which only opens Windows' settings. It now asks the Windows Runtime factory that carries the routing interface,
  so on Windows 10 21H2 and later, and on Windows 11, each app row gets its Output picker. Where that factory is
  missing, the row keeps the button to Windows' settings. Routing had never turned on since it arrived in 1.55.0
  (#2584).

---

Verify the download

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

Expected SHA256: B81DD173A91AE9F74912FA408E75DC4FB68356500B29C2A3A0FB1C7A07F88D23

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