The short answer
When sound disappears, check the selected output and its volume before changing a driver. A silent app, unplugged speaker, muted display or Bluetooth routing change can look like a driver fault. Work from the simplest observable part of the path toward the hardware controller.
Choose a test that isolates the failure
These checks apply primarily to Windows 11 playback from internal speakers, wired headphones, USB devices and connected displays. Begin at a safe low volume; avoid sudden full-volume tests. Note whether all applications are silent or only one, and whether another known-working output plays sound.
A successful sound from one endpoint proves that at least one playback path works, not that every audio component is healthy. A local audio file and Windows' device test can help isolate app-specific behavior. If the issue affects recording only, inspect microphone input and permissions rather than following a speaker-only procedure.
Follow the route from app to speaker
In Settings > System > Sound inspect the selected output. Check system volume and the app's own volume or output choice; an app may remember a disconnected headset. If a connected monitor is selected but has no speakers, sound can be sent to a valid digital endpoint without becoming audible.
For powered speakers check the power, lead and correct jack. For a headset, check whether insertion changes the selected endpoint. For a display, inspect its menu volume and cable. For Bluetooth, verify that the headset is connected for audio, charged and selected as the current output; pairing alone does not prove playback is routed to it.
Three silent-output patterns
A browser and the Windows test sound are audible through laptop speakers, but one video-call app is silent. That result directs attention to the app's speaker choice, per-app volume or communications routing. The laptop's codec is demonstrably capable of playing at least one sound; updating it first would be poorly targeted.
A monitor shows a picture and appears in the output list, but it has no speakers. The system can route sound to that endpoint successfully without creating an audible result. Consult the monitor's manual for an audio-out jack or select laptop speakers. If the display does have speakers, inspect its own mute and input controls before looking for graphics audio support.
A headset plays when connected by USB but not when plugged into the analog jack. That comparison points toward the analog route, its jack, endpoint or internal controller. It does not say whether the USB headset and analog jack share a driver—they generally do not. Record which exact endpoint vanishes and whether another analog headset behaves the same way.
Use the first successful test to narrow the cause
Move one variable at a time. The Windows audio troubleshooter may offer additional observations, but read any proposed change before accepting it. Record changes so you can reverse them. Device Manager status can reveal a missing controller or a reported error, yet a normal status does not test speakers or application routing.
- Select the intended playback device in Sound and bring system and app volume up gently from a low setting.
- Play a known local file in two applications; test another endpoint such as headphones if available.
- Inspect power, cable, display sound capability or Bluetooth connection for the affected output.
- Only if the path remains broken, note controller status and current version in Device Manager and check official support for a targeted fix.
Caution: Do not remove all audio entries to fix a single silent output; that can complicate recovery and disrupt unrelated devices.
What each result tells you
If only one app fails, its output or volume settings are likely more relevant than the system driver. If headphones play but speakers do not, internal speaker hardware, jack detection or OEM tuning could be involved. If neither wired nor USB audio is available and Device Manager reports an error, investigate the corresponding hardware and package.
If a tested cable, speaker or port fails independently of Windows, software changes may not help. If sound vanished immediately after an update, compare what changed and use the recovery guide rather than installing a succession of unrelated packages.
Choose the focused follow-up
Use the output-and-volume page for route checks; the speakers-and-headphones page for analog and wired paths; and the display-audio page for HDMI/DisplayPort. The settings-versus-driver page helps determine whether a package change is warranted. If a physical device is not detected, manufacturer diagnostics or service may be the safer next step.
When a driver is a reasonable suspect
A reported error on the identified controller, a device that vanished after a known driver installation, or a repeatable regression linked to a specific package increases the case for a targeted driver intervention. Note the current version and exact PC or accessory model first. If a new package is needed, consult Windows Update or the official manufacturer support path and prepare a way back.
A normal Device Manager status is narrower evidence: Windows can communicate with a device sufficiently to report a status, but this does not test amplification, cables or acoustic output. If multiple known-good external speakers fail on one port while other audio paths work, official manufacturer diagnostics can be more informative than another random driver version.