Download SysManager 1.65.18

[1.65.18] - 2026-08-18
Volume Control now notices audio devices you plug in while it is open. Before, the "play on" list was read
once when you first opened the tab and never again, so a headset connected afterwards simply never showed up.
Fixed
- A headset or speaker plugged in after opening Volume Control never appeared. The list of output
devices was read a single time, when the tab first loaded, and each app's "play on" dropdown got its own
private copy of that list — so even a refresh would not have reached a dropdown that already existed. The
tab stays loaded for as long as the app runs, which meant the only way to see a new device was to restart
SysManager. The list is now re-read every ten seconds and every dropdown shares it, so a device appears on
its own. Ten seconds rather than every second because asking Windows for the device list is expensive, and
plugging something in is not something you do several times a second.
- Changing your default output device could make each app's dropdown forget where you sent it. Refreshing
the list replaces its contents, and Windows reports the default flag as part of each device — so switching
the default made every entry count as different, and the dropdown lost the app you had routed. Each
selection is now re-matched by device identity after a refresh.
Verify the download
Get-FileHash .\SysManager-v1.65.18.exe -Algorithm SHA256
Expected SHA256: 72B76C034D7F797C1ED5C956A82AF97EDCBDBE7D293A812752D6FDEBAA058560
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.65.18.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.65.18.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.