No sound in Windows 11? Find where the audio path stops

Start by defining what “no sound” means

Do not change drivers until you know the scope. Use a short, known-good local audio file or a Windows system sound. Avoid starting with a browser tab or streaming service, because the site, browser, account, connection, and protected media path add extra variables.

Write down which pattern fits:

• One app is silent. Other apps and Windows sounds work.
• Every app is silent on one output. Speakers fail, but headphones or another output works.
• The wrong device plays. Audio goes to a monitor, dock, headset, controller, or Bluetooth device you were not watching.
• The output is missing. The expected speakers or headphones do not appear in Sound settings.
• All outputs are silent. System sounds and known-good local audio fail everywhere.
• Sound cuts in and out. Record whether the change follows a cable, dock, display, sleep, update, or Bluetooth connection.

Save the exact time, Windows edition and OS build, computer or motherboard model, affected app, selected output, connection type, and any recent Windows, driver, dock, display, or audio-app change.

Check the selected output and physical path

Open Settings > System > Sound and look at the output device Windows selected. Connecting an HDMI or DisplayPort monitor can move audio to that display even when the monitor has no speakers or its volume is off. Docks, USB headsets, Bluetooth devices, game controllers, and virtual audio tools can also become the active output.

Select the output you actually want and use the device’s supported test control if one is available. Check the hardware mute key, speaker or headset volume, cable seating, dock power, and monitor audio controls. For a wired headset, verify that it is connected to the intended jack or USB port. Do not force a plug or keep reconnecting hardware that is hot, damaged, sparking, or producing an unusual odor.

Use Volume mixer when one app is silent

Windows can mute one app or route it to a different output while the rest of the system works. Open Settings > System > Sound > Volume mixer while the affected app is running. Check its volume, mute state, and output device.

Also check the app’s own audio setting. Meeting tools, games, browsers, media players, and creative apps may remember a headset or monitor that is no longer connected. Pick the same known-good output Windows is using, then close and reopen that app once.

If only browser audio fails, compare one local Windows sound before clearing browser data or changing extensions. If only a call app fails, separate speaker output from microphone input. A working microphone does not prove the speaker route is correct, and vice versa.

Compare one built-in output with one external output

If it is safe and practical, compare the computer’s built-in speakers with one known-good wired or USB output. Change only one thing at a time. This tells you whether the symptom follows the Windows audio path, one physical connector, one external device, or one selected route.

Do not use five different adapters and docks in one session. That creates more unknowns than evidence. If a dock or monitor is involved, test the computer directly once. If the direct connection works, preserve the dock model, cable type, port, firmware context, and exact failing route for the next step.

For Bluetooth-only trouble, use the Windows 11 Bluetooth guide to separate pairing, connection, profile, and device-selection problems. Do not remove every paired device just because one headset is silent.

Check whether Windows can see the audio device

Open Device Manager and expand Sound, video and game controllers and Audio inputs and outputs. Record whether the expected device appears, whether it is disabled, and whether Windows shows an error code. Also save the displayed device name, driver provider, driver date, and driver version.

A missing output in Sound settings and a missing device in Device Manager point to a different branch than a present device that is selected but silent. Microsoft’s current guidance for missing or undetected audio devices includes showing hidden devices, scanning for hardware changes, enabling a disabled device, and then working through the supported driver path.

Do not download an audio driver from a generic driver site. Use Windows Update or the computer, motherboard, or device maker’s official support page for the exact model. A newer-looking version number is not proof that a driver fits your hardware.

Run the Windows audio troubleshooter before broad repairs

Microsoft currently directs Windows 11 users to the automated audio troubleshooter in the Get Help app. Run it with the affected output connected and selected. Save what it checked, what it changed, and whether the same known-good test works afterward.

A successful test means the symptom cleared under that condition. It does not prove the root cause. A “fixed” message without working audio is not a completed diagnosis, and a “no issues found” result does not show that the hardware is healthy.

Restart audio services only when the device is present

If Windows sees the expected device but every app remains silent, a normal restart is the lower-risk first comparison. Save your work and restart the PC once. Retest the same file and output.

Microsoft also documents restarting Windows Audio and related services as a supported step. Record the service state before and after. If the service stops again, preserve that result instead of repeatedly forcing it to start. On a managed PC, do not change service startup settings without approval.

Handle driver changes as controlled tests

Driver work belongs after you have recorded the output route, Device Manager state, and recent-change timeline. If sound stopped immediately after a driver or Windows update, note the update and date. The driver-update recovery guide explains how to preserve that evidence before rollback or replacement.

Use one supported action at a time: Windows Update, the manufacturer’s exact-model package, a documented rollback when available, or a carefully recorded uninstall and restart if Microsoft or the hardware maker directs it. Keep BitLocker recovery information and backups available before firmware, chipset, or recovery work.

Do not remove every audio, chipset, Bluetooth, USB, display, and monitor device at once. HDMI audio may come through the graphics device, USB audio through a dock, and Bluetooth audio through a separate path. Mass removal destroys the comparison you just built.

Know when this is no longer a routine software check

Stop owner troubleshooting when the computer or audio hardware is physically damaged, hot, wet, sparking, swollen, or producing an unusual smell. Also stop when important data is not backed up, BitLocker recovery details are unavailable, or the next step would change firmware, erase the PC, or affect a managed environment.

If one known-good external output works but the built-in speakers never appear or never produce sound, the remaining possibilities can include the internal audio path, connection, firmware, driver, or speaker hardware. If no output appears anywhere, the device inventory and exact-model support path matter more than another generic reinstall.

Build a clean handoff

• Windows edition, version, and OS build
• computer or motherboard make and exact model
• the affected app, output, connector, dock, monitor, or headset
• whether system sounds and a known-good local file work
• the Volume mixer route and mute state
• Device Manager names, status, error code, provider, date, and version
• the last known-good time and recent Windows, driver, hardware, or app changes
• results from one direct-output comparison, one restart, and the supported troubleshooter

Screenshots and logs can expose user names, device names, meeting details, file paths, and account information. Review them before sharing. Never provide passwords, recovery keys, or two-factor codes in a troubleshooting transcript.

Where OmniMend fits

OmniMend can help organize the affected app, selected output, Device Manager state, Windows build, recent changes, and results from reversible comparisons. It does not install unknown drivers, reset Windows, open the computer, or promise that every audio problem is software-only.

The OmniMend help article library keeps Bluetooth, driver, update, performance, display, storage, and app problems in separate evidence paths so one symptom does not trigger an unrelated fix.