Windows 11 Microphone Not Working or Not Detected

Windows 11 Microphone Not Working or Not Detected

You start a call and the other person can’t hear you, or Windows itself shows no microphone connected at all. Sometimes a recording app plays back nothing but silence, or audio so quiet it’s unusable, even though the microphone looks perfectly connected and the app never throws an error. It’s the input-side counterpart to a speaker problem, and the causes don’t overlap nearly as much as you’d expect.

Microphones fail differently than speakers do, mostly because Windows treats input devices with an extra layer of privacy control and per-app device selection that output devices don’t have to deal with. That extra layer means a mic that’s fully functional at the hardware level can still end up silent for reasons that have nothing to do with a driver or a broken connector.

Quick explanation: this guide covers confirming the right microphone is actually selected as the input device, Windows 11’s microphone privacy permissions blocking apps from using it, confirming Windows detects the mic at the device level, an input volume or enhancement setting making audio silent or distorted, another app holding exclusive control of the device, and an outdated or corrupted microphone driver.

For the full feature list and usage details, you can also visit the Fixyfier Documentation.

Quick Answer

A microphone that isn’t working on Windows 11 is most often blocked by a privacy permission, pointed at the wrong input device, or turned down by an input level slider set too low — not a broken microphone. Check Settings > Privacy & security > Microphone first, since it’s the cause unique to input devices and the one most often overlooked, then confirm the correct device is selected both system-wide and inside whichever app you’re actually using it in.

Confirm the Right Microphone Is Actually Selected

The most common cause of a “broken” microphone isn’t broken at all — it’s simply not the one Windows or the app in question is currently listening to. A PC with a built-in laptop mic, a headset mic, and a USB microphone all plugged in at once gives Windows several candidates to choose from, and it doesn’t always pick the one you meant.
Windows’ own input device setting, under Settings > System > Sound, controls which microphone the system defaults to — but a great many apps, video calling tools especially, keep their own separate input device selection that ignores the system default entirely. A mic that’s correctly set as the default in Windows can still go unused if the app itself is pointed at a different, possibly disconnected, device in its own settings menu.
Checking both places rather than just one is worth the extra thirty seconds, especially after plugging in a new headset or USB microphone, since that’s exactly the moment an app’s own setting is most likely to still be pointed at whatever it was using before.

Microphone Privacy Permissions Blocking Access

Windows 11 keeps a dedicated privacy control specifically for microphone access, separate from anything related to output audio, and it operates at two levels — one master switch for whether any app can use the microphone at all, and individual toggles for which specific apps are allowed to. Either one being off produces the exact same symptom: the app records nothing, with no error message explaining why.
This is the cause most unique to microphones specifically, since there’s no equivalent permission gate for speaker output, which is why it’s easy to overlook if you’re used to troubleshooting audio the way you would a sound problem. It’s also an easy setting to trip by accident — declining a permission prompt once, or a Windows update resetting app permissions back toward more restrictive defaults, is enough to silence a microphone that was working fine the day before.
This is worth checking before anything else on this list, since it silences a completely healthy microphone just as effectively as an actual hardware fault would, and it’s often the very first thing to rule out when a mic that was working suddenly isn’t.

Confirm Windows Detects the Microphone at All

Once device selection and privacy permissions check out, the next question is whether Windows recognizes the microphone as connected hardware in the first place. A microphone listed under Device Manager’s Audio inputs and outputs node with a warning icon is a fundamentally different situation from one that isn’t listed there at all.
A warning triangle points to a driver problem Windows already knows about, which an update, rollback, or reinstall can usually resolve directly. A microphone missing from the list entirely suggests something more basic — a loose connection, a disabled device, or, for a USB microphone, a port or cable issue rather than anything at the driver level.
Get-PnpDevice -Class AudioEndpoint | Select-Object FriendlyName, Status
That command lists every audio endpoint Windows currently recognizes, microphones included, along with each one’s status — a fast way to confirm whether the device is present and healthy from Windows’ point of view before assuming anything about drivers or physical connections. Fixyfier’s Windows Tools section also puts a Device Manager shortcut a click away for the same check without digging through Windows Settings first.

Input Volume, Boost, and “Enhancements” Set Wrong

A microphone that’s detected and selected correctly can still come through silent, barely audible, or oddly distorted because of how its input level is configured. Each microphone in Windows has its own volume slider, separate from the system’s overall volume, and a “microphone boost” setting on top of that which amplifies a weak signal — or, turned too high, clips it into distorted noise instead of clearer speech.
Windows’ audio “enhancements” — noise suppression, echo cancellation, and similar processing — sit on the same properties page and are meant to help, but a buggy or overzealous enhancement occasionally does the opposite, filtering out the actual voice signal along with the background noise it was meant to remove. Disabling enhancements entirely is a useful test: if audio suddenly sounds normal again, one of them was the actual cause.
Working through the input level slider, the boost setting, and the enhancements list one at a time — rather than assuming the microphone itself is at fault — catches a surprising share of “my mic is too quiet” and “my voice sounds robotic” complaints that have nothing to do with the hardware.
NordVPN
One Thing Worth Knowing

Protect the Call You're Troubleshooting the Microphone For

A microphone problem almost always shows up in the middle of an actual call — a job interview, a work meeting, a family video chat — often over whatever Wi-Fi happens to be available at the time. NordVPN keeps that connection encrypted while you sort out the audio, whether you're on your home network or a public one you don't fully trust.

Protect This Session

Another App Already Has Exclusive Control of the Device

Some applications, and a checkbox in Windows itself, allow a program to take exclusive control of a microphone while it’s running — a leftover setting that made more sense on older audio hardware than it does today. When one app is holding a microphone exclusively, every other app trying to use that same device at the same time gets silence instead of an explanation.
This shows up most often when a recording app or an older video conferencing tool doesn’t release the microphone cleanly after closing, leaving it locked even though nothing visible is still using it. Closing every app that might be touching audio and trying again is a quick way to rule this out, and the “Allow applications to take exclusive control of this device” checkbox on the microphone’s own properties page is worth turning off if the problem keeps recurring with a specific app.
This cause is easy to miss because nothing about it looks broken — the microphone still shows as connected and enabled the entire time, it’s simply been claimed by something else in the background.

An Outdated or Corrupted Microphone Driver

If device selection, permissions, input levels, and exclusive access all check out and the microphone still isn’t producing usable audio, the driver itself is the remaining likely cause. This applies to a laptop’s built-in microphone just as much as a USB or headset one, since every microphone runs through some driver whether it’s a generic Windows one or something manufacturer-specific.
A driver that’s reverted to a generic version after a Windows update, or one that’s simply gone stale, can produce exactly the symptoms covered so far — detection without usable audio, or audio quality that’s noticeably worse than it used to be. Confirming exactly which driver is currently loaded and active is the fastest way to know whether this is actually the cause before spending time reinstalling anything.
Fixyfier’s System Tools section includes List Installed Drivers, which shows every driver currently installed and active on the system — useful here for confirming whether the microphone is running its proper driver or something more generic has quietly taken its place.

Frequently Asked Questions

Why does my microphone work in one app but not another?

This almost always comes down to per-app device selection or per-app privacy permissions rather than anything wrong with the microphone itself. Many apps keep their own input device setting separate from Windows’ system default, and Windows 11 also lets you grant or deny microphone access on an app-by-app basis — so it’s entirely possible for one app to be correctly configured while another is quietly pointed at the wrong device or blocked outright.

Can a Windows update reset my microphone permissions?

Yes, this happens more often than people expect. Updates occasionally reset privacy settings back toward more restrictive defaults, or install a generic audio driver over a manufacturer-specific one that was working correctly. If a microphone that worked fine yesterday suddenly doesn’t after an update installed, checking the privacy permissions and Device Manager is the fastest place to start.

How can I tell if the problem is the microphone hardware or a Windows setting?

Testing the same microphone on a different PC, or a different microphone on this one, is the clearest way to tell. If a different microphone also produces no sound on this PC, the problem is almost certainly on the Windows side — a permission, a device selection, or a driver — rather than the microphone itself. If the original microphone works fine elsewhere, that points back toward something specific to this PC rather than a dead device.

Let Fixyfier Help You Track Down a Microphone That’s Gone Silent

Fixyfier’s Windows Tools section puts Device Manager a click away for confirming whether Windows still detects the microphone as connected hardware, and its System Tools section includes List Installed Drivers for confirming exactly which driver is actually running it — together, enough to tell a driver problem apart from a permission or device-selection issue before you go any further.
Get Fixyfier from the Microsoft Store