One computer can have several audio states
A system alert can use the default destination while an application uses a saved output. Microsoft's current support guidance explicitly identifies per-app levels and destinations as relevant when system sounds work.
This is why a successful alert is useful evidence but not a complete speaker or player test. Keep the exact application and output named.
Compare the app entry
Open the Windows 11 Sound settings and Volume mixer through the documented route. Inspect whether the affected app is muted, set very low or directed elsewhere. Keep the source item and selected track unchanged.
Do not reinstall the player merely because the main volume icon looks normal. A reinstall changes application state without first resolving the mixer observation.
Confirm the destination physically
Listen for the actual output device and check its own volume or mute control. A monitor selected as an audio output may not have the expected speakers or may use its own level.
If headphones or HDMI equipment were recently disconnected, record that transition. An app retaining an old route is a different pattern from persistent silence on every output.
Keep format questions for the right stage
If routing and level are correct but only one identified track fails, report the format and comparison. Do not label every silent app a missing-codec problem. Conversely, a successful mixer correction does not establish multichannel decoding or passthrough support.
The useful process moves from the observable state to a narrower question rather than applying every audio fix.
Write an actionable report
State that system alerts reach the intended speaker while the named app's reference remains silent, and include the app's selected output and level. That gives the developer or equipment support team a clear boundary.
No Windows machine, driver or IPTV account was tested for this article. It explains a documented per-app distinction and does not promise that the mixer alone resolves every audio failure.
Keep the level change modest
If a low per-app slider is corrected, listen briefly before increasing another stage. Two independent levels can multiply the perceived change when the downstream device is unmuted. Once ordinary sound returns, leave a sensible documented setting rather than preserving every temporary increase. This keeps the household recovery route predictable and avoids confusing a later loud passage with a new decoding defect.
Sources and scope
Scope notes distinguish published documentation, supplied information and editorial methods. They do not report a hands-on service test.
- Microsoft per-app audio troubleshooting — Official current support excerpt: Windows11 Volume mixer, per-app level and output selection; proposed checks not executed.
- Microsoft low or quiet sound — Official current support excerpt: independent system/app level and output enhancement comparison; no driver or hardware test performed.
