Start with the signal path
Sound travels through more than one component. An app sends playback to an output endpoint selected by the operating system; a controller, connection, amplifier and speaker complete the path. For recording, a microphone and its capture endpoint reverse the direction. An audio driver helps Windows communicate with the relevant hardware, but silence alone cannot identify a faulty driver.
What this category covers
These guides cover Windows 11 audio identification, compatible driver installation, missing playback, driver recovery, and differences between internal sound chips, USB equipment, Bluetooth headsets and audio sent to a display. The same concepts can help readers using other systems, but the menu-by-menu procedures here are Windows-specific. On another platform, use its official help and your device manufacturer's instructions.
A single computer may list Speakers, Headphones, a display name and a Bluetooth headset as separate outputs. Its microphone list may show an internal array, a webcam and a headset. The name you select in Sound settings is an endpoint: it is not necessarily the controller whose package appears under Sound, video and game controllers in Device Manager.
A symptom is a starting clue, not a diagnosis
If only one app is silent, its own volume or output route is a better first check than a driver replacement. If an external headset is silent but internal speakers work, check its connection, power and endpoint selection. If all outputs disappear immediately after a driver change, the update history and Device Manager status become relevant evidence.
Try a familiar local recording at a low volume, then another output if available. Test capture separately with a short recording. A device that appears in Windows can still have an unplugged cable, muted monitor, denied microphone permission, or failed speaker. Avoid changing multiple drivers simultaneously: doing so makes the result difficult to interpret.
Identify which device owns the audio
In Windows 11 open Settings > System > Sound to see output and input devices. Note the selected endpoint, its connection and whether the problem concerns playback, recording or both. Open Device Manager to inspect the associated sound or Bluetooth hardware and its Driver tab; not every endpoint has a separately downloadable driver.
For built-in speakers, find the exact computer or motherboard model on its label, system information or manufacturer support page. For a USB interface, use its own model and maker. For HDMI or DisplayPort audio, verify the screen's audio capability and the graphics connection. A 3.5 mm headphone generally uses the host computer's audio hardware rather than a separate headphone driver.
Choose the right starting guide
Start with Audio driver installation and updates if Windows identifies the device and you have a specific compatibility or update need. Start with No sound and audio-output troubleshooting if a device is connected but silent. If a known update changed working sound, Audio driver recovery and reinstallation is the narrower route. Audio-device identification and compatibility is the starting point when you do not yet know what hardware or connection owns the sound.
Before installation, note the existing version and keep the working package or a recovery route. Prefer Windows Update or the exact manufacturer's support page for your hardware and Windows version. A manufacturer's utility may include tuning, microphone processing or jack detection that a generic package does not supply.
Know when software is not the next step
If several known-good outputs fail on one port, a damaged connector or hardware fault may require official support or service. Persistent crackling that tracks a loose cable, distortion only at high volume, or a speaker that remains silent across supported systems is not proven to be a driver problem. Do not open equipment or repeatedly force incompatible packages to investigate a possible physical fault.
Official device support is also appropriate if an installer rejects your model, a PC maker specifies a particular audio package order, or a dock/interface needs its own documented setup. These pages explain decisions; they cannot detect your hardware or guarantee that a driver change will restore it.