Why the order matters
Almost every microphone guide starts with drivers. That is the wrong end. Driver problems are real but uncommon, and reinstalling a driver takes longer and risks more than the four checks that come before it.
The browser test is first because it is the cheapest possible test that splits the problem. Everything downstream of it (the meeting app, its own device selection, its own permission) is eliminated in one step if the meter moves.
The checks, in order
- Open the microphone test, press start and allow access when the browser asks. Speak normally. If the meter moves, jump to the last section: your hardware is fine and the problem is the application.
- If the browser never asked for permission, look in the address bar for a blocked microphone icon. A previously denied permission is remembered per site and produces exactly this silent failure.
- Check Windows Settings, Privacy and security, Microphone. There are two switches that matter: microphone access for the device, and access for desktop apps. Either one off produces a dead meter with no error.
- Check the physical mute. Headsets mute on the cable, on the earcup or by rotating the boom, and USB microphones have a mute button that is easy to knock. A muted device still appears as present and working.
- Check which device is selected. Windows picks a default that is not always the one you are speaking into, and a laptop with a built-in array microphone will happily select that instead of your headset.
- Only now look at the driver. Device Manager, Audio inputs and outputs: a device with a warning triangle is a real driver problem. A device that looks normal almost never is.
What the browser can and cannot tell you here
| What you see | What it rules out | What is left |
|---|---|---|
| The meter moves when you speak | The microphone, cable, driver, Windows privacy settings and device selection | The application that cannot hear you, and its own device and permission settings |
| Permission prompt appears, meter stays flat | Permissions, and the browser's ability to open the device | A muted device, the wrong device selected, or a hardware fault |
| No permission prompt at all | Nothing about the hardware | A previously blocked site permission, or a system-level block on the browser |
| The browser reports the device is in use by another application | The microphone itself, which clearly works | The other application holding it open, which on Windows is usually a meeting client running in the tray |
| No microphone found at all | Permissions | A disconnected device, a disabled device in Windows, or a driver that is not presenting it |
Compiled by MyGearCheck from the errors the getUserMedia API reports. The middle column is the useful one: each result eliminates a whole class of causes.
The device-in-use trap
Windows lets multiple applications share a microphone, but not always, and some applications take exclusive control. The symptom is confusing: the microphone works in one application and is completely dead in every other, with no error anywhere.
Meeting clients are the usual culprit because they keep running in the tray after you close the window. Quit them properly from the system tray rather than closing the window, then retest.
The browser reports this case specifically, which is why the test is worth running rather than guessing: a device that is present but held by something else produces a different error from a device that is absent.
When it is the application, not the system
If the browser meter moves and your meeting application still hears nothing, the problem is inside that application. Two settings account for most of it: its own input device selection, which is separate from the Windows default, and its own microphone permission, which on Windows 11 is granted per application.
Check the application's audio settings for a device dropdown and a level meter of its own. If its meter is flat while the browser's moves, the application is listening to a different device.
Noise suppression is a less obvious cause. Aggressive noise suppression in a meeting client can gate a quiet microphone almost completely, so you sound present in the browser test and inaudible in the call. Turning it off is a one-click test.
Nothing here worked
At that point the useful next step is to remove your computer from the equation. Plug the microphone or headset into another machine, or into a phone with the right adapter, and test it there. That distinguishes a broken microphone from a broken system in one step.
If it works elsewhere, the fault is in your machine and a driver reinstall is finally a reasonable move. If it fails everywhere, you have a hardware fault and a clear warranty case. Save the test result before you contact support: a dated record showing no input detected is better evidence than a description.
Frequently asked questions
Why does the browser test work but Teams or Zoom cannot hear me?
Because those applications select their own input device and hold their own microphone permission, both separate from the Windows default. Check the device dropdown inside the application first, then its noise suppression setting, which can gate a quiet microphone into silence.
The browser never asks for microphone permission. What now?
The permission was denied earlier and remembered. Click the icon at the left of the address bar, reset the microphone permission for the site, and reload. If there is no icon at all, a system-level policy is blocking the browser.
Does the microphone test record or upload my voice?
No. The audio stream is read in the page, turned into a level and a waveform, and discarded. Nothing is recorded, buffered or sent anywhere. You can confirm it yourself: open your browser's Network tab and run the test, and you will see no requests.
Can I choose which microphone the test uses?
Yes, once you have granted permission. Before permission is granted, browsers deliberately hide device names, so the selector only fills in after you allow access.
Why is my microphone extremely quiet even though it works?
Windows keeps a per-device input level and a separate microphone boost. A device that was set quiet stays quiet across every application. Raise the level in the sound control panel for that specific device, not the master.
My headset microphone works on my phone but not on my PC. What does that prove?
That the microphone and cable are fine, and the problem is your computer: the port, the driver, or a setting. A combined headphone and microphone jack that only carries headphones is a common cause on desktops.
Does a USB microphone need a driver on Windows 11?
Almost never. USB audio devices use a class driver that ships with the operating system. If a USB microphone needs a manufacturer driver, that is for extra features, not for basic input.
Why does the level meter move when I am not speaking?
That is the noise floor: room noise, fan noise and the microphone's own self-noise. A meter that sits near the bottom and twitches is normal. One that sits high with nothing happening points at a gain set far too high.