DeviceOK
SearchDevice checks
Home / Fixes / Microphone Not Detected

microphone · evidence-led troubleshooting

Microphone Not Detected

Check detection, permission, selected input and live signal separately when the browser or app cannot find the microphone. The result should determine which troubleshooting layer comes next.

Reviewed 2026-08-116 diagnostic steps2 official sources
Run Mic testSee fault tree ↓

What this symptom means

Nothing useful can be tested until the device or browser path is visible. Start with connection, power, permission and OS recognition before app settings.

Diagnostic principleSeparate detection, permission, selected input, signal level, routing and physical capture. A microphone can be listed by the OS while still producing no usable signal, and it can work in the browser while one app is misconfigured.

Fault tree

Microphone fault tree

Use the observation that best matches what you can reproduce. Do not treat every cause as equally likely.

1
Wrong input or routing

Evidence: A different microphone shows signal, or DeviceOK works while the affected app does not.

Next: Compare the selected input in the browser, operating system and affected app.

2
Permission/privacy block

Evidence: The device exists but access is denied, never prompts, or works in one context and not another.

Next: Check browser site permission and OS microphone privacy controls before reinstalling anything.

3
Mute/gain/input-stage problem

Evidence: The microphone is detected but the meter stays flat or is extremely quiet.

Next: Check physical mute, interface gain, OS input level and app input gain in that order.

4
Connection or endpoint failure

Evidence: The microphone is absent in DeviceOK and another trusted app, or reconnecting changes detection.

Next: Simplify the connection path: direct port, known-good cable, no dock, then official driver/firmware support.

Interpret the result

Evidence matrix

A test result is useful only if it changes the next troubleshooting branch.

ObservationWhat it supportsPrioritize next
Works normally in DeviceOKThe browser received a live audio stream from the selected input during this session.App selection, app permission, routing, processing or conferencing settings.
Detected but no signalAn endpoint exists, but detection alone does not prove the capsule/interface is passing audio.Mute, gain, wrong endpoint, interface channel, cable or hardware path.
Not detected anywhereThe problem is below the affected app layer.Connection, power, OS recognition, driver/firmware, then hardware.
Intermittent/static onlyThe path exists but signal integrity is unstable.Cable, connector, wireless interference, USB power, grounding or failing hardware.

Fast baseline

Rule out the simple causes first

  1. 1

    Run the DeviceOK microphone test and note whether the microphone is detected and whether live input appears.

  2. 2

    Confirm the intended microphone is selected and any physical mute control is off.

  3. 3

    Check the cable, USB port, Bluetooth connection, or headset connector as applicable.

Full sequence

Work from reversible checks to invasive ones

Do not install unofficial driver packs or firmware from download sites just because the device is missing.

  1. 1

    Run the DeviceOK microphone test and note whether the microphone is detected and whether live input appears.

  2. 2

    Confirm the intended microphone is selected and any physical mute control is off.

  3. 3

    Check the cable, USB port, Bluetooth connection, or headset connector as applicable.

  4. 4

    Check browser and operating-system microphone permissions.

  5. 5

    Try the microphone in one other trusted app to separate an app-specific problem from a device-wide problem.

  6. 6

    If the microphone still fails everywhere, use the manufacturer's official driver/firmware/support path before considering hardware failure.

Platform branches

Where the setting lives

Windows

  • Settings → Privacy & security → Microphone
  • System → Sound → Input device and input level
  • Device Manager only after detection/permission is checked

macOS

  • System Settings → Privacy & Security → Microphone
  • System Settings → Sound → Input
  • Check aggregate/multi-output audio only if you intentionally use Audio MIDI Setup

Browser

  • Use the lock/site-controls icon to confirm microphone access
  • Make sure the intended input is selected after reconnecting a headset/interface
  • Retest in a private/incognito window only to isolate extensions—not as a permanent fix
If it works in DeviceOK

A live signal reaching the browser proves the selected input can capture audio in this session. If the original symptom remains, keep the next checks above the hardware layer until evidence says otherwise.

If it also fails here

Failure in both DeviceOK and a second trusted app moves the fault below the original app layer. Compare the simplest direct connection and official diagnostic path before replacement.

Escalation threshold

When software troubleshooting has stopped being high value

  • Fails in DeviceOK and at least one other trusted app
  • Fails after a direct known-good cable/port path
  • Manufacturer diagnostics also report an input/interface fault
  • Physical damage, liquid exposure or connector damage is visible
Changed one variable?The first milestone is simple detection. Only after the device appears should you troubleshoot signal quality or app behavior. Retest under the same condition so the result is comparable.
Retest Mic test