Lataa SysManager 1.65.16

[1.65.16] - 2026-08-18
Volume Control now tells you when a change did not take. Before, if Windows refused a volume, mute or
output-device change, the slider still moved to where you put it while the app kept playing at the old
setting, with nothing on screen to explain it.
Fixed
- A volume, mute or "play on" change could silently do nothing. All three of those controls ask
Windows to apply the change and get back a yes or no, and the app was ignoring the answer. When the
answer was no — which happens for a second or so after an app stops playing, while the list of audio
sessions is being rebuilt — the slider or switch stayed where you left it and the sound did not change.
Dragging Chrome to 20% could leave it playing at 80% with the label reading 20%. All three now say so
in the status line under the list, naming the app, and the app keeps the control where you put it
rather than yanking it back under your cursor. A change that succeeds stays silent, and the once-a-second
background refresh never reports anything, so the message only ever appears for something you did.
Verify the download
Get-FileHash .\SysManager-v1.65.16.exe -Algorithm SHA256
Expected SHA256: F04E627528E772750CDB2B3203C2F4D35027F27A5B7CF1EAD076F4D3999958D8
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.16.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.16.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.