Check the selected output, volume, and mute settings

Use one known test and name the expected destination

Begin with one test sound and one expected destination. “My audio is silent” is too broad to tell whether Windows is muted, an app is muted, or sound has been sent to a display or headset. Play a familiar clip, then identify whether you expect built-in speakers, a named USB device, Bluetooth headphones, or display speakers to reproduce it.

Look at the app first. A paused video, an in-player mute button, or a meeting application with its own speaker setting can create a symptom that Windows volume cannot fix. If another application and system notification sounds work through the expected device, do not treat the result as a computer-wide driver failure. Keep the investigation in the silent application.

1. Start one ordinary audio test and leave it playing.
2. Check the application’s own mute and speaker controls.
3. Write down the output you expect to hear before opening Windows controls.

Select the correct Windows output

Select the taskbar’s network, sound, or battery area. Next to the volume slider, open the output chooser and select the intended audio device. The same choice is available in Start > Settings > System > Sound under Output. The names can include a display, dock, headset, internal speakers, or a device manufacturer name, so choose based on the connection you are actually using rather than a name that merely sounds familiar.

The desired result is audible playback and a persistent selected endpoint. If the list shows a connected monitor but you meant to use desktop speakers, reselect the speaker output and repeat the test. If the expected device is absent, selection cannot repair that absence. Check its power, cable, USB connection, pairing, or display path before assuming that a slider setting is at fault.

1. Open the output chooser beside the taskbar volume slider.
2. Select the device that matches the physical speakers or headphones in use.
3. Repeat the test, then confirm the same device under Settings > System > Sound.

Compare system, device, and application volume

Windows has more than one relevant level. Raise the main volume and confirm it is not muted, then check the physical speaker, headset, or display volume. A powered speaker can be selected correctly while its own knob is at minimum. Likewise, a headset may have a hardware mute or volume control that Windows cannot override.

Open Settings > System > Sound > Volume mixer to inspect the test application. Restore an app that is muted or set much lower than the system. Volume mixer can also show an application output assignment; set it back to the intended device if it differs. Make only this one correction, close and reopen the app if needed, and retest. A successful result isolates the issue to per-app controls rather than an audio driver.

1. Unmute and raise the Windows main volume to an audible level.
2. Check the physical device’s local volume or mute control.
3. In Volume mixer, check the test app’s volume and assigned output.

When these settings do not restore sound

If the intended output is selected, volumes are audible, and the test is still silent, do not keep toggling mute. Compare with another output if one is available. Working laptop speakers and silent wired headphones point toward the headphone path; a working headset and silent monitor point toward the display path. This comparison is a result, not a repair, but it directs the next check. It also prevents an app-level configuration error from being misread as a driver fault.

If every available output is silent, run the Windows 11 audio troubleshooter in Get Help, as Microsoft recommends, then keep the facts it reports. If an output has disappeared or Device Manager reports a device problem, move to the driver-focused guide. The original pillar explains the broader sequence and when manufacturer support is a better next step.

1. Try one alternate output without changing driver software.
2. Run the Get Help audio troubleshooter if the symptom is system-wide.
3. Investigate connections or drivers only after recording which outputs do and do not work.

Frequently Asked Questions