Microphone Not Working? The Checklist That Finds It Fast

1. First, is any signal coming in at all?

Start by answering one question: is the computer receiving audio right now? Open the mic test in your browser, allow access, and speak at a normal volume while watching the input meter.

What the meter says, and where it sends you:

• It moves with your voice — the microphone and the operating system are both fine, so the fault is inside one app. Skip to step four.
• It stays completely flat — the fault is physical or system-level. Continue with step two.
• It moves but jumps, cuts out, or spikes on its own — suspect the cable, the connector or a wireless link before you touch any settings.

This single check halves the search space, which is why it belongs first rather than after twenty minutes of clicking through menus. Keep the tab open while you work: you want the meter visible after every change, so that the fix announces itself instead of waiting for the next call to disappoint you. And if the trouble runs the other way — you cannot hear them either — start with the speaker test instead, because a call with no sound in both directions is usually one wrong device selection rather than two faults.

2. Physical checks — mute switches and plugs

The most common cause is also the most humbling. Run these five in order — they take under a minute together and they clear away the causes no amount of software fiddling can reach.

1. Look for a hardware mute: headsets often carry one on the inline remote or an ear cup, and a red marker usually means muted.
2. Confirm the plug is fully seated, and that you have not swapped the microphone and headphone jacks. On color-coded analogue ports the microphone is pink and the headphones are green.
3. If you are using phone earphones, check the plug: a four-pole (TRRS) plug in a PC with separate three-pole jacks leaves the mic dead, and a Y-splitter adapter usually fixes it. The reverse trips people up too: a three-pole microphone plug in the single combo jack of a laptop is often not recognized at all. An adapter works in many cases, but some manufacturers advise against it, so a headset built for the jack you actually have is the surer fix.
4. On wireless gear, confirm the charge and the pairing, then reconnect once before judging.
5. With a USB microphone, plug it straight into a port on the back of the machine. Front-panel ports and unpowered hubs can leave it short of power, and the symptom is an unstable connection rather than a dead one.

The TRRS trap catches people repeatedly because nothing looks wrong — the plug fits, the headphones play sound, and only the microphone is missing. If audio comes out but nothing goes in on a set of phone earphones, that is the first thing to suspect rather than the last.

One more check belongs beside the plug test, because it settles which half of the device is at fault. A headset’s microphone and its earpieces usually arrive over the same connector and appear under the same device entry, so if the headphones are also silent the fault lies in the connection or the selected device rather than in the microphone. Run a headphone check first: sound in both ears narrows the problem to the input path, and silence in both narrows it to something the two halves share.

3. Operating system — permission and input device

If the meter is still flat, the system layer is next. It holds two independent switches that both have to be right, and the first of them silences every app at once when it is off.

1. Turn on the master microphone switch — Windows keeps it under Settings, Privacy, Microphone; macOS under System Settings, Privacy and Security, Microphone.
2. Check the per-app list underneath it, because the master switch being on does not mean your app is allowed.
3. In Settings under System and Sound, open the Input section and confirm the selected device is the microphone you mean to use — a webcam mic or a virtual audio device very often claims the default.
4. If the microphone is not in that list at all, check whether it is switched off rather than missing: on Windows, open Settings, System, Sound, More sound settings, then right-click inside the Recording tab and tick Show Disabled Devices. A disabled input is hidden from the picker entirely, so right-click the microphone that now appears and choose Enable — its absence a moment ago was never evidence that the hardware is dead.
5. Select that device and watch its input level while you speak, so you can tell "no signal" apart from "signal at almost zero volume".

Step three is where most of these cases end. Plugging in a webcam, a monitor with a built-in mic, or a virtual audio driver from any recording tool can silently move the default input, and the system keeps working perfectly — it is just listening to a device on the other side of the room. Watch the meter after each change rather than at the end, or you will never know which step did it.

4. Apps and browsers keep their own settings

If the system meter moves but one app stays silent, that app is the culprit. Every layer above the system has its own memory, and these are the four places it hides:

• The app's own microphone picker, which can point at a different device than the system default.
• The in-app mute button, including the one your meeting software turns on by default when you join.
• The site permission in your browser — click the padlock in the address bar; a "block" chosen months ago still applies today.
• The browser's own default microphone, set on its settings page and separate from the system one.

Stale browser blocks are worth their own sentence, because they explain a surprising share of "it worked last week" reports. The dialog appears once, you dismiss it while distracted, and the site is denied permanently with no further prompting. The same wall blocks video, so if the camera is dark on the same call, our guide on a webcam not working covers that half of the problem.

5. Drivers, then the final verdict — hardware or not

Still silent? Two moves remain, and the second one gives you a definite answer rather than another theory.

1. Open the device manager, look for warning marks on audio input devices, then uninstall the driver and reboot — or install the latest version from the manufacturer. Uninstall only the entry for the microphone itself — a USB mic usually appears as “USB Audio Device”. Leave the built-in audio driver (Realtek and similar) alone: removing that one takes the speakers with it.
2. Run a swap test: connect the microphone to another computer or a phone, and connect a different microphone to this machine.

The swap test is the whole diagnosis in one step. If the mic fails elsewhere too, the hardware is faulty and no amount of settings archaeology will help; if it works elsewhere, the fault lives in this machine's jack, drivers or configuration. Either way you now know which object to spend money or time on. If the microphone is still under warranty, file the claim rather than reaching for a screwdriver — opening it usually ends the coverage.