Two-minute triage: does Windows hear the microphone at all?
Before touching a single setting, establish which side of the line you are on. Open our mic test, allow access when the browser asks, pick your microphone in the input device selector and speak. If the level meter and the real-time waveform move, then Windows has already found the microphone, loaded a working driver and is passing audio to programs. Your problem is not the operating system; it is a specific app choosing the wrong device, lacking permission or being held off by another program, and our guide on a mic that works in the browser but not in Discord, Zoom or games covers that path in detail. Nothing you say in the test leaves your computer, so speak normally.
If the meter stays flat, or the microphone is not even listed in the selector, the fault is somewhere between the plug and the Windows audio stack, and that is what this guide is for. Two more observations from the test help you skip steps later. First, note the exact device names in the selector: a name like 'Microphone (Realtek(R) Audio)' means an analog jack on a Realtek codec, 'Microphone Array' means a laptop's built-in microphones, and 'USB Audio Device' or the product name means a USB microphone or headset. Second, note whether the meter twitches very slightly when you tap the microphone. A faint response means signal is reaching Windows but the gain is nearly zero, which sends you to the volume and boost steps rather than the driver steps.
The rest of this article moves outward from the cheapest checks to the most invasive ones: privacy permissions, then the modern Sound settings, then the classic Sound control panel, then Device Manager and drivers, then hardware-specific quirks such as front-panel jacks and laptop mute keys. Follow it top to bottom and keep the test tab open, because the moment the meter starts moving you have found the layer that was broken and can stop. If you are on Windows 10 rather than 11, the same settings exist; only some page titles differ, and those differences are called out where they matter.
Windows privacy permissions: the master switch and the desktop-app toggle
Windows has a system-wide microphone permission layer that sits above every program, and when it is off, every app in the world reports silence while the hardware is perfectly healthy. On Windows 11, open Settings, then Privacy and security, then Microphone. On Windows 10 the same page is under Settings, Privacy, Microphone. There are three levels here and all three need to be on. The top item, called Microphone access, is the master switch for the whole device; on Windows 10 it appears as a Change button with the text 'Microphone access for this device'. Below it, 'Let apps access your microphone' controls whether programs are allowed to ask at all. Under that is a list of individual apps with their own switches.
The list of individual apps only shows programs installed from the Microsoft Store. Chrome, Firefox, Discord, OBS, Steam games and nearly everything else installed from a downloaded installer are what Windows calls desktop apps, and they are governed by one separate toggle at the very bottom of the page, labelled 'Let desktop apps access your microphone'. This is the single most overlooked switch in Windows audio troubleshooting. When it is off, the built-in Voice Recorder and Microsoft Teams from the Store may work fine while the browser and every game stay silent. Turn it on, then close and reopen the affected program, because many apps only ask for the device when they start.
Two more things about this page are worth knowing. First, it lists the date and time each app last used the microphone, which is a quick way to confirm whether an app is even attempting to open the device. Second, on managed work or school computers these switches can be locked by policy and appear greyed out; if that is the case, no amount of driver work will help and you need the administrator. If the whole page is accessible and everything is on, but the meter in our test is still flat, the operating system is permitting access but not receiving audio, so move on to the Sound settings.
Sound settings and the classic Recording tab
Open Settings, System, Sound and scroll to the Input section. The first thing to check is simply which device is selected under 'Choose a device for speaking or recording'. Windows keeps a separate default for each type of device and will happily pick a webcam or a monitor's built-in microphone over your headset. Select the device that matches the one you are physically using, then look at the Volume slider next to it; a value of zero, or a very low value, produces exactly the flat meter you are chasing. Push it to somewhere around 80 to 100 for now. Just below, 'Test your microphone' runs a short capture and reports a percentage of the total volume it heard; if it stays at zero even with the slider up, the signal is not arriving.
Click the device name to open its properties. If a device is shown as 'Not plugged in', Windows believes the jack is empty even if a plug is in it, which points to the jack-detection section later in this guide. If the device does not appear at all, scroll to the bottom of the Sound page and open 'All sound devices' under the Advanced heading, then look at the Input devices list. A device that has been disabled shows an Allow button rather than 'Don't allow'; click Allow to enable it. On this properties page you will also find the input format and, on Windows 11, an 'Audio enhancements' setting. Set enhancements to Off while you diagnose, because manufacturer processing can gate a quiet voice to complete silence.
The modern page hides a few options that still live in the classic Sound control panel, so open it as well: press Windows key plus R, type mmsys.cpl and press Enter, then choose the Recording tab. Right-click on an empty area of the list and tick both 'Show Disabled Devices' and 'Show Disconnected Devices'. A microphone that had been disabled reappears greyed out; right-click it and choose Enable. Then right-click the device you use and set it as both Default Device and Default Communication Device. These are two different roles. Games and recording software follow the default device, while Skype-style calling apps and some browsers follow the default communication device, and if the two point at different microphones you get the maddening situation where one program hears you and another does not.
Still in the Recording tab, open Properties for your microphone. On the Levels tab there is a slider and, next to it, a small speaker icon; if that icon has a red circle through it, the microphone is muted at the driver level, which nothing in the modern Settings app will tell you. Click it to unmute and raise the slider. Analog microphones on Realtek and similar codecs also show a Microphone Boost slider here; a boost of ten to twenty decibels is normal for a headset mic on a 3.5 mm jack, and without it many headsets are almost inaudible. On the Advanced tab, look at the exclusive mode checkboxes. If 'Allow applications to take exclusive control of this device' is ticked and some background program has grabbed the microphone, everyone else gets silence; untick it for diagnosis. The Default Format dropdown on the same tab is also worth setting to a common value such as 2 channel, 16 bit, 48000 Hz, because a few USB devices misbehave at exotic formats.
Device Manager: drivers, yellow triangles and disabled devices
If the microphone is missing from every list, or it appears but produces nothing with all volumes up, the driver layer is next. Right-click the Start button and choose Device Manager, then expand 'Audio inputs and outputs' and 'Sound, video and game controllers'. The first category lists endpoints such as 'Microphone (Realtek(R) Audio)' or 'Microphone Array'; the second lists the underlying codec or USB device. A yellow triangle on any of these means the driver failed to load, and a small downward arrow means the device has been disabled. For a disabled device, right-click it and choose 'Enable device'. For a yellow triangle, double-click it and read the Device status text; it usually names the error code, and a code 10 or 43 on a USB microphone points to a power or cable fault rather than software.
For driver problems there is a clear order of operations. Right-click the codec entry under 'Sound, video and game controllers' and choose 'Update driver', then 'Search automatically'. If Windows reports that the best driver is already installed, open the Driver tab in the device's Properties and look at whether 'Roll Back Driver' is available. It is available only when a previous driver is still on the machine, and it is the fastest cure when the microphone stopped working right after an update. If neither helps, choose 'Uninstall device', tick the box to attempt to remove the driver software if it is offered, and restart the computer. Windows will reinstall a fresh copy of the driver on boot, which resolves a surprising number of cases where the configuration, not the driver file, had become corrupt.
Which driver matters depends on the hardware. Desktop motherboards and many laptops use a Realtek codec, and the Realtek driver is best obtained from the motherboard or laptop maker's support page rather than from Realtek directly, because the manufacturer's package includes the correct jack layout for that specific board. Many recent Intel laptops route the built-in microphone array through Intel Smart Sound Technology, which appears in Device Manager as Intel SST entries; when those are broken, the internal microphones vanish while a USB headset keeps working, and the fix is the laptop maker's Intel SST and audio driver bundle rather than the Realtek package alone. USB microphones and headsets normally use the generic USB Audio class driver built into Windows and need nothing extra, so when a USB device disappears it is more likely a port, hub or cable problem than a driver one; try a rear port directly on the motherboard.
Two related steps often rescue a microphone that has died after a Windows Update. First, open Settings, Windows Update, Update history, and use 'Uninstall updates' to remove the most recent update if the timing lines up, and check the Optional updates section under Advanced options, where driver updates are offered separately and can be both the cause and the cure. Second, restart the Windows audio services: press Windows key plus R, type services.msc, find 'Windows Audio' and 'Windows Audio Endpoint Builder', right-click each and choose Restart. This clears the audio engine without a reboot and fixes cases where the device list is stale or every program reports that the microphone is in use. If the services refuse to start, that is itself the diagnosis, and a driver reinstall or a system file check is the next move.
Jacks, front panels, laptop mute keys and manufacturer audio apps
Analog microphones have their own set of traps that live outside the Windows Settings entirely. On a desktop, the front-panel audio jacks are wired to the motherboard through a small internal cable and header, and if that cable is unplugged or connected to the wrong header, the front jacks are dead while the rear ones work; plugging your headset into the pink rear jack is the quickest test. The Realtek codec also performs jack detection, meaning it only exposes the microphone endpoint when it senses a plug, and some headsets and splitters are not detected. Open the Realtek Audio Console from the Start menu, go to Device advanced settings, and turn on the option to disable front panel jack detection; the device will then be listed regardless of what the sensor believes. The same console can retask jacks, so if Windows insists a microphone is plugged into a headphone port, choose the correct role from the popup that appears when you connect the plug, or from the connector settings.
The physical shape of the plug matters too. A headset with a single four-contact plug, known as TRRS, needs a port that accepts a combined headphone and microphone signal, which most laptops have and many desktop rear panels do not. Plugged into a headphone-only or microphone-only three-contact jack, the microphone contact is simply not connected, so the headphones work and the mic is silent. A small TRRS-to-dual-TRS splitter fixes this on a desktop with separate green and pink jacks. The reverse also happens: a microphone with a three-contact plug pushed into a laptop's combo jack may not be recognised as a microphone at all, and a USB adapter or a proper TRRS cable is the reliable route.
Laptops add a hardware mute layer that Windows does not always reflect in its own settings. Most business laptops and many consumer models have a function key, typically F4 or one of the keys marked with a crossed-out microphone, that mutes the microphone at the firmware level, and a small LED on that key or on the palm rest lights up when the mic is muted. Press it once, watch the LED, and check the level meter in our test. Some machines also have a physical privacy switch or a BIOS option that disables the microphone entirely, so if the internal mic is missing from every list, a glance in the BIOS setup under the integrated peripherals or security section is worthwhile before spending time on drivers.
Finally, manufacturer audio software sits on top of the Windows driver and can override anything you set. Realtek Audio Console, MSI's Nahimic, Waves MaxxAudio on many Dell laptops, Dolby Access and similar tools apply noise gating, beam forming and automatic gain, and they occasionally pick their own input device or mute the microphone for a mode they consider inactive. Open whichever of these is installed, look for a microphone or recording page, and turn off every effect while you diagnose. In Windows itself, set 'Audio enhancements' to Off on the microphone's properties page in Settings, and on the classic Sound control panel untick 'Disable all enhancements' or its opposite depending on the driver's wording, then retest. If a quiet or missing signal suddenly appears, you have found the culprit, and you can reintroduce enhancements one by one to see which one was hurting you.
The whole procedure as one ordered checklist
Here is everything above condensed into the order that finds the cause fastest. Start with our mic test; if the meter moves, stop here and go to the in-app guide instead. Check the physical basics: mute switch on the headset, boom position, a rear USB port rather than a hub, the correct 3.5 mm jack. Press the laptop's microphone mute key and check the LED. Open Settings, Privacy and security, Microphone, and turn on the master access switch, the app access switch and the desktop apps switch. Open Settings, System, Sound, Input, select the right device, raise the volume, run the built-in microphone test, and set Audio enhancements to Off.
Next, open the classic Sound control panel with mmsys.cpl. On the Recording tab, show disabled and disconnected devices, enable anything greyed out, set your microphone as both the default device and the default communication device, unmute it on the Levels tab and raise the level and boost, and untick exclusive mode on the Advanced tab. Then open Device Manager, enable any disabled entry, and for a yellow triangle or a mic that died after an update, roll back the driver, or uninstall it and restart so Windows reinstalls it. Restart the Windows Audio service. If it is a desktop with a front-panel headset, try the rear jack and disable jack detection in the Realtek Audio Console; check the plug type and use a splitter if needed. Turn off every manufacturer audio effect.
If the meter still does not move after all of that, test the microphone on another computer or phone, and test a different microphone on this computer. A microphone that works elsewhere while this PC hears nothing from any microphone points to the codec or the port, and on a desktop a cheap USB sound adapter is a practical way around a failed onboard jack. A microphone that is silent everywhere is simply broken. And once the meter is moving again but the level is low or the sound is noisy, our guides on a microphone that is too quiet and on static, crackling or buzzing pick up exactly where this one ends.