SysManager 1.121.0 다운로드

[1.121.0] - 2026-10-06
Volume Control now has a This PC card above the apps: one slider for all sound, and a picker for the speakers or
headphones it plays through. "Everything is too loud" and "the sound is coming out of the wrong speakers" no longer
mean leaving SysManager for the taskbar.
Added
- This PC on Volume Control (#1588). A card of its own above the app list, tinted so it does not read as one more
app.
- All sound: the PC's volume, mute and live level, with the same controls an app row has. It is Windows' own
volume, the one the taskbar slider moves, and it applies on top of each app's level.
- Sound plays through: picks the device all sound goes to, for everyday sound, media and calls at once, as the
Windows sound flyout does. The open list says what kind of device each one is (headphones, speakers, a monitor or
TV over HDMI or DisplayPort) and which one is in use now. Apps you sent to a device of their own keep it. Where
Windows does not let SysManager switch, the card names the device in use and offers Windows' sound settings
instead.
- Volume presets still keep each app's level and nothing more, so applying one never changes the PC's volume or
moves the sound to other speakers.
- The status line names the device too ("3 apps playing audio · output: Headphones").
- Searching the sidebar for "speakers", "headphones" or "output device" opens Volume Control.
Fixed
- Volume Control stayed on the device that was in use when it first opened (#1588). It opened the default output
device once and kept it, so after headphones were plugged in or the device was changed from the taskbar, the app
list went on showing the first device's apps, and their sliders moved sound that no longer played there, until
SysManager restarted. The tab now follows the change within about ten seconds, and at once when the device is
changed from the card. This dates from the first Volume Control, in 1.52.38.
- A closed drop-down showed a programmer's description instead of what you picked. After picking a preset, the
Presets box on Volume Control read "VolumePreset { Name = Evening, Entries = … }", and Gaming Profile's game box read
"RunningProcess { ProcessId = … }". The drop-down style added in 1.52.24 (#1243) left out the part that shows an
item by its name. It shows the name now.
Verify the download
Get-FileHash .\SysManager-v1.121.0.exe -Algorithm SHA256
Expected SHA256: 80933F985D369A6B4CD9D649863982F986FD32869CF167E2889E8566AF885426
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.121.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.121.0.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.