Quick answer
What this guide helps you determine
Check mute controls, input selection, permission, operating-system privacy and exclusive device use.
Begin with the observable browser result, repeat it under the same conditions, and change one connection, setting or application at a time. A browser result narrows likely causes but does not certify hardware or decide a repair.
Scope of this check
A silent microphone can be muted in hardware, mapped to the wrong input, blocked by site permission, blocked by operating-system privacy, held by another application or disconnected. The live meter and the exact permission error help locate the failing layer.
Step-by-step method
- Check physical mute switches, headset inline controls and interface gain first. Click Start, read the error and choose the intended input. Watch whether the browser or operating-system microphone indicator activates.
- Review the address-bar site setting and the OS privacy permission for the browser. Close voice chat, recording and conferencing applications that may use exclusive mode, then reconnect an external input directly.
- Test the microphone in the operating-system recorder and test a known-good microphone in the same computer. A failure that follows the microphone points toward cable/device hardware; one that stays with the computer points toward configuration or input path.
What to check first
Use these checkpoints to keep the comparison focused. Record the visible behavior rather than assigning a fault label too early.
- Verify hardware mute switches
- Select the correct input device
- Close apps that may hold the microphone
How to read what you see
| Observation | What it can suggest | Useful next check |
|---|---|---|
| Permission is granted but the wrong meter moves | Another input, such as a laptop array, is selected. | Choose the correct label and speak near each mic to confirm. |
| No application receives audio | The problem is below the browser layer. | Check cable, mute, interface, driver and manufacturer support. |
| Only one browser fails | Stored permission, browser profile or extension behavior is likely. | Reset only this site permission and compare a clean current browser. |
Common mistakes to avoid
- Do not disable all privacy protections.
- Do not raise gain to maximum before confirming the selected input.
- Do not send device IDs or private recordings in a support request.
Put the guide into practice
Trace microphone input from the physical device to the operating system, browser and final application. The examples below are teaching scenarios, not recordings or measured repair outcomes.
Check Windows input separately
In Windows Sound settings, choose the intended input and use the available microphone test. Check its input level and physical mute. In Privacy & security, review microphone access for the application category that includes your browser. Settings can differ by Windows build or management policy; the Microsoft instructions below provide the current paths. If Windows does not see the device at all, compare a compatible cable or port before troubleshooting a website.
Illustrative examples. These scenarios explain how to compare observations. They are not measured test reports, customer testimonials or confirmed repairs.
The OS receives speech but the web page does not
- Starting observation
- The operating-system input indicator responds while the browser page is silent or displays a permission message.
- Controlled comparison
- Verify the page selected the same microphone and review access for the browser and that specific site.
- How to interpret it
- The OS observation establishes input in that context; browser selection and permission remain separate.
- Next step
- Reload if requested by the permission interface and deliberately start the test again.
The meter moves but playback cannot be heard
- Starting observation
- Input activity appears while speaking, but a short local playback is silent.
- Controlled comparison
- Test the selected output at low volume, then listen to the recording through a known-working output.
- How to interpret it
- A playback routing problem can resemble a recording problem. A moving meter alone also does not establish intelligible speech.
- Next step
- If output works but the recorded phrase does not, recheck input selection and repeat with processing settings changed one at a time.
Your inspection worksheet
Use Observed working, Needs follow-up or Not tested for each item. These labels describe this session, not a hardware certification.
Notes stay in this open page and are not submitted or saved by the site. Print or save as PDF before leaving or reloading. Test links open a separate tab so you can keep this worksheet open.
-
Hardware and OS input
Record physical mute, selected input and whether the OS receives a spoken phrase.
-
Browser input
Record selected input, permission message and response to speech.
Open test (new tab) -
Playback and final app
Verify output separately, then record whether the meeting or recording app receives the same input.
Continue with a related check
Official setup and troubleshooting instructions
Use the platform or device manufacturer's current instructions when settings differ from this guide.
- Fix microphone problems in WindowsMicrosoft Support
- Camera and microphone permissions in ChromeGoogle Chrome Help
Build evidence another person can use
Write down the exact action, visible result and whether it repeats. Include the browser family, operating-system family, connection type and the single comparison that changed the result. Quote the observation directly—for example, “Permission is granted but the wrong meter moves”—then add where it occurred and which comparison changed it.
Change one condition per comparison and return settings that have no effect. Follow model-specific manufacturer instructions before firmware changes, cleaning, disassembly or warranty action.
When to seek qualified support
If the same problem remains in multiple applications and on another compatible connection or computer, collect the repeatable observations and contact the manufacturer or a qualified technician. Stop using equipment that is physically damaged, unusually hot, wet, sparking or unsafe. Device Test Bench cannot inspect electrical condition or make a repair decision.
Privacy during testing
Our public tests process key events, pointer values, media streams and controller input locally. Do not send private recordings, complete typed text or device identifiers when asking for help. A short description of the behavior, browser and page URL is normally enough.
Questions readers ask
Why does the microphone indicator show activity but the meter is flat?
The browser may be capturing a silent or wrong input, or the page may have lost its audio processing state; reselect and restart.
Can another app block the mic?
Yes. Some drivers or exclusive modes allow only one client, and conferencing tools can keep a stream open.
Primary technical references
The following specifications define the browser APIs discussed in this guide. They are primary web-platform references, not product repair manuals.