ASUS ExpertBook B3 laptop on white, illustrating microphone troubleshooting on Windows 11
Use & troubleshooting

Windows 11 laptop microphone not recording: where to start

Hear the meeting but nobody hears you? Check mute controls, the input test, Windows permissions and the meeting site before changing drivers.

Share:

You can hear the meeting clearly, but nobody hears your reply. Speaker volume and microphone recording are different checks. Start by choosing one recording source, testing a short sentence and comparing Windows with the call app. This guide is for Windows 11 and favours changes you can understand and reverse. Labels may differ with the language or version on your laptop. If the call is urgent, tell the organiser before attempting a longer repair.

1. Check mute controls and identify the recording source

Diagram of mute controls, Windows input selection and a short microphone test
TECHBUY explanatory diagram, not a Windows screenshot. Check the source before removing drivers.

Look at the call mute button and any headset switch. If you have Bluetooth headphones, a USB webcam and the laptop together, write down which microphone you intend to use. Do not assume a shortcut from another laptop applies to your model.

ASUS explains that audio ports can be separate or combined. A headset playing sound does not prove its microphone plug is compatible. Read the model instructions rather than forcing a plug or poking a microphone opening. For example, after unplugging a USB headset, compare the input name instead of moving every volume slider.

  • Check the call and accessory separately.
  • Speaker volume is not a microphone test.
  • Do not dismantle the laptop.

2. Run the Windows input test

Microsoft describes a microphone test in Sound settings. Select your input, open its properties and record a short sample. Stop the test and listen back where offered. Adjust the recording level if needed, rather than immediately choosing the maximum.

Use the same harmless sentence at your normal working distance. Note the source name, whether playback is audible and whether speech breaks up. Never read passwords or customer details into a test. An audible Windows sample with a silent call is a reason to inspect the app, not a complete certificate of hardware health. A missing input and a silent recorded sample should be recorded as separate symptoms.

  • Speak normally instead of tapping the microphone.
  • Keep the same input for comparisons.
  • Record the result before changing another setting.

3. Review microphone access without allowing everything

Three-layer diagram of Windows permissions, the selected input and meeting website access
System access and website permission are separate. Allow only trusted apps and meeting addresses.

Open the Microphone page under Privacy & security. Microsoft privacy guidance distinguishes system access, listed apps and desktop software. Not every desktop app has its own switch in the individual-app list. Follow the options actually displayed on your Windows version.

Ask IT about restricted controls on a managed laptop. Do not remove management software or change Registry entries to bypass the policy. After a permitted change, repeat the same voice test. Granting unrelated camera or location access does not help isolate the recording problem.

  • Camera permission is not microphone permission.
  • Grant access for an actual need.
  • Redact account information in support screenshots.

4. Compare the call input and website grant

Compare the microphone name in the call settings with the source you tested. When several accessories are present, the default selection may not be your intended input. Also check the call mute button rather than relying on a permission indicator alone.

Google explains the Chrome site grant and default microphone selection. Review Microphone under Site settings and check the real meeting domain. A work-managed browser may require administrator help. Save unfinished work before rejoining a call, and report the useful distinction: Windows records the sample, but the meeting receives no speech.

  • Compare device names, not just icons.
  • Avoid unknown microphone-test websites.
  • Tell the organiser before leaving the call.

5. Collect evidence before a driver change

For an undetected device or an issue following an update, use Microsoft microphone troubleshooting guidance. If a driver intervention is needed, use a suitable official source for the exact model. Save work before restarting, and avoid packages claiming to repair every audio fault.

Give support the model, Windows version, source name, start time and Windows-versus-call results. A known working USB headset can be a temporary meeting option, not proof that the internal microphone is broken. For video problems, read the Windows webcam checks; for playback issues, use the separate Bluetooth headphone guide.

  • Do not share meeting recordings or private data.
  • Change one factor at a time.
  • Seek warranty help for damage or repeated failure.

Conclusion

Work through mute, input selection, a Windows sample, permissions and call settings in order. Keep a brief result for each change. This gives you and technical support a clearer starting point than a laptop on which several unrelated drivers and policies have already been changed.