Microphone Not Working? Quick Fixes That Actually Work
⚡ Quick Answer
A completely silent microphone is almost always blocked, muted or misselected rather than broken. Work through the layers in order: run a 10-second browser mic test, allow microphone access in the browser AND in your operating system's privacy settings, check every physical mute switch and mute hotkey, close apps that may hold the mic exclusively, then confirm the correct input device is selected both system-wide and inside the app that can't hear you.
Ten Seconds of Testing Saves an Hour of Guessing
Your mic has gone completely dead — no response in calls, no waveform in recordings, nothing. Before touching a single setting, establish one fact: does any audio from this microphone reach your computer at all?
Open the TestMyPC microphone tester, click Allow, and speak. Two outcomes, two entirely different situations. If the level meter moves, your microphone, cable, port and drivers are fine, and the fault is confined to one app's settings — skip straight to per-app fixes. If the meter shows nothing on any listed device, keep reading: something between the microphone and the operating system is blocking the signal, and this guide works through the blockers in the order they actually occur.
(If your problem is that the meter does move but only faintly, that's a different article — see our guide to fixing a microphone that's too quiet. This one is for a mic that's totally silent.)
Free Tool
🎤 Run the 10-Second Mic Test
Meter moves = app problem. Meter flat = follow the fixes below.
Test Microphone →Fix 1: Both Permission Layers — Browser AND Operating System
This is the fix that solves more dead microphones than any other, and the reason it gets missed is that there are two independent permission layers, and either one can silently block the mic. Granting one does nothing if the other says no.
Layer 1 — the browser. If you ever clicked Block on a microphone prompt, the browser remembers it forever and won't ask again. Look at the address bar: a microphone icon with a red cross means this site is blocked. Click the padlock or tune icon → site settings → set Microphone to Allow, then refresh the page.
Layer 2 — the operating system. Windows and macOS both have privacy controls that sit above every app, browsers included. On Windows 11: Settings → Privacy & security → Microphone. Three things must all be on: "Microphone access" (the master switch), "Let apps access your microphone", and the individual toggle for your browser or meeting app in the list below. On macOS: System Settings → Privacy & Security → Microphone, and enable the toggle for each app — then quit and reopen the app, because macOS applies the change on restart.
The telltale sign of an OS-level block is that the browser prompt behaves normally, permission appears granted, and yet every input device shows a dead-flat meter. The audio stream is being handed to the browser empty.
Fix 2: The Physical Mutes Everyone Forgets
Hardware mutes produce exactly the same symptom as a driver failure — total silence — while every setting on screen looks perfect. Check all of these before touching Device Manager:
Headset inline switches. Nearly every wired headset has a mute slider or button on the cable pod, and they're easy to knock without noticing. USB headsets often add a second mute on the earcup or a flip-to-mute boom arm — on many models, boom up means muted.
Laptop mic mute hotkeys. Many business laptops (ThinkPads, Dell Latitudes, HPs) have a dedicated F-key that mutes the microphone at hardware level, usually with a small LED. It's adjacent to the speaker mute key and gets hit by accident constantly. Press it once and retest.
Desk mic mute buttons. USB desk microphones typically have a touch-sensitive or push mute on the body; some indicate mute with a red light, others just go dark.
👤 Example scenario
A remote worker's headset mic dies mid-week — silent in Teams, silent in the browser test, on every input device. Two hours go into driver reinstalls before anyone checks Windows Settings → Privacy & security → Microphone, where "Let apps access your microphone" has been switched off by a security suite's "privacy hardening" update. One toggle, and the meter springs back to life. The lesson: when every device is silent everywhere, suspect the layers above the hardware first.
Fix 3: Exclusive Mode Conflicts and the Combined-Jack Trap
Another app may own your microphone. On Windows, an application can take exclusive control of an audio device, locking everyone else out — the mic works in that app and is silent everywhere else. Close every app that could plausibly be holding it (meeting apps sitting in the system tray, recording software, voice assistants), then retest. To stop it recurring: Control Panel → Sound → Recording tab → your mic → Properties → Advanced → untick "Allow applications to take exclusive control of this device".
The combined 3.5 mm jack trap. This one catches out anyone with a wired headset. Modern laptops usually have a single combined jack that expects a 4-pole TRRS plug carrying both headphones and mic. Older headsets with two separate 3-pole plugs (pink mic, green headphone) will play audio through that jack but the microphone will be completely dead — the socket has no separate mic input for the second plug. The fix is a TRRS combiner/splitter adapter, a few pounds. The reverse also happens: a TRRS headset plugged into a desktop's headphone-only front port gives sound but no mic. If your headset mic is dead but the headphones work, suspect the jack before anything else.
Fix 4: Drivers and the Missing Device
If the mic doesn't even appear in the tester's device list or in your OS sound settings, the operating system can't see it. On Windows, open Device Manager → Audio inputs and outputs. A warning triangle on the device, or no device at all, points at the driver: right-click → Uninstall device, then restart — Windows reinstalls a fresh driver on boot, which clears corrupted states that a simple update often won't. On a Mac, audio glitches after sleep or an OS update are often cured by restarting Core Audio: open Terminal and run sudo killall coreaudiod, or simply reboot.
If an external mic is missing, also try a different USB port (avoid unpowered hubs) and a different cable before blaming software.
Fix 5: Per-App Device Selection in Zoom, Teams and Meet
If the browser test passes, your hardware is proven and this section is the whole problem. Meeting apps keep their own input selection, independent of the system default, and they routinely cling to a device that's no longer connected or was never the right one.
Zoom: Settings → Audio → Microphone — pick the exact device name that moved the meter, then use Test Mic. Untick "Automatically adjust microphone volume" if levels behave strangely. Teams: Settings → Devices → Microphone, then Make a test call. Meet: gear icon → Audio → Microphone (Meet also needs the browser permission from Fix 1). Discord: User Settings → Voice & Video → Input Device — and check Input Mode, because push-to-talk left enabled is a classic "dead mic" that isn't.
Finally, check the app's own mute: Zoom and Teams both remember mute state between meetings, and a keyboard shortcut (Ctrl+Shift+M in Teams, Alt+A in Zoom) may have muted you without a click.
| Symptom | Most likely cause | First fix to try |
|---|---|---|
| Flat meter, every device, every app | OS privacy setting blocking mic access | Windows/macOS microphone privacy toggles |
| Flat meter in browser, no permission prompt | Site blocked in browser settings | Address bar → allow microphone, refresh |
| One mic dead, others fine | Physical mute switch or hotkey | Check inline pods, boom arm, F-key LED |
| Headset audio works, mic silent | Combined-jack (TRRS) mismatch | Use headset port or a TRRS adapter |
| Works in one app, dead elsewhere | Exclusive mode lock | Close the app; disable exclusive control |
| Mic missing from all device lists | Driver or connection failure | Reseat USB; uninstall driver and restart |
When It Really Is Broken
If you've cleared both permission layers, every mute, exclusive mode and the jack wiring, and the meter is still flat while other microphones on the same machine work — the microphone itself has likely failed. Wired headset mics fail at the cable strain points; built-in laptop arrays fail after liquid exposure. The clinching test is the same one in reverse: try the suspect mic on a second computer or a phone. Dead in two places is a hardware verdict. At that point a budget USB microphone is usually cheaper than a repair, and while you're auditing your setup it's worth running the sound tester too, so you know the output half of your audio chain is clean.