Muted microphone with padlock and fading signal waves
It’s frustrating when your microphone works in Windows Sound settings, but Teams, Zoom, or a browser still shows “no mic” or records silence.

This is often a “handoff” problem: Windows can see the mic, but the app is blocked, pointed at the wrong device, or can’t take control.

Let’s fix it without risky downloads or random “driver updater” tools.

Before you change anything: if this is a work/school PC, your organization may enforce microphone policies. If you suspect that, jump to the “when to stop” section so you don’t waste time.

1. Confirm which microphone Windows is actually testing

Windows can “successfully” test a different mic than the one your app is trying to use (for example: webcam mic vs headset mic).

  • Go to Settings > System > Sound.
  • Under Input, note the selected device name.
  • Click Test your microphone and speak.
  • Then open your app (Teams/Zoom/browser) and select that exact same device in the app’s audio settings.

If you have a USB headset/dock, unplug it and replug it once, then re-check the selected input device.

2. Check Windows microphone privacy permissions (and the per-app toggle)

Microphone icon beside a privacy toggle and shield
A very common pattern is: Windows sound test works, but the app is blocked by privacy controls.

  • Go to Settings > Privacy & security > Microphone.
  • Turn on Microphone access.
  • Turn on Let apps access your microphone.
  • Then check the list below for your specific app (for example, Teams) and make sure it’s allowed.

For browsers, also check Let desktop apps access your microphone (browsers often appear as desktop apps depending on install type).

3. Fix “exclusive mode” conflicts (one app hogging the mic)

Sometimes one application (or an audio utility) takes exclusive control, so other apps can’t use the microphone—even though Windows can still detect it.

  • Go to Control Panel > Sound (you can search “Sound Control Panel”).
  • Open the Recording tab and double-click your microphone.
  • Go to Advanced.
  • Temporarily uncheck Allow applications to take exclusive control of this device.
  • Click Apply, then fully close and reopen the app that can’t hear you.

If this fixes it, you can leave exclusive mode off. If you later need low-latency audio for a specific tool, you can turn it back on.

4. Reset the app’s audio selection and permissions (Teams/Zoom/browser)

Audio mixer slider with warning symbol and microphone icon
Apps cache device IDs. If you changed ports, used Bluetooth, or updated drivers, the cached device can become “dead” even though the mic still works elsewhere.

  • In the app’s audio settings, manually select the microphone again (don’t leave it on “Default” while testing).
  • If the app has a built-in test call/recording, run it.
  • For a browser, open the site’s permission prompt and re-allow microphone access for that site.
  • In Windows, try Settings > System > Sound > Volume mixer and ensure the app isn’t muted and is using the intended input/output devices.

One fast sanity check: close every app that could use audio (Teams, Zoom, Discord, OBS, game launchers), then test again with only one app open.

5. Run the built-in troubleshooter and check for “enhancements” issues

These steps are safe and reversible, and they often fix odd levels or silent input.

  • Go to Settings > System > Sound > Input and look for Troubleshoot (if available on your Windows version).
  • In Control Panel > Sound > Recording, open your mic’s Properties and look for options like Audio enhancements or Enhancements. Temporarily disable enhancements.
  • Set the mic level to a reasonable value (for example 70–90) and ensure it’s not set to 0.

If you’re using Bluetooth, test with a wired headset or USB mic if possible—Bluetooth profiles can switch to a low-quality hands-free mode that behaves differently per app.

6. When to stop troubleshooting and contact support (clear boundary)

This is the part people skip. If you’ve done the steps above and still have the same symptoms, continuing to “poke around” can waste time or introduce new problems.

  • Work/school device with policies: Microphone access toggles are missing/greyed out, or the app is managed. Contact your IT/help desk. They may need to change a policy or approve the app.
  • Driver keeps re-installing or failing: Windows Update repeatedly replaces your audio driver, or Device Manager shows errors. Contact the PC manufacturer support (Dell/HP/Lenovo/etc.) because they can provide the correct OEM audio package.
  • Hardware symptoms: The mic cuts in/out when you touch the cable/port, works only at certain angles, or has loud static on multiple devices. Stop—this points to a bad connector, port, or headset.
  • Security/privacy concerns: You see unknown apps requesting mic access, or mic indicator behaves strangely. Don’t install “fixer” tools. Contact Microsoft support or your IT team and run a trusted security scan.
  • App-side account/tenant issues: In Teams specifically, if mic works in other apps but not in Teams across reboots, your org may have meeting policies or device restrictions. Contact your Microsoft 365 admin.

If you do contact support, it helps to share: the exact mic model, Windows version, the app name/version, and whether the mic works in Windows test + one other app.

Final thoughts

When Windows can hear your mic but an app can’t, it’s usually permissions, exclusive control, or the app pointing at the wrong device.

If you hit managed policies, repeating driver failures, or hardware-level symptoms, it’s a good time to stop and escalate—support can resolve those faster than trial-and-error.