Working Windows system sounds do not establish one player’s volume or output. Microsoft documents app-specific checks in Volume mixer. Inspect the affected app using the route for the installed Windows version, then compare the same permitted media without changing unrelated sound routes.
Identify the intended route
Record the Windows version, player and intended connected output. Keep the player open with permitted active media and a supplied audio track selected. Use an ordinary level and preserve the starting values.
For example, notifications might reach desk speakers while a player is assigned elsewhere. Treat that as a route hypothesis until the app entry is inspected, not proof that the whole computer or media source is broken.
Use the correct Windows branch
On Windows 11, open Start > Settings > System > Sound > Volume mixer. Under Apps, inspect the affected app’s mute, volume and Output device. An app can use an output different from the system default.
The checked Windows 10 guidance uses the taskbar Volume mixer and Sounds > Playback controls. Do not expect the identical Windows 11 per-app settings screen; use the installed OS’s documented route.
If the expected app or output is absent, record the actual state before broader changes. On managed equipment, use the administrator’s supported procedure rather than removing policy controls.
Change one app value
Choose the intended ordinary volume or connected output only if its current state is wrong. Keep the media track, TV/receiver route and system default unchanged during this comparison.
| Item | Before | After the app change |
|---|---|---|
| System sound route | Record the known output. | Confirm its intended route remains. |
| Affected app | Record mute, level and selected output. | Record the deliberate app-specific choice. |
| Media state | Note the chosen audio track and player mute. | Keep these fixed for the route comparison. |
| Unrelated apps | Preserve their working configuration. | Check only if a later symptom concerns them. |
Keep a remaining failure precise
If the app now reaches the intended speaker, retain that setting and stop the wider repair. The result does not show that a driver, codec or account was replaced. If the expected output and normal app level were already selected, inspect the player’s own track/mute state and continue with the current Microsoft guidance for the remaining symptom.
A useful support note names the OS, app, selected device and exact result. Working notifications and an unexamined mixer are not a reason to reinstall drivers first. Preserve the functioning sound setup other household tasks rely on while isolating the affected app.