Skip to main content

Audio · Focused guide

Check microphone selection, permissions, and device support

Diagnose missing recording by selecting the intended input, checking app access and recording a sample before changing an audio driver or other software.

3 min readReviewed
  1. Select

    Choose the intended microphone

  2. Permit

    Check Windows and app access

  3. Record

    Compare local capture with call app

Concept diagram: Check microphone selection, permissions, and device support: diagram comparing select, permit, record. Simplified; not a screenshot.

The short answer

If people cannot hear you, identify the microphone the app actually uses and check its permission and input level. Successful playback does not prove that capture works: a USB headset, webcam or laptop array can expose a separate microphone endpoint.

Find the intended capture source

On Windows 11, Settings > System > Sound lists input devices independently of outputs. Note whether your microphone is built-in, attached by USB, part of a Bluetooth headset or an analog headset connected through a combined jack. Record the device model and a quiet place for a short test.

Interpret an input test carefully

A moving input meter during speech suggests Windows receives a signal, but it does not establish that a call app has permission or has selected that microphone. A successful local recording is stronger evidence that basic capture works. If the call alone fails, inspect its input menu and mute state before changing the device driver.

If the internal array works but a USB headset microphone is absent, check the headset's own input endpoint, cable and USB connection. Playing audio through its speakers proves only the playback side. If an analog headset has a plug or adapter incompatible with the PC's headset jack, software cannot create a microphone connection that is not physically present.

If neither the local recording nor the input meter responds, test a second known-good input if available. When only one physical microphone fails on multiple supported systems, contact its maker. If all input devices disappeared immediately after a documented controller change, record versions and follow the narrow recovery route.

Test capture outside the problem app

Select the intended input in Sound settings and observe its input test while speaking normally. Check Settings > Privacy & security > Microphone for the relevant app access; individual desktop apps can also have their own microphone choice or mute control. Ensure an external microphone or inline switch is powered and not muted.

  1. Select the intended input and speak at a normal level while watching its test indicator.
  2. Make a brief recording in a trusted app and play it back at safe volume.
  3. Check Windows microphone access and the specific app's chosen input and mute setting.
  4. If the input is missing, reconnect the device and inspect the matching controller or USB/Bluetooth connection.

Caution: Do not raise microphone gain excessively to mask a missing or physically disconnected input.

Use the recording result

If the recording works but a call app fails, investigate that app's permission, mute and input selection. If a USB microphone is absent, check the USB connection and its manufacturer's support. If the built-in array never registers audio in Windows or maker diagnostics, consider a hardware fault.

Changing a playback driver cannot be assumed to fix capture. If a confirmed package change coincided with failure, use the narrowly matched audio recovery path after documenting versions and settings.

Questions readers ask

Why can I hear others but they cannot hear me?

Playback and recording use separately selected endpoints. Check microphone permissions, app mute and input selection first.

Does a moving microphone meter mean a call app has access?

Not necessarily. A Windows input test can work while the app uses another input or lacks permission. Test a local recording, then check app-specific settings.

Sources