Microphone not working on Windows 11 usually comes down to one of three things: the wrong microphone is selected in the app or Windows, Windows privacy settings are blocking access, or the driver has a problem. The order matters — privacy settings block thousands of hours of unnecessary driver troubleshooting every year. If you want the full context, see our Complete Guide to Fixing Windows, Browser, and Software Errors.
Before anything else: Settings → Privacy and security → Microphone. Confirm three things are on: “Microphone access” at the top, “Let apps access your microphone,” and if you’re using a desktop app (not a Store app), scroll down to confirm “Let desktop apps access your microphone” is also on. If any of these are off, turn them on and test immediately. This is the complete fix for a large proportion of microphone failures on Windows 11 — the privacy toggle was turned off by a Windows update, a Windows reset, or accidentally.
Which App Is the Microphone Not Working In?
This question changes everything about the diagnosis. Microphone not working in Windows itself (Voice Recorder, Speech Recognition) is different from microphone not working in Chrome, which is different from microphone not working in Teams or Zoom.
- Not working in Windows-native apps (Voice Recorder, Cortana) — Windows driver or privacy settings issue. Fix 1 and Fix 2.
- Not working in a browser (Chrome, Firefox, Edge) — Browser-level microphone permission for the specific site, plus the same Windows privacy settings. Fix 3.
- Not working in a specific app (Teams, Zoom, Discord) — Application audio device settings, plus Windows permissions. Fix 4.
- Not working anywhere — Driver problem, hardware fault, or privacy toggle. Fix 2, then Fix 1.
Fix 1: Select the Right Microphone
Windows 11 can have multiple microphones simultaneously: the built-in laptop mic, a USB headset mic, a Bluetooth headset mic, a webcam mic. Each appears as a separate input device. When you connect a new microphone, Windows sometimes keeps the old one as default — meaning apps still use the old (now disconnected or wrong) microphone.
Set the correct default: right-click the speaker icon in the taskbar → Sound settings → scroll to Input → click the dropdown and select the correct microphone. The green bar below the selected device should respond when you speak — if it doesn’t move at all, the selected microphone isn’t picking up audio (wrong device, muted, or hardware issue).
For more control: right-click the speaker → More sound settings → Recording tab. This shows every input device including disabled ones. Right-click → Enable on any device showing as disabled that you want to use. Right-click the correct microphone → Set as Default Device. Also right-click → Properties → Levels tab — ensure the volume isn’t at zero and the microphone isn’t muted.
Fix 2: Update or Reinstall the Microphone Driver
Built-in laptop microphones are managed by the audio driver (typically Realtek or Intel Smart Sound Technology). When this driver becomes corrupted or gets replaced by a less capable version after a Windows update, the microphone stops working even though Windows shows it as present in the Recording tab.
Download the audio driver from your laptop manufacturer’s support page (search by model number). Manufacturer audio drivers are almost always better than the generic Windows version for microphone functionality — they include proper noise cancellation, beam-forming support, and correct microphone array configuration for the specific hardware.
For a clean reinstall: Device Manager → Audio inputs and outputs → right-click the microphone entry → Uninstall device → tick “Delete the driver software” → Uninstall → restart. Windows reinstalls a generic driver automatically. Then install the manufacturer driver on top of it.
USB microphones and headsets have their own separate drivers. If a USB microphone isn’t working: Device Manager → Audio inputs and outputs or Sound, video and game controllers → find the USB microphone → update or reinstall its driver. Check the manufacturer’s website for a specific Windows 11 driver if the generic one doesn’t work correctly.
Fix 3: Browser Microphone Permissions
Browsers maintain their own microphone permissions separate from Windows. Even with Windows microphone access fully enabled, a browser can still block microphone access for a specific website. This is the cause when microphone works in Voice Recorder or desktop apps but fails specifically in browser-based applications (Google Meet, browser Zoom, Jitsi).
Chrome: Click the padlock icon in the address bar of the meeting site → Site settings → Microphone → Allow (not Block). Also check chrome://settings/content/microphone to confirm the site isn’t in the blocked list.
Firefox: Click the padlock → Connection secure → More Information → Permissions → Use the Microphone → Allow.
Edge: Same as Chrome — padlock → Permissions for this site → Microphone → Allow.
If you previously clicked “Block” on a microphone permission request, the browser remembers this and blocks all future requests from that site. Clearing it through the site permissions settings is the only fix — refreshing the page alone won’t help.
Fix 4: In-App Audio Settings
Teams, Zoom, Discord, and other communication platforms have their own audio device selectors that work independently from Windows defaults. An app can have a different microphone selected than what Windows shows as default, and if the app’s selected device disconnects or changes, the app’s audio fails even though Windows audio is fine.
Check each app’s audio settings:
- Teams: Settings → Devices → Microphone — confirm the correct device is selected
- Zoom: Settings → Audio → Microphone — confirm and click Test Microphone
- Discord: Settings → Voice and Video → Input Device — confirm and test
Also check for “Exclusive Mode” conflicts. Some apps request exclusive control of the microphone, locking other apps out. When Teams has exclusive access, Discord may show the microphone as unavailable. Closing apps that are using the microphone and reopening the one you need often resolves this.
Fix 5: Microphone Boost and Volume
A microphone that’s working but too quiet — others can barely hear you — is a volume level or microphone boost issue rather than a driver problem.
Right-click speaker → More sound settings → Recording → right-click active microphone → Properties → Levels tab. Check two values: Microphone (the main input level, 0–100%) and Microphone Boost (+0 dB to +30 dB). If the main level is below 70%, increase it. If the mic is still too quiet at 100%, add some boost (+10 dB is usually enough without adding excessive noise). Test after each adjustment — too much boost amplifies background noise alongside your voice.
Fix 6: Run the Audio Troubleshooter
The Windows recording troubleshooter handles the most common microphone failures automatically: wrong default device, stopped audio service, and basic driver issues. Settings → System → Troubleshoot → Other troubleshooters → Recording Audio → Run. Apply whatever it recommends. This is a two-minute step worth running even if you’re skeptical — it handles a specific set of common problems reliably and occasionally saves deeper troubleshooting.
Microphone Echo and Background Noise
If the microphone works but produces echo or picks up excessive background noise, the issue is usually audio enhancements or the Stereo Mix device.
For echo: check Recording tab → Stereo Mix → if enabled, it records the system audio output back into the microphone stream, creating feedback. Right-click Stereo Mix → Disable.
For excessive background noise: microphone Properties → Enhancements tab → check whether “Noise Suppression” and “Acoustic Echo Cancellation” are enabled. Enabling these reduces noise pickup but can occasionally over-suppress the voice signal. Experiment with which combination produces the best call quality for your specific microphone and environment.
Our guide on no sound on Windows 11 covers the audio output side — the driver and device selection approach is the same for input and output, and fixing one often resolves the other. For microphone issues specifically in Zoom or Teams calls, our Zoom audio troubleshooting covers the in-app settings that override Windows defaults. Microsoft’s Windows 11 microphone documentation covers the microphone privacy settings in more detail for enterprise environments where Group Policy controls application access to audio hardware.
Laptop Built-in Microphone vs External Microphone
Built-in laptop microphones are arrays — multiple microphone capsules that Windows uses together to provide beam-forming (focusing on sounds in front of the laptop) and noise cancellation. When the audio driver is generic rather than manufacturer-provided, Windows often doesn’t know how to correctly process the array and treats it as a single microphone, resulting in poor quality, quiet output, or the microphone appearing not to work at all despite technically receiving audio.
The manufacturer’s audio driver is particularly important for laptop built-in microphones. Dell laptops with Waves MaxxAudio, HP laptops with Bang & Olufsen audio, Lenovo laptops with Dolby Atmos for voice — each of these has specific audio processing that the generic Realtek driver doesn’t implement. Installing the manufacturer’s specific audio package (not just the driver, but the full audio software package from the support page) enables the microphone array processing that makes the built-in mic sound acceptable for calls.
Exclusive Mode and Communication Apps Conflicting
Windows audio exclusive mode allows an application to take full control of an audio device, preventing other applications from using it simultaneously. For microphones, this means if Teams has exclusive access during a call, Discord or a recording application attempting to use the same microphone will find it unavailable.
Disable exclusive mode to allow multiple applications to share the microphone: right-click speaker → Sound settings → More sound settings → Recording → right-click your microphone → Properties → Advanced tab → uncheck “Allow applications to take exclusive control of this device.” With exclusive mode disabled, all applications share the microphone simultaneously. Some applications need exclusive mode for specific features (very low-latency audio recording in DAWs, for example), but for everyday communication applications, shared access is preferable to the “microphone busy” errors that exclusive mode creates.
Microphone Not Appearing in Device Manager
A microphone that doesn’t appear in Device Manager → Audio inputs and outputs at all is either physically disconnected (check the cable or USB connection), disabled in BIOS (for built-in laptop mics, check BIOS for an “Integrated Microphone” setting), or has a physical hardware fault. Unlike software issues where reinstalling a driver brings the device back, a device that doesn’t appear in Device Manager even with “Show hidden devices” enabled has a problem at the hardware or firmware level.
For laptops: some manufacturers include a physical mute button or switch for the microphone, separate from the software mute. Check for a dedicated microphone mute button on the keyboard (often marked with a microphone icon with a line through it) or a physical privacy switch on the laptop’s chassis. These hardware mutes completely disconnect the microphone at the hardware level, making it invisible to Windows regardless of any software settings.
Microphone in Safe Mode as a Test
If the microphone works in Safe Mode but not in normal Windows operation, a startup application or non-essential service is interfering with it. Safe Mode loads only essential Windows components and drivers — so stable microphone operation there confirms the hardware and core driver are fine.
Boot into Safe Mode with Networking (hold Shift + Restart → Troubleshoot → Advanced options → Startup Settings → press 5). Test microphone in Voice Recorder. If it works, boot normally and disable startup programs one group at a time (Task Manager → Startup apps → disable half → restart → test). This binary search approach finds the conflicting startup program in two to three rounds of testing rather than disabling and re-enabling every item individually.
Third-Party Audio Software Conflicts
Gaming headset software (Razer Synapse, SteelSeries GG, Logitech G HUB, HyperX NGENUITY) installs its own audio processing layers that sometimes conflict with Windows audio settings. These conflicts manifest as the microphone appearing in Windows settings but producing no audio, or the microphone working in the headset software’s test but not in other applications.
Temporary test: close all gaming headset software completely (system tray → quit/exit, not just minimize) and test the microphone. If it works after closing the software, the conflict is confirmed. Usually the fix is updating the headset software to its latest version — headset software manufacturers update their drivers to resolve Windows compatibility issues fairly regularly, and running an old version against a recent Windows 11 is a common cause of these conflicts. If no update resolves it, removing the headset software and using the generic Windows HID driver for the headset is the alternative, losing some manufacturer-specific features in exchange for reliable audio.
One practical final check: after working through driver and privacy settings fixes, test the microphone in Windows Voice Recorder specifically rather than in a calling application. Voice Recorder uses the Windows audio API directly with minimal processing — if it works there, the microphone hardware and Windows driver are confirmed functional, and any remaining failure in a specific app (Teams, Zoom, browser) is an app-level permission or settings issue in that application rather than a Windows-level problem. This distinction tells you exactly where to look next without retesting everything from scratch. See also Fix Chrome Microphone Not Working for a related case.
