Microphone Not Detected on Windows: Fix It in Order

When a microphone is not detected in Windows, work in this order: confirm the mic and port are good, then check the Microphone privacy toggles, then check that the device is selected and enabled in Sound settings, then fix the driver in Device Manager. Most “it worked yesterday” cases are a port, a privacy toggle, or a driver that an update replaced. Checking in that order means each step rules out one layer before you touch the next.
The order matters because the fixes get more disruptive as you go. Reseating a USB plug costs ten seconds. Uninstalling a driver means a restart. Start cheap, and stop as soon as the mic appears.
All Windows setting paths below come from Microsoft Support pages, and each one names the Windows version it applies to. Windows 10 and Windows 11 label the same switches differently, so use the path that matches your system.
First, decide which problem you actually have
“Not detected” covers two different failures, and they have different fixes.
- Windows cannot see the device at all. The mic is missing from Sound settings and from Device Manager, or it shows an error. That is a hardware, port or driver problem.
- Windows sees it, but an app cannot use it. The mic shows up in Sound settings and may even pass the built-in test, yet Zoom, Discord or your recording software hears nothing. That is almost always a privacy permission or a wrong device selection inside the app.
| What you see | Most likely layer | Go to |
|---|---|---|
| Mic missing from Sound settings and Device Manager | Port, cable or power | Step 1 |
| Mic listed in Device Manager with a warning icon or “Code 10” | Driver, or a known update issue | Steps 4 and 5 |
| Mic listed in Sound settings, but apps hear nothing | Privacy permissions | Step 2 |
| Mic works in one app but not another | App’s own input selection or desktop app permission | Steps 2 and 3 |
| Mic was fine until a Windows update | Driver replaced or update bug | Steps 4 and 5 |
Knowing which row you are in saves you from reinstalling drivers for a problem that was one toggle.
Step 1: Rule out the port, cable and mute switch
Microsoft’s own troubleshooting starts with the physical checks: make sure any mute button on the headset or mic is off, and that the device is properly connected, or paired if it is Bluetooth. Then work through the port in this order.
USB microphones
- Unplug the mic, wait a few seconds, and plug it straight into a port on the computer itself, not a hub, dock, monitor port or keyboard pass-through.
- On a desktop, try a rear port on the motherboard rather than a front-panel port. Front ports run through an internal cable and are a common weak point.
- Try a second port, and a second cable if the mic uses a detachable one. Some USB cables carry power only, not data, and a power-only cable will light the mic’s LED without Windows ever seeing it.
- If you use a USB-C adapter, remove it and test with a direct connection.
3.5 mm analog microphones and headsets
Laptop combo jacks and desktop mic jacks are wired differently. A headset with a single four-pole (TRRS) plug expects a combo jack. A mic with a three-pole (TRS) plug expects a dedicated pink mic input. Plugging the wrong kind of plug into the wrong jack often leaves the mic silent or undetected, even though the headphones still play. A splitter or combiner adapter solves the mismatch. If you are weighing a headset against separate headphones and a mic for this reason, the trade-offs are laid out in gaming headset vs headphones and mic.
XLR microphones
Windows never detects an XLR mic directly. It detects the audio interface or mixer the mic plugs into. If the interface is listed but you get no signal, the problem is on the interface side: gain, input selection, or phantom power. A condenser mic needs 48V phantom power to produce any signal, while most dynamic mics do not, which is one reason condenser vs dynamic mics behave so differently in an untreated room and in setup. For how the two connection types compare overall, see USB vs XLR microphone for podcasting.
The fastest single test: plug the mic into another computer or a phone. If it fails there too, no Windows setting will fix it.
Step 2: Check the Microphone privacy settings
This is the most common cause when the mic appears in Sound settings but apps hear nothing. Windows has a device-level switch, an app-level switch, and a separate switch for desktop programs. All three need to be on.
According to Microsoft’s page Turn on app permissions for your microphone in Windows, the paths are:
Windows 11
- Select Start > Settings > Privacy & security, then Microphone under App permissions.
- Make sure Microphone access is turned on.
- Make sure Let apps access your microphone is turned on.
- Under Choose which apps can access your microphone, turn on the apps you use.
- Make sure Let desktop apps access your microphone is turned on.
Windows 10
- Select Start > Settings > Privacy, then Microphone under App permissions.
- Make sure Microphone access for this device is turned on.
- Turn on Allow apps to access your microphone.
- Under Choose which Microsoft Store apps can access your microphone, turn on the apps you use.
- For programs like Zoom or Teams, turn on Allow desktop apps to access your microphone.
The desktop apps switch is the one people miss. Traditional programs such as most recording software and many chat clients do not appear in the per-app list, so the list can look correct while the one switch that governs them is off. Microsoft’s page also notes that support for Windows 10 ended on October 14, 2025, so a Windows 10 machine no longer receives free security fixes.
Step 3: Make sure Windows is using the right microphone
A laptop’s built-in mic, a webcam mic and a USB mic can all be present at once, and Windows or the app may quietly pick the wrong one.
Microsoft’s Fix microphone problems page gives these paths:
- Windows 11: go to Start > Settings > System > Sound. Under Input, use Choose a device for speaking or recording to select your mic. Open the device to find the microphone test, and select Start test while you speak.
- Windows 10: go to Start > Settings > System > Sound and pick your mic under Choose your input device, then speak and watch the level meter.
Also check that the device has not been disabled. Microsoft’s sound troubleshooting page, checked the same day, says that in Windows 11 you go to Start > Settings > System > Sound, select More sound settings under Advanced, open the Recording tab, select the mic, choose Properties, and confirm Use this device (enable) is set under Device usage. In Windows 10, open the mic’s Device properties from Sound settings and make sure the Disable checkbox is cleared.
Finally, check the app itself. Most calling and recording apps have their own input dropdown that overrides the Windows default. If Windows shows the right mic and the level meter moves, but one app is silent, the fix is in that app’s audio settings.
Step 4: Update, roll back or reinstall the driver
If the mic is missing from Sound settings, or Device Manager shows it with a warning icon, the driver is next. Right-click Start and open Device Manager, then expand Sound, video and game controllers. USB mics may also appear under Audio inputs and outputs.
Microsoft’s support pages describe three separate actions, and which one you want depends on when the problem started:
- Update driver. Right-click the audio device, choose Update driver, then Search automatically for drivers. Use this when nothing changed recently.
- Roll back driver. Right-click the device, choose Properties, open the Driver tab and select Roll Back Driver. Use this when the mic stopped working right after an update. The button is grayed out if there is no earlier driver to return to.
- Uninstall and reinstall. Right-click the device, choose Uninstall device, and tick the option to remove the driver (in Windows 10 it reads “Delete the driver software for this device”). Restart, and Windows will try to reinstall the device. If it does not reappear, use Scan for hardware changes in Device Manager.
If you need a manufacturer driver, get it from the maker of your computer or your mic, directly from their own support site. Avoid third-party “driver updater” download sites.
Step 5: Check whether a Windows update is the cause
This is where a mic that “worked yesterday” often lands, and it is the step most guides skip. Updates can change drivers, and sometimes they introduce a known bug that no setting on your side can fix.
As of September 23, 2026, Microsoft’s release notes for the Windows 11 update KB5124010 (a preview for versions 24H2 and 25H2, released September 22, 2026) list a known issue: after installing the September 8, 2026 security update, some USB Audio Class 1.0 devices might fail to start or produce audio. Symptoms Microsoft lists include Device Manager showing “This device cannot start (Code 10)”, no audio, volume controls stuck at zero, and sound settings that are unresponsive or unavailable. At that date, Microsoft said it was working on a resolution and listed no workaround.
What this means in practice:
- If your USB mic or USB audio interface shows Code 10 after a September 2026 update, the cause may not be your hardware, port or settings.
- Check the current status of the issue in Microsoft’s Windows release health notes before you replace anything, because a fix may have shipped since this was written.
- Use Start > Settings > Windows Update to install the latest available update once Microsoft marks the issue resolved.
Checking this before buying a new mic can save you money on hardware that was never broken.
When Windows sees it but it still sounds wrong
Once the mic is detected, a new set of problems can look like “not working”: the mic is so quiet that meters barely move, or it picks up the room more than your voice. Low level is usually gain or input volume. Windows 11 puts the Input volume slider under the mic in Sound settings, while Windows 10 uses the Levels tab in the mic’s properties for Microphone and Microphone Boost. Positioning matters too: many studio mics are side-address, so speaking into the top puts you in the least sensitive zone. Microphone polar patterns explained shows where each type of mic listens hardest.
What this checklist cannot fix
Be realistic about the limits. If the mic fails on a second computer, it is faulty. If a USB port fails for every device you plug in, that port or the motherboard needs attention. And if a known Windows issue is the cause, your only real choices are to wait for Microsoft’s fix or use a different device in the meantime, since no toggle on your side changes it. Editing the registry or running unofficial scripts is not a safe shortcut for any of these cases.
FAQ
Why is my microphone not detected in Windows 11 after an update?
Updates can replace a manufacturer driver with a generic one or introduce a known bug. Try Roll Back Driver in Device Manager, then check Microsoft’s release notes. In September 2026, Microsoft listed a known issue where some USB Audio Class 1.0 devices might fail to start after the September 8 security update.
My mic shows in Sound settings but Zoom or Discord cannot hear it. Why?
That is usually a permission. In Windows 11, turn on Let desktop apps access your microphone under Settings > Privacy & security > Microphone. In Windows 10, the switch is Allow desktop apps to access your microphone under Settings > Privacy > Microphone. Then check the input dropdown inside the app.
Why does my headset play sound but the mic is not detected?
Usually it is a plug mismatch. A four-pole headset plug in a separate mic jack, or a three-pole mic plug in a combo jack, can leave the mic silent while audio still plays. A splitter or combiner adapter matching your jack fixes it.
Does Windows detect an XLR microphone?
No. Windows detects the audio interface or mixer, not the XLR mic itself. If the interface is listed but there is no signal, check its gain, its input channel, and phantom power for a condenser mic.
How do I know if my microphone itself is broken?
Plug it into a different computer or a phone. If it fails there too, the mic or its cable is faulty. If it works elsewhere, the problem is in your Windows settings, driver or port.






