A Windows 11 microphone is detected but meetings hear silence

A microphone can appear in Windows while the meeting app records nothing. The failure may sit at the physical mute switch, Windows input selection, privacy permission or the meeting app's chosen device. Reinstalling the audio driver first changes many variables and often misses a browser-site denial. Compare the microphone in a Windows test and a meeting preview, then change only the failing layer.

Before you start​

Know which microphone should be used: laptop array, USB headset or webcam. Check its cable, hardware mute and headset battery. Tell meeting participants you are testing rather than repeatedly joining live calls. If you need to record a sample, use a private local test and delete it afterward if it contains sensitive speech.

Do it step by step​

1. Open Settings > System > Sound > Input and choose the intended microphone. Speak at normal distance and watch the input-level meter. If it stays flat, check physical mute, device power and the manufacturer's own mute control.
2. Use the Windows input test or a local recorder. If Windows records clearly, avoid changing its driver and move to the app's device selection and permissions.
3. Go to Settings > Privacy & security > Microphone. Check device and app access. For a conventional desktop meeting app or browser, confirm the desktop-app access setting; for a Store app, inspect its specific toggle.
4. In the meeting app select the same input by name and run its test. In a browser, inspect the site's microphone permission and the browser's selected device. Close a competing app only if it appears to hold exclusive access.
5. If the Windows input meter fails on two known-good microphones, run the audio troubleshooter and inspect Device Manager for an error or recent driver update. Use a targeted rollback or supported driver from the PC maker only when the evidence points there.
6. Restart the app and test a short private call. Verify that the correct microphone still works after unplug/replug or sleep; restore unnecessary broad permissions to your preferred state.

Check the result​

The Windows input meter responds and a meeting test receives intelligible speech from the intended device. The app's device name matches the Windows selection, and hardware mute behaves predictably.

If something goes wrong​

If the meter moves but the meeting app is silent, focus on app or site permissions. If no input device appears, check USB connection and Device Manager. If only a Bluetooth headset microphone fails, its connection or profile may be the issue rather than Windows privacy.

Know the limit​

Windows permission controls do not replace an app's own selection or browser site consent. Some managed devices enforce microphone policy. Do not disable privacy protections globally as a permanent workaround. Microsoft microphone troubleshooting General audio checks

Decision checkpoint​

A meeting app may remember a headset that is no longer connected. Check its selected input immediately before a call, especially after using a dock or Bluetooth device. If the Windows meter is healthy but the other person hears silence, collect the app's device and permission settings before touching the system driver.