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 microphone input, first watch the Settings input meter and record locally before testing a call app.
What this covers
- Windows microphone input with this exact failure state
- Diagnosis across microphone hardware versus permission, input selection, level and app processing
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: capture clear speech through the intended input without clipping.
Isolate the component boundary
ReversibleWatch the Settings input meter and record locally before testing a call app. Test the peripheral on a different port or user account, and test a different peripheral on the same port. Boundary to separate: microphone hardware versus permission, input selection, level and app processing.
Correct only the proven cause
ReversibleSelect the correct input, set a moderate level or replace the failed headset/cable. 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. Do not insert tools into microphone openings; stop for heat or liquid damage.
Evidence ledger
Sources behind this answer
Exact questions