Look at the device before the sound panel
The sound panel only lists endpoints that exist. Device Manager shows whether the controller is present, disabled or hiding under a warning sign.
devmgmt.msc > Sound, video and game controllers
The speaker icon with a red cross and that message means Windows lost the endpoint, not that the speakers died. The order of repairs matters.
Check **Device Manager** for a code 10 or a hidden device, restart the **Windows Audio** and **Audio Endpoint Builder** services, then reinstall the **chipset and audio driver**. A sleep-related driver crash causes most cases.
The sound panel only lists endpoints that exist. Device Manager shows whether the controller is present, disabled or hiding under a warning sign.
devmgmt.msc > Sound, video and game controllers
A device that failed to start after a sleep cycle often stays as a ghost entry. Removing the ghost forces a clean enumeration on the next scan.
View > Show hidden devices
Windows Audio plays the sound, the Endpoint Builder creates the devices. If either is stopped, no endpoint exists no matter what the driver says.
net stop audiosrv & net stop audioendpointbuilder
A Windows Update driver for an older codec often fails after a feature update. Install the vendor package, reboot, and confirm the entry no longer shows a warning.
Some boards disable the onboard codec when a front-panel header is unplugged, and laptops can disable it in the firmware when a dock is set as default. Look for an audio or HD Audio entry.
A missing or corrupted audio component survives every driver reinstall. A quick system file check repairs the component store without a reinstall.
sfc /scannow
The driver cannot start. Remove the device with its driver, reboot and reinstall the vendor package.
A power-management bug in the driver. Update it, or disable the selective suspend for the audio controller.
The jack detection is stuck. Replug, or disable jack detection in the vendor control panel.
A dependency is stopped. Start the Windows Audio Endpoint Builder first, then Windows Audio.
Only if the fault appeared after an update. Note the date first.
Yes when the codec was disabled in firmware. Loading defaults is quick to test.
Nothing here changes your data. If the vendor driver made it worse, roll it back in Device Manager under Properties > Driver > Roll Back Driver.
Free · no account needed · tracks your progress