Browser Mic Permission vs Windows Mic Permission — Why Both Can Block You Independently

You click Allow. The browser still says microphone blocked. You check Chrome settings — it says allowed. Windows says allowed. Yet the mic test fails. This happens because microphone access on Windows requires three independent permission layers to all say yes simultaneously — and most troubleshooting guides only address one of them.

The Three Permission Layers

Layer 1: Windows OS Permission

Location: Settings → Privacy & Security → Microphone

This is the system-wide gate. If Windows microphone access is off here, no browser or application can access the microphone regardless of what their own settings say. Windows introduced this gate in Windows 10 version 1903.

Two separate toggles must both be on:

• "Microphone access" — the master switch for the entire OS
• "Let desktop apps access your microphone" — specifically for browsers (Chrome, Firefox, Edge are desktop apps)

What breaks it: Windows Updates sometimes reset these toggles. If your mic stopped working after an update, check here first.

Layer 2: Browser Global Permission

Location: chrome://settings/content/microphone (Chrome) or equivalent in Firefox/Edge

This controls whether Chrome will even ask sites for microphone access. If set to "Don't allow sites to use your microphone," no site will ever receive a microphone prompt — the request is silently blocked before it reaches Layer 3.

What breaks it: Accidentally clicking "Never allow" in a permission prompt, or a browser extension modifying media permissions.

Layer 3: Per-Site Permission

Location: The padlock icon in the address bar on any specific site

This is stored per-domain in Chrome's preferences. When you click Allow or Block in the browser permission prompt, Chrome records the answer for that specific domain. Future visits to the same domain use the stored answer without prompting.

What breaks it:

• Clicking Block once stores a permanent block that never re-prompts
• Clearing browsing data with "Site settings" checked wipes all stored answers
• Using incognito mode — per-site permissions never save in private mode, so every session starts fresh and prompts again
• HTTP vs HTTPS of the same domain are stored as separate permissions
• Different subdomains are separate (meet.google.com and docs.google.com store permissions independently)

Why All Three Must Be "Allow"

Layer 1 off → mic completely unavailable to everything. Layer 1 on but Layer 2 off → browser silently refuses all mic requests from sites. Both on but Layer 3 blocked for this site → this site specifically is blocked while others work fine.

The diagnostic question is: does the mic work on a different site in the same browser? If yes, Layer 1 and 2 are fine — the issue is Layer 3 for the specific site.

How to Check All Three Layers Quickly

Check Layer 1 (Windows):

Settings → Privacy & Security → Microphone → confirm both toggles are On

Check Layer 2 (Chrome global):

Go to chrome://settings/content/microphone — confirm it says "Sites can ask to use your microphone" not "Don't allow"

Check Layer 3 (per-site):

Click the padlock in the address bar → find Microphone → confirm it shows "Allow" not "Block"

See all blocked sites at once:

Go to chrome://settings/content/microphone and scroll to the "Not allowed" section — every site you have ever blocked appears here. Remove any that should be allowed.

The Most Common Scenarios

"I allowed it before and now it is blocked"

Most likely: you cleared browsing data with "Site settings" included. This wipes all Layer 3 permissions. The site will prompt again on next visit — click Allow.

"I am in incognito and it keeps asking"

Expected behavior. Layer 3 permissions never persist in incognito mode. Click Allow each session.

"It works in Chrome but not Firefox"

Each browser maintains its own separate Layer 2 and Layer 3 permission databases. Allowing in Chrome does not affect Firefox.

"It stopped working after a Windows Update"

Check Layer 1. Windows Updates have been known to reset the "Let desktop apps access your microphone" toggle.

"It works on one site but not another"

Layer 1 and Layer 2 are fine. The specific site is blocked at Layer 3. Click the padlock on the broken site and change Microphone to Allow.

Testing After Fixing

After changing any permission layer, refresh the page completely (Ctrl+R or Cmd+R) — the browser permission state is loaded on page load and does not update mid-session. Then run the mic test at miccheckonline.com/mic-test to confirm all three layers are now clear.