Microphone Test: Windows Has Two Inputs, Not One

You are about to join a call, you want to know the microphone works, and the only way you know to find out is to phone somebody and ask them.

Good news: Windows has a test built in that takes about fifteen seconds and costs you no favours. It only tests one microphone though, and your machine almost certainly has more than one.

I counted the audio inputs on this laptop before writing, expecting one, and found two.

The test Windows already has

No website, no download, and no permission prompt.

⭐ Microsoft states the route on its microphone setup page: "Select Start > Settings > System > Sound."

⚡ Then the arrow, which is easy to walk past: "In Input, select the microphone to test and choose > to the right of the device to open the Properties page."

⚠️ The test is on that Properties page. Not on the main Sound screen. That arrow is the whole trick.

⛔ Microsoft says what to do next: "select Start test and speak normally. Select Stop test and choose Play to hear your recorded sample."

Why the bar does not move

The commonest reason a test fails, and it is not a broken microphone.

⭐ Windows reports two capture devices on this laptop. Two, on an ordinary machine with nothing plugged in.

⚡ Add a headset, a webcam or a monitor with a camera and you have four. Every one of them appears as a separate input.

⚠️ The test only tests the one highlighted in Input. Speak into a headset while the built-in microphone is selected and nothing moves.

⛔ So pick the device first, then test. That single order change fixes most of these.

What a good result actually looks like

Microsoft describes the buttons and not the outcome, so this part is ours.

⚡ Play the sample back rather than trusting the level. Hearing yourself is the only real proof.

⭐ A level that moves but stays tiny means the input volume is low, not that the microphone is faulty. There is a slider on the same page.

⚠️ A level pinned to the top is the other failure. That is what people hear as distortion on calls.

⛔ Speak at the distance you actually use. Testing with your mouth on the microphone tells you nothing about a meeting.

What a passing test rules out, and what it does not

The useful half, and it saves a lot of driver reinstalling.

⭐ A passing test means the hardware, the driver and Windows are all fine. That is three things eliminated in fifteen seconds.

⚡ It says nothing about the app you are about to use. Apps pick their own input and have their own permission.

⚠️ If Windows hears you and Teams does not, that is an app problem. Which device it grabbed is the usual answer.

⛔ And if the test itself finds nothing at all, this is the wrong page. Eight fixes, easiest first.

Online microphone testers, and whether to bother

Short, and the answer is mostly no.

⚡ They work by asking your browser for permission to use the microphone, then showing you a level.

⭐ That is a real permission you are granting to a website. Windows asks for nothing because it already has access.

⚠️ The browser one does test the browser path, which is genuinely useful if your problem is only in web meetings.

⛔ For everything else, the built-in test is better and it is not on the internet. Same answer, nothing granted.

The mute you cannot see

It catches somebody every week, and naming it is ours.

⭐ Laptops and headsets have physical mute switches, on a function key, an inline remote or the earcup.

⚡ A hardware mute is invisible to the Windows test. The level stays flat and everything on screen looks correct.

⚠️ Check the key with the crossed out microphone before you conclude anything from a test.

⛔ Some keyboards have a light on that key. If it is lit, that is your answer and nothing else matters.

What this laptop reports

Counted rather than assumed, and the split is the useful part.

⚡ Five audio endpoints in total, all working. Two are inputs. Three are outputs.

⭐ Nothing is plugged in. Those two inputs are what the machine has on its own.

⚠️ So a test on this machine could be pointed at the wrong one of two before any headset arrives.

⛔ Read your own list in Settings, System, Sound, under Input. The number of entries is usually a surprise.

Status: audio endpoints counted here on 29 August 2026, on a Windows 11 Home 25H2 laptop, against Microsoft's own microphone setup page. ⛔ No recording was made or kept, no test audio was saved, nothing was changed, and no device name is published.

How do I test my microphone in Windows 11?

Settings, System, Sound. Under Input, select the microphone you want, then choose the arrow to its right to open its Properties page. Select Start test, speak normally, then Stop test and Play to hear the sample back. Hearing yourself is the proof, not the moving bar.

Why does the microphone test show nothing when I speak?

Usually because the test is pointed at a different microphone. Windows reports two inputs on this laptop with nothing plugged in, and a headset or webcam adds more. Select the right device in Input first. Then check for a physical mute switch on the laptop or headset.

Do I need an online microphone test website?

Not for Windows. The built-in test does the same job without granting a website access to your microphone. A browser based test is worth using for one thing only: checking the path your web meetings actually use, if that is where the problem is.

The Short Version

• The test is in Settings, System, Sound, then the arrow next to your input.
• Microsoft's steps: Start test, speak, Stop test, then Play the sample.
• Play it back. A moving bar is not proof and hearing yourself is.
• Windows reports two inputs on this laptop with nothing plugged in.
• Testing the wrong input is the commonest reason nothing happens.
• A passing test clears the hardware, the driver and Windows in one go.
• It says nothing about the app you are about to use.
• A physical mute switch is invisible to the test. Check the key.

Where to Next

Open Settings, System, Sound and count how many entries are under Input. That number is the first surprise.

Select the one you actually intend to use, then open its Properties with the arrow.

Run the test, then play the sample back rather than judging by the bar.

If Windows hears you and one app does not, stop testing Windows and look at that app's own input setting.

And if your machine reports more inputs than you can account for, say how many in the comments. Nobody publishes what a normal number looks like.