Windows 11’s Volume Mixer not working — the per-app volume controls not responding, volume mixer not opening, or app volumes resetting to the same level — is a Windows audio shell issue with several well-established fixes. For a broader walkthrough, our Complete Guide to Fixing Windows, Browser, and Software Errors is a good next read.
The Volume Mixer (right-click the speaker icon → Open volume mixer) should show individual volume sliders for every running application that outputs audio. If it’s blank, unresponsive, or missing specific apps: here’s what to do.
The fastest fix: restart the Windows Audio service
Volume Mixer issues almost always clear after restarting the audio subsystem. Win+R → type services.msc → find “Windows Audio” → right-click → Restart. Also restart “Windows Audio Endpoint Builder” immediately after. These two services together manage the entire Windows audio stack, including per-app volume routing.
After both restart: right-click the speaker icon → Open volume mixer. Give it 10 seconds for apps to re-register their audio sessions. If sliders now appear and respond: the service state was corrupted.
Windows 11 Volume Mixer vs Classic Mixer
Windows 11 has two Volume Mixer versions. The new mixer (Settings → System → Sound → Volume mixer, or right-click speaker → Open volume mixer in newer builds) is integrated into Settings. The classic mixer (sndvol.exe, which was the Windows 10 standard) is still accessible but handled differently.
If the Settings-based Volume Mixer isn’t responding: try the classic mixer. Win+R → type sndvol → Enter. If the classic mixer works but the Settings one doesn’t: the new Windows 11 mixer has a shell issue. If neither works: the audio service needs to be restarted (see above) or the driver needs attention.
App not appearing in Volume Mixer
An application only appears in the Volume Mixer when it’s actively playing audio. If an app isn’t showing: confirm it’s currently outputting audio (not paused, not muted at the application level). Trigger some sound in the app → check Volume Mixer again. Apps that use exclusive audio mode (some games, some communication apps) sometimes don’t appear in the mixer even when playing audio — they’ve bypassed Windows’ audio session management.
Per-app volumes resetting to 100%
If you set an app’s volume in the mixer but it resets every time the app closes and reopens: this is expected behaviour for many applications. Windows stores per-app volume settings in the audio session, but the session is destroyed when the application exits. Some apps (like Spotify or Windows Media Player) remember their volume across sessions; many don’t.
For persistent per-app volume control that survives app restarts: third-party tools like EarTrumpet (free, Microsoft Store) add more capable per-app volume management that persists settings and provides more accessible controls than Windows’ built-in mixer.
Audio device switching and Volume Mixer
When you switch the default audio output device (from speakers to headphones, or add a Bluetooth device): the Volume Mixer can lose track of existing app audio sessions. All sliders may disappear temporarily. Switch back to the original device → verify sliders reappear → then switch to the new device. Apps may need to be restarted to register with the new device’s audio session.
EarTrumpet — the recommended Volume Mixer alternative
EarTrumpet (free from the Microsoft Store) is the most popular replacement for Windows’ Volume Mixer. It shows per-app volume control in the system tray, persists volume settings across app restarts, allows grouping apps to a specific output device, and provides a much cleaner interface than the built-in mixer. If the built-in mixer is unreliable: installing EarTrumpet is a practical long-term solution rather than continuing to troubleshoot the built-in mixer.
Volume Mixer not showing some apps
Browser audio (Chrome, Edge, Firefox) appears in the mixer as a single entry for the entire browser, not per tab. If you want to control audio from individual browser tabs separately: that level of granularity isn’t available in Windows’ built-in mixer. Each browser process appears as one entry regardless of how many tabs are playing audio simultaneously.
Also: UWP apps (Microsoft Store apps) and some system services route audio differently from traditional desktop applications. They may appear with generic names (“ApplicationFrameHost”) rather than recognisable app names in the mixer.
Our guide on Windows audio troubleshooting covers the broader audio driver and device issues that affect volume and playback. For the Windows Audio service restart that’s the primary fix here, our audio crackling guide covers the audio subsystem in more detail. Microsoft’s audio documentation covers the Windows 11 Volume Mixer location changes across different Windows 11 builds, including where the mixer moved between the original Windows 11 release and subsequent feature updates.
SFC for audio infrastructure
The audio session manager’s system files can become corrupted after failed Windows Updates or disk errors. Administrator Command Prompt:
sfc /scannowAfter SFC repairs and a restart: test the Volume Mixer. Corruption in audiosrv.dll, AudioEndpointBuilder.dll, or related audio infrastructure files causes mixer failures that service restarts don’t fix — but SFC resolves by restoring the files from the Windows component store.
Driver reinstall for persistent audio issues
An outdated or corrupted audio driver can cause the Volume Mixer to malfunction even when the Windows Audio service runs correctly. Device Manager → Sound, video and game controllers → right-click the audio device → Uninstall device → check “Delete the driver software” → confirm → restart. Windows reinstalls the basic driver automatically. For better performance: install the manufacturer-specific driver from the laptop or motherboard manufacturer’s support page.
Volume Mixer and exclusive audio mode
Some applications request exclusive control of the audio output. When an app is in exclusive mode: other applications can’t use the same audio device simultaneously, and the Volume Mixer can’t show or control that app’s volume. Common exclusive mode users: high-end DAC software, some games using WASAPI, certain communication apps.
If an app’s volume doesn’t appear in the mixer while it’s running: right-click the speaker icon → Sound settings → More sound settings → your audio device → Properties → Advanced → uncheck “Allow applications to take exclusive control of this device” → Apply. This forces all applications to use shared mode, making them visible in the Volume Mixer.
Group Policy and volume controls
In enterprise environments: Group Policy can disable the Volume Mixer or restrict volume control to system-level only. If the Volume Mixer is completely inaccessible and the speaker icon shows a lock or “managed by your organization” note: IT controls audio settings. Users can’t override these restrictions locally.
Volume Mixer registry reset
Windows stores audio device preferences and per-app volume settings in the registry at:
HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionMTCUVC
Deleting this key (Win+R → regedit → navigate to the path → right-click → Delete → restart) forces Windows to recreate the audio preference store with defaults. This resolves cases where stored audio preferences have become corrupted and are causing the mixer to misbehave. After the registry key is deleted: Windows recreates it on the next boot, and the audio system initialises fresh.
Communication app ducking
Windows has a feature that automatically lowers other application volumes when communication apps (like Teams or Skype) detect audio activity. Settings → System → Sound → More sound settings → your audio device → Properties → Communications tab → “When Windows detects communications activity” → set to “Do nothing” to disable this. If other app volumes keep dropping unexpectedly during calls: this feature is the cause.
| Problem | Cause | Fix |
| Volume Mixer blank / won’t open | Audio service crash | Restart Windows Audio and Endpoint Builder services |
| Sliders not responding | Corrupted audio infrastructure | SFC /scannow; audio driver reinstall |
| App not in mixer | Exclusive mode or app not playing audio | Trigger audio in app; disable exclusive mode |
| Settings-based mixer fails, sndvol works | New Windows 11 mixer shell bug | Use sndvol as workaround; Windows Update may fix |
| Other apps get quieter during calls | Communications ducking enabled | Sound device Properties → Communications → Do nothing |
Spatial sound and Volume Mixer
Windows Spatial Sound (Windows Sonic, Dolby Atmos, DTS:X) adds a processing layer to audio output. When enabled: the Volume Mixer may show some applications under the spatial sound processor rather than directly. If an app isn’t appearing in the expected mixer position with spatial sound enabled: temporarily disable it (right-click speaker → Spatial sound → Off) → check the mixer. Re-enable spatial sound after confirming the issue is spatial sound related.
The practical summary: the Windows Audio service restart resolves most Volume Mixer failures immediately. EarTrumpet handles the cases where Windows’ mixer is persistently unreliable. The exclusive mode change fixes apps that silently bypass the mixer. These three approaches together handle the full range of Volume Mixer problems without requiring deep system changes or registry work in most scenarios.
Windows 11 has gone through several Volume Mixer location and design changes across its release history. The original Windows 11 release (21H2) had the mixer in the same position as Windows 10. The 22H2 update added a Settings-integrated mixer while keeping the classic sndvol.exe accessible. Later builds further modified mixer access. If the mixer location feels unfamiliar after a feature update: the interface may have changed rather than the feature itself being broken. Searching “volume mixer” in the Start menu (Win+S → “volume mixer”) provides a consistent access point regardless of which Windows 11 build you’re on.
System sounds and Volume Mixer
Windows system sounds (notification pings, startup sounds, error tones) have their own Volume Mixer entry labelled “System Sounds.” If system sounds are too loud or too quiet relative to other audio: adjust this slider in the mixer. Setting “System Sounds” to a lower level (20-40%) while leaving other apps at 80-100% creates a more balanced audio experience without disabling system sounds entirely.
Bluetooth device volume and the mixer
Bluetooth audio devices have two independent volume controls: Windows’ software volume (controlled in the Volume Mixer) and the hardware volume on the device itself. When both are active: the effective volume is the product of both. A device at 50% hardware volume and 100% Windows software volume produces quieter audio than a device at 100% hardware and 50% Windows software — even though both show “50%.” For the cleanest volume control: set Bluetooth devices to 100% hardware volume and control volume through Windows and the Volume Mixer, which gives the full available dynamic range to the Windows software control.
Volume Mixer on multiple audio output devices
When multiple audio output devices are connected (speakers + headphones, USB audio + HDMI): the Volume Mixer shows the current default output device’s audio sessions. Apps outputting to non-default devices don’t appear in the standard mixer view. To see apps on a different device: change the default audio output device → open Volume Mixer again. EarTrumpet handles this more elegantly by showing all active audio sessions across all devices simultaneously.
For audio professionals, content creators, and home recording users: the Volume Mixer’s limitations (no persistent per-app settings, single device view, no routing control) make it insufficient for professional workflows. Voicemeeter (free, from VB-Audio) provides a full software audio mixer that sits between applications and audio devices, enabling per-app routing, effects, and precise volume control that Windows’ built-in mixer doesn’t support. This is overkill for casual users but genuinely useful for anyone managing multiple audio sources simultaneously.
Keyboard volume control and the mixer
Media keys (volume up, volume down, mute) control the master volume — not individual app volumes. When you press the volume key: the master volume changes while all app volumes in the mixer stay at their set levels. If you want keyboard shortcuts for per-app volume control: EarTrumpet supports this (configurable hotkeys per app), or AutoHotkey scripts can be written to control specific application volumes through Windows’ audio API.
Gaming and Volume Mixer behaviour
Some games running in exclusive fullscreen bypass the Volume Mixer entirely and manage their own audio volume. For games that don’t appear in the mixer or whose mixer slider has no effect: the game is in exclusive fullscreen mode using direct hardware audio access. Switch the game to borderless windowed mode → check if it now appears in the mixer. Most modern games in windowed or borderless windowed mode respect Windows’ audio session management and appear correctly in the mixer.
The Volume Mixer’s most useful everyday function — balancing app volumes without adjusting the master — is something many Windows users don’t realise they can do. Setting individual app volumes (Discord at 60%, music at 80%, game at 100%) rather than fighting with the master volume creates a much better audio experience, particularly when video calling while listening to music or gaming. If the mixer hasn’t been explored before: spending 2 minutes setting app-specific levels is worth it. When it stops working and the service restart isn’t fixing it: EarTrumpet is the most practical path to reliable per-app volume control without further Windows audio system investigation. See also Windows 11 Brightness Not Working for a related case.
