Establish the narrow symptom
Use a permitted reference with a known audible track. Confirm that the application is actually playing and that the track is not disabled. Then identify whether other system sounds or apps are audible through the intended speakers.
Record the player and Windows version. A silent programme, a muted app and a missing audio device are different observations.
Inspect the per-app level
Microsoft's current Windows 11 instructions use Start, Settings, System, Sound and Volume mixer. Under Apps, inspect the affected application's mute state and level. The system master level is not the only control.
Start at a comfortable level. Do not raise every slider to maximum while the destination may still be muted, because sound can return suddenly when another stage changes.
Inspect the per-app destination
Microsoft documents that an app can use a different output from the system default. Confirm the intended device in the app's mixer entry. A monitor, headset and built-in speakers may all be available.
Keep the programme and track unchanged during this destination comparison. If the app also has an internal output choice, record that separate setting rather than silently changing both.
Test before deeper maintenance
Replay the same reference after one relevant change and confirm where sound emerges. If the app remains silent while another works through the same destination, retain that evidence for its developer.
Do not infer a missing codec from silence alone. A format-specific problem requires identifying the actual track and decoding path after volume and routing are understood.
Report the correct state
Useful support details include the app entry, selected output, mute state, source track and exact error. A device missing from the output list is a different case from one selected but silent.
This is a documentation-based Windows 11 workflow. No audio service, driver or account was modified here, and it does not certify every sound device or IPTV player. The goal is to establish the smallest failing audio layer.
Observe reconnection behaviour
After the destination works, disconnect and reconnect an accessory only through its supported ordinary process if that transition is relevant to the original problem. Check whether the app follows the intended route. Record the previous and new device names. A failure only after reconnection is useful evidence about route handling and should remain separate from a source track that is consistently silent.
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.
