No sound and audio-output troubleshooting

Start with the path sound is supposed to take

“No sound” is a useful symptom, not a diagnosis. Windows can send audio to a different endpoint while an application plays normally, a television can be selected even though its speakers are off, or a headset can be connected but muted on the headset itself. A driver is one possible part of that path, but it is not the first thing to change when the problem could be an output choice or a loose connection.

Before changing anything, choose one ordinary test: a system sound, a browser video, or a local audio file. Notice whether the playback indicator or app meter moves. Then state the expected destination precisely: built-in laptop speakers, a wired headset, USB speakers, Bluetooth headphones, or speakers in a connected display. That comparison prevents a fix aimed at the wrong device.

Keep input and output separate. A meeting app can have a working microphone while its speaker output is routed elsewhere. Conversely, a recording problem does not establish that playback is broken. This guide concerns the output side; the device name shown in Settings is evidence, not proof that its physical speakers can produce sound.

1. Pause other audio apps so one test is easy to observe.
2. Write down the device you expect to hear and how it is connected.
3. Play the same short test after each meaningful change.

Check the selected output before changing drivers

In Windows 11, select the network, sound, or battery area on the taskbar and use the control beside the volume slider to view available output devices. Select the intended device. You can also open Start > Settings > System > Sound and choose the device under Output. Raise the Windows volume and make sure the output is not muted; then use the device’s own volume control if it has one.

A successful result is specific: the intended device remains selected and the test becomes audible. If it does, the problem was routing or level rather than proof of a bad driver. If the meter or app indicates audio but nothing is heard, continue with the connection appropriate to that device. If the expected device is absent, do not repeatedly select another name; first check its power, cable, pairing, or display connection.

Also consider application-level routing. In Settings > System > Sound > Volume mixer, an app can be muted or assigned a different output. Restore the app volume and output only if it differs from the intended device. Close and reopen that app after the change. A single silent app with working system sounds points more usefully to that app or its output assignment than to a system-wide audio driver.

1. Open the taskbar sound control and select the expected output.
2. Open Sound settings and confirm Output, volume, and mute state.
3. Use Volume mixer to compare the test app with the system output.

Match the check to speakers, headphones, or a display

For wired speakers or headphones, confirm the plug is fully seated in the intended jack and that powered speakers have power and their own volume turned up. Disconnecting and reconnecting one device at a time can make Windows rediscover it, but it is safer to stop playback first. A USB headset or speaker is both a physical connection and an audio endpoint, so try a different supported USB port only after checking that it is selected in Windows.

For Bluetooth audio, a connection shown as paired is not the same as the desired playback output being selected. Reconnect it according to the device and Windows pairing controls, then select its audio output. Do not infer that a general Bluetooth connection proves the headset is ready for media playback; use the Sound output list and the same test sound.

For HDMI, DisplayPort, or USB-C display audio, the graphics connection may expose a display output to Windows. Select that output only if the display or receiver is meant to play sound, is powered on, and has its own volume or audio setting enabled. A monitor without speakers can still appear as an output. Selecting it can create silence at the desk even though Windows is working as designed.

1. Check physical power and local volume for the intended hardware.
2. Reconnect one cable or peripheral, then recheck the Windows output list.
3. For a display, confirm its speakers or receiver are available before selecting its output.

Use the Windows 11 troubleshooter as a diagnostic step

Microsoft directs Windows 11 users to the automated audio troubleshooter in the Get Help app before the longer manual sequence. It can run diagnostics and attempt fixes. Launch it from the Microsoft support link or by opening Get Help and following the audio troubleshooting prompt. Read what it identifies rather than treating it as a guarantee that every audio fault has been repaired.

If the troubleshooter restores the selected output or identifies a muted setting, repeat the original test and stop when sound is stable. If it reports no resolution, preserve the useful observations already made: whether the device is present, whether another output works, and whether the issue affects every app. Those facts make the next decision less disruptive than jumping immediately to uninstalling software.

If Windows shows an output device but it fails after these checks, inspect the driver path. Windows Update is Microsoft’s recommended route for audio-driver updates. Device Manager can also search automatically for a driver, while a PC or audio-device manufacturer may provide a package for the exact model. Choose only a package matching the device and supported Windows version; a random driver download cannot establish compatibility.

1. Run the Windows 11 audio troubleshooter in Get Help.
2. Repeat the same playback test after it finishes.
3. If sound remains absent, record the device name and move to a driver check rather than making multiple unrelated changes.

Decide whether settings, hardware, or a driver deserves attention

A useful failure branch is based on what still works. If built-in speakers play but the headset does not, focus on the headset, jack, cable, USB connection, pairing, and selected endpoint. If a display is the only silent output, focus on the display audio path. If every output is silent and the expected device has disappeared, the audio driver or a broader Windows change becomes more plausible, though it is still not confirmed.

Open Device Manager only to inspect the audio device state before altering it. An error or missing audio device is information to carry to the device manufacturer or Microsoft guidance. If a problem began directly after an update, use the recovery branch rather than installing several packages in succession. If this is a work-managed PC, organization policy or managed drivers may limit what can be changed; contact the administrator instead of bypassing controls.

Seek the PC, display, headset, or audio-interface manufacturer’s support when the correct output remains unavailable after connection and Settings checks, when a manufacturer package is required, or when the device does not work with a known-good supported connection. Hardware service can be appropriate for physical damage, a failed port, persistent speaker failure, or a device that is not detected at all. Windows 10 support ended October 14, 2025; this guide is written primarily for supported Windows 11 systems.

1. Compare a working output with the silent one, if one is available.
2. Inspect Device Manager before driver changes when the device is missing or errors appear.
3. Escalate with the connection type, device name, and test results rather than a general “no sound” report.

Frequently Asked Questions