A computer feature or peripheral that has completely stopped should be separated into driver, permission and physical-connection layers before assuming component failure. For Windows audio device and driver, first play the test tone, inspect the volume mixer and test a known headset.
What this covers
- Windows audio device and driver with this exact failure state
- Diagnosis across speaker/headset hardware versus output selection, app mixer and driver
What it does not cover
Try in this order
0 of 4 completedCapture the exact failure state
ReversibleCheck Device Manager or System Information for whether the hardware is even detected, and whether an error code is shown. Expected behavior: route audio to the selected endpoint with the correct sample format.
Isolate the component boundary
ReversiblePlay the test tone, inspect the volume mixer and test a known headset. Test the peripheral on a different port or user account, and test a different peripheral on the same port. Boundary to separate: speaker/headset hardware versus output selection, app mixer and driver.
Correct only the proven cause
ReversibleSelect the right endpoint, restart audio services or install the OEM driver. Reinstall or roll back the driver, or grant the missing app permission.
Verify and stop safely
ReversibleConfirm the feature works after a full restart in at least two different applications. Stop for loud popping, heat, liquid or a damaged jack.
Evidence ledger
Sources behind this answer
Exact questions