START HERE
Test the microphone in Windows—or record a local 10-second sample in the online microphone test—before troubleshooting the call app. A clear local recording points to app settings or permissions; a silent local recording points to the input, connection, or mute control.
1. Check the microphone you are speaking into
Look for a physical mute button, a raised-to-mute headset boom, or a laptop microphone shortcut. Bring the microphone into its normal speaking position. A webcam, laptop, headset, and USB microphone can all be connected at once, so a moving meter does not necessarily belong to the device you intended.
For this test, close the call app and any recording software. Use the same short sentence each time, at a normal speaking level. The aim is to establish whether Windows can receive usable speech before changing echo cancellation or noise filters.
2. Make a local Windows microphone test
- Go to Settings → System → Sound and find Input.
- Select the microphone by name and open its properties.
- Use Start test, speak, then Stop test and play the recorded sample. Adjust input volume if necessary.
Listen to the sample as well as looking at a meter—or check live digital levels and play back a short clip in the browser microphone test. Room noise can move a meter while speech remains indistinct. If you hear the voice from across the room instead of close to the boom, check whether the laptop or webcam microphone was selected.
3. Check the permission layer
In Settings → Privacy & security → Microphone, check device access and access for the app you intend to use. Traditional desktop applications use the desktop-app access setting; they are not all presented as individual switches. Reopen the app after changing access.
A browser call also needs permission from that website. In Chrome, open the site's information beside the address, inspect its microphone permission, and select the intended input in the call. Grant access to the site you are using; a permission for a different meeting site does not transfer.
4. Follow the result, not the loudest guess
| Observation | Next check |
|---|---|
| Windows recording is clear; the call is silent | Call input selection, app mute, push-to-talk, and permissions. |
| The recording is faint | Microphone position and input level before filters. |
| The intended device is absent | Its connection or receiver; use the USB guide if applicable. |
| A recording contains a delayed copy | Monitoring and speaker feedback in the echo guide. |
In a voice app, explicitly choose the microphone you just tested. Check whether push-to-talk is enabled and which key activates it. A headset mute button and the app's mute button are separate controls; releasing one may leave the other active.
5. If the microphone still fails
Try the microphone on another compatible device, or a different microphone on this PC, if either is available. A failure that follows the microphone suggests a different next step from a failure that stays with one app. For a missing USB input, follow USB detection troubleshooting before changing voice-processing options. If Windows records your microphone normally but speech cuts out in calls or streams, see Discord microphone cutting out, OBS microphone filters, or NVIDIA Broadcast in OBS.
If you would like to use an available phone as a different input on Windows, the phone microphone guide explains MicDrop and its separate virtual-cable requirement. Establish that the replacement input works locally before using it for an important call.
Sources & version notes
Platform steps were checked against the official documentation below on November 13, 2026. Labels and available controls vary by operating-system version and device. Manufacturer examples apply to the named models; consult your own device manual for its options.