Mic Not Working on Windows 11: Walk the Full Permission-to-Driver Path
Launch Companion Diagnostic Tool
Test your hardware right now in your browser with zero install:
Open Mic TestYour microphone is almost certainly being blocked by Windows 11's layered privacy permission system, a mis-routed default device assignment, or a corrupted audio driver left behind by a feature update. These are not vague software gremlins. Windows 11 introduced a three-layer permission gate that sits above the old Control Panel audio stack: OS-level privacy toggles, per-app capability grants, and the new audio session routing in the modern Settings app. Any one of those layers can silently block audio capture while the device still shows green in Device Manager. Driver corruption is the second major cause, specifically when a Windows Update replaces a vendor-tuned UAD driver with a generic Microsoft High Definition Audio Class driver, dropping sample rate support and stripping noise-cancellation firmware.
Confirm the Mic Is Actually Receiving Signal Before Touching Settings
Before you touch a single toggle, verify the hardware is live. Open Mic Test in Chrome or Edge, grant the one-time browser permission, and speak at normal volume. The level meter should move. If it does not move at all, you have either a hardware fault, a dead USB port, or a complete driver absence. If it moves but your communication app still shows nothing, the problem is entirely in Windows routing and permissions, which is the more common scenario after a Windows 11 update.
While you are in the test, note the peak dB reading. A condenser USB mic should hit between -18 dBFS and -6 dBFS at conversational distance. A headset mic will typically sit between -24 dBFS and -12 dBFS. Anything below -40 dBFS with the mic close to your mouth points to a gain stage problem, not a permission problem.
Also run a quick Speaker Test to confirm your audio output device is on the same physical interface. Some USB audio dongles enumerate a mic and a headphone output as a single composite device, and Windows 11 sometimes splits them into separate logical devices after an update, breaking the expected routing.
The Three-Layer Windows 11 Permission Check
Go through these in order. Skipping ahead wastes time.
- Open Settings > Privacy & security > Microphone. The top toggle labeled "Microphone access" must be On. This is the OS-level gate. If it is Off, no application, including the browser, gets capture access regardless of any other setting.
- Directly below that toggle is "Let apps access your microphone." Also must be On. This controls the WinRT app layer, which includes Microsoft Teams, the Xbox app, and any Store-distributed application.
- Scroll down to "Let desktop apps access your microphone." This is a separate toggle that controls Win32 processes: Discord, Zoom desktop client, OBS, and similar. This toggle was added in Windows 11 22H2 and is the one most commonly left Off after a feature update because the update resets it to Off as a privacy default.
After confirming all three are On, go back to Mic Test and retest. If signal appears now, you are done. If not, continue.
Default Device Assignment and Exclusive Mode
Open Settings > System > Sound. Under "Input," confirm the correct device is selected in the dropdown. Windows 11 frequently promotes a newly enumerated device, such as a monitor's built-in mic array or a GPU HDMI audio input, to default input when you connect a display or update a graphics driver.
Now open the legacy panel: right-click the speaker icon in the taskbar, select "Sound settings," then scroll to "More sound settings" at the bottom. In the Recording tab, right-click your microphone and select "Properties." Go to the Advanced tab. Uncheck both "Allow applications to take exclusive control of this device" and "Give exclusive mode applications priority." Exclusive mode lets a single application lock the audio device, which means any second application, including diagnostic tools, will see silence even though the first app is capturing fine.
While in Properties, go to the Levels tab. Set the Microphone level to 80 and Microphone Boost to +10 dB as a baseline. Do not run boost at +30 dB; that introduces noise floor artifacts on most consumer capsules.
Driver Rollback and Reinstall Path
Open Device Manager (Win + X, then M). Expand "Audio inputs and outputs" and "Sound, video and game controllers." You are looking for two things: any device with a yellow warning icon, and whether your mic shows as its vendor-specific name (Blue Yeti, Razer Seiren, SteelSeries Sonar, Elgato Wave) or as "USB Audio Device" or "High Definition Audio Device." The generic names mean Windows replaced the vendor driver.
If you see the generic driver, right-click the device, select "Update driver," then "Browse my computer for drivers," then "Let me pick from a list." Uncheck "Show compatible hardware" and look for the vendor entry. If it is not listed, go to the manufacturer's support page and download the current UAD driver package manually. Install it, reboot, and retest.
If the vendor driver is already loaded and the mic is still dead, right-click the device and select "Uninstall device." Check the box to delete the driver software. Reboot. Windows will re-enumerate the device and install a clean driver instance, which clears any corrupted INF registration that a Windows Update may have left behind.
| Symptom | Most Likely Cause | Fix Layer |
|---|---|---|
| No signal in any app, browser shows no level | OS privacy toggle Off or hardware fault | Settings > Privacy & security > Microphone |
| Browser mic works, Teams/Discord does not | Desktop app permission toggle Off (22H2 reset) | "Let desktop apps access your microphone" toggle |
| Mic works in one app, silent in all others | Exclusive mode lock held by first app | Advanced tab, uncheck exclusive mode |
| Very low volume, no boost available | Generic Microsoft HDA driver loaded | Device Manager driver rollback or reinstall |
| Mic disappeared after Windows Update | Default input reassigned to HDMI/monitor mic | Settings > System > Sound > Input dropdown |
If you are also having issues with your webcam's built-in microphone specifically, run a Webcam Test to confirm the camera and its audio stream are both enumerating correctly as a composite device.
Frequently Asked Questions
Why did my mic stop working after a Windows 11 update?
Feature updates, specifically 22H2 and 23H2, reset the "Let desktop apps access your microphone" privacy toggle to Off as part of a privacy-first default policy change. They also frequently swap vendor audio drivers for the generic Microsoft High Definition Audio Class driver, which drops vendor-specific gain staging and DSP firmware. Check both issues before assuming hardware failure.
My microphone shows up in Device Manager with no errors but still does not work. Why?
Device Manager only confirms the driver is loaded and the device is enumerated. It does not validate the privacy permission layer above it. A mic can be fully healthy at the driver level and still be blocked by the OS privacy gate or by an exclusive mode lock held by a background process like a game anti-cheat module or a communication app running minimized.
How do I know if my mic is broken versus just misconfigured?
Use Mic Test directly in the browser. The browser permission request bypasses most Windows audio routing and hits the device more directly than a Win32 app would. If the level meter shows zero movement even in the browser test with the OS privacy toggle confirmed On, the problem is hardware: a failed capsule, a broken USB data line, or a dead internal connector. If the browser test shows signal but your apps do not, it is purely a configuration issue.
Should I use the Windows 11 built-in microphone troubleshooter?
Run it once as a quick pass because it does catch the default device reassignment issue automatically. Go to Settings > System > Troubleshoot > Other troubleshooters > Recording Audio and run it. Do not rely on it as a final answer. It does not touch exclusive mode settings, does not detect driver downgrades, and does not check the desktop app permission toggle introduced in 22H2.
My headset mic works on another computer but not on this Windows 11 machine. What does that confirm?
It confirms the capsule, cable, and TRRS or USB connector are functional. The fault is entirely on the Windows 11 side: driver, permission, or routing. Start at the three-layer permission check and work down to the driver reinstall path. You do not need to test the headset further on other hardware.
Does Windows 11 have a different audio stack than Windows 10?
The core Windows Audio Session API (WASAPI) and the kernel streaming path are the same. What changed is the privacy permission architecture layered on top, the new Settings app audio routing UI that coexists with the legacy Sound control panel, and the update servicing behavior that more aggressively replaces third-party audio drivers with inbox class drivers during feature updates. The hardware interaction is identical; the software gates above it are not.
Launch Companion Diagnostic Tool
Test your hardware right now in your browser with zero install:
Open Mic Test