Microphone Not Working on Windows 11? Fix

Open Settings, Privacy & security, Microphone. Three toggles to check: Microphone access at the top must be On, Let apps access your microphone below that must be On, and then scroll through the per-app list and make sure your specific app — Zoom, Teams, Discord, Chrome, whatever — is toggled On individually. This is the fix roughly 40% of the time and it takes thirty seconds.

A high school teacher called us an hour before her first class of the year. Laptop microphone wasn’t picking up anything in Zoom. Students could see her, hear nothing. We screen-shared, and the Windows Sound test bar moved fine when she spoke — so Windows could hear her, but Zoom couldn’t. In the per-app permission list, Zoom was specifically toggled Off. Turned it on, relaunched Zoom (the app caches its permission state at startup, so you have to restart it), mic came alive. Ninety seconds, class started on time.

About 60% of “mic not working” tickets resolve by fixing privacy settings or selecting the right input device. No driver changes, no reinstalls.

Selecting the Right Input

Your laptop probably has more microphones connected than you realize. The built-in mic array, maybe a Logitech webcam mic, your Bluetooth headset, a USB headset you plugged in last month — Windows lists all of these as separate input devices and sometimes defaults to the wrong one. I once helped a customer who had six microphone inputs listed and Windows had defaulted to the HDMI input from his monitor, which had no actual microphone attached. Dead silence on every call for three days.

Go to Settings, System, Sound, Input section. Click the dropdown and pick the microphone you actually want. Then test it right there — click the microphone name, and a “Test your microphone” bar appears. Speak into it. If the bar fills up, Windows can hear you and any remaining problem is app-specific. If the bar doesn’t move at all, the mic is muted somewhere, disabled, or has a driver issue.

Check for mutes in several places: the Settings Sound panel itself, any hardware mute switch on your headset cable or earcup, the Fn-key mic mute that some laptops have in the function row, and Device Manager where the mic might be disabled entirely. If it’s not showing in Device Manager, click View, Show hidden devices. Also try Win+R, mmsys.cpl, Recording tab, right-click in the empty area, Show Disabled Devices and Show Disconnected Devices — mics sometimes vanish from the UI but reappear after toggling those options.

App-Specific Fixes

If the Windows test works but your app can’t hear you, the problem is inside that app. Every communication app has its own audio device selection that’s separate from what Windows defaults to.

Zoom is the one we troubleshoot most. Go to Settings, Audio, change the Microphone dropdown from “Same as System” to your actual mic name. That “Same as System” default sounds harmless but it fails surprisingly often. Hit the Test Mic button right there to confirm. One other thing worth checking — Zoom’s “Automatically adjust microphone volume” checkbox sometimes drives the gain slider down to zero on its own. If your volume keeps dropping mid-call, uncheck that and manually set input to around 80%.

Teams is notorious for losing mic permissions after Windows Updates. Microsoft resets the privacy toggle silently, and your next Monday standup is how you find out. If Teams was working last week and isn’t now, go to Privacy & security, Microphone and flip the Teams toggle off then back on. In Teams itself, click your profile picture, Settings, Devices, pick your mic from the dropdown, and use “Make a test call” to verify.

Discord handles things differently. Gear icon bottom-left, Voice & Video, pick your mic from Input Device, hit the “Let’s Check” button. The thing that gets people on Discord is the input sensitivity slider — auto-sensitivity is aggressive, and if you speak softly or your mic is naturally quiet, Discord decides you’re background noise and gates you out. Switch to manual sensitivity and drag the threshold down until the green bar lights up at normal speaking volume.

If you’re trying to record your screen with audio, OBS also has its own mic selection in Settings, Audio — the same “works in Windows but not in the app” pattern applies. For browser-based apps like Google Meet, the browser has its own per-site permission layer on top of Windows. Go to chrome://settings/content/microphone (or edge://settings/content/microphone) and make sure the site isn’t blocked. Also click the lock icon next to the URL when on the page and check that microphone is set to Allow.

Drivers and Audio Enhancements

Windows 11 applies audio “enhancements” — noise suppression, echo cancellation, beam forming — to mic input by default. On some Realtek and Intel chipsets, these enhancements are so aggressive they suppress your voice entirely. The mic is technically working but Windows is filtering out everything it picks up. Go to Settings, System, Sound, click your microphone in the Input section, find Audio enhancements, set to Off. Test again. If the bar suddenly starts responding, the enhancement processing was the culprit.

If the mic still doesn’t work at the Windows level after disabling enhancements, reinstall the audio driver. Device Manager, expand Sound, video and game controllers, right-click the audio device (usually “Realtek Audio” or “Intel Smart Sound Technology”), Uninstall device, check “Delete the driver software” if it asks, restart. Windows reinstalls a generic driver on boot that works but is basic. Your laptop OEM probably has a full audio driver package — Dell support, HP support, Lenovo support — that includes array mic beamforming tuned for your specific chassis. I’ve seen cases where the generic driver picked up audio fine but the directional beamforming was completely off and the customer sounded like they were in a parking garage.

If the audio services themselves crashed — nothing sound-related works at all, not just the mic — try Win+R, services.msc, find Windows Audio, right-click Restart. Do the same for Windows Audio Endpoint Builder. These two services control all audio I/O and they sometimes stop after a driver crash or a sleep/wake cycle.

Bluetooth headset mic quality dropping is a separate issue and it’s actually the Bluetooth standard’s fault. Bluetooth uses A2DP for music playback (high quality, no mic) and HSP/HFP for calls (bidirectional audio, much lower quality). When you enable the mic, it switches from A2DP to HSP/HFP and music goes from CD-quality to AM-radio-quality. Not much you can do about it except use a wired headset for calls, or buy a newer headset that supports Bluetooth LE Audio which maintains better quality during mic use. If the Bluetooth mic won’t appear at all, remove the device completely from Settings, Bluetooth & devices, then re-pair from scratch — Bluetooth profile negotiation sometimes gets stuck during initial pairing and skips the mic profile entirely. For deeper Bluetooth connection issues, pairing failures, or constant disconnects, our Bluetooth guide covers the pairing-level diagnostic. If your speakers also have no sound alongside the mic, both halves of the audio stack are down — usually a shared driver crash — and we can check Event Viewer audio events and driver state remotely in about twenty minutes.