Camera or Microphone Works in Windows but Not Teams or Zoom

If your camera or microphone works in Windows but not in Teams, Zoom, or Google Meet, treat it as a layer problem: first verify Windows privacy access, then pick the exact device inside the meeting app, then check browser permissions if the call runs in Chrome or another browser.

Why This Happens

Windows can detect a webcam or microphone while a meeting app still points to the wrong one. A laptop may have a built-in microphone, a USB webcam, a Bluetooth headset, a monitor microphone, and a dock audio device. "Default" can change after sleep, unplugging a dock, reconnecting Bluetooth, or installing a driver.

That is why the right question is not just "does the microphone work?" It is "does Windows allow it, does the app see it, and did the app choose the same one I tested?"

Step 1: Check Windows Privacy Access

Microsoft's camera and microphone privacy documentation explains the Windows-level controls that can block or allow device access. If an app reports no camera or no microphone, confirm camera and microphone access are enabled for the relevant app type before changing deeper settings.

Step 2: Prove the Microphone Works in Windows

Use Windows sound settings to select the expected input and confirm that the level meter moves while you speak. Microsoft's Windows microphone test instructions are useful because they verify the device outside the meeting app.

Step 3: Choose Devices Inside Teams, Zoom, or Meet

Teams, Zoom, and Meet each keep their own device choices. Microsoft documents call and device settings in Teams. Zoom documents how to test and choose audio settings and video settings. Google explains how to change devices in Google Meet settings.

Step 4: Check Browser Permissions for Web Calls

For Google Meet, Zoom web links, and other browser-based calls, the browser adds another permission layer. Google's Chrome help explains how sites request and manage camera and microphone permissions. A site can be blocked in Chrome even when Windows and the device itself are fine.

Step 5: Watch for Changed Devices

Device changes are easy to miss. Bluetooth reconnects, monitor sleep, docking stations, USB webcams, and headset mute controls can all change what the app uses. If a call worked yesterday and fails today, inspect what changed since the last successful call.

CallReady is built around that pre-call moment. It runs as a Windows tray utility and, in one click, checks camera, microphone, speakers, face presence, lighting, changed devices, and network latency, jitter, and throughput in approximately 10 seconds. It then reports READY, NEEDS ATTENTION, or NOT READY.

CallReady's camera, microphone, face, and lighting analysis is local. There is no account, backend, or analytics. The network test contacts Cloudflare. It does not claim to read Teams, Zoom, or Meet internals, so app-level settings still matter.

Related Fixes

For a full pre-call checklist, start with Test Your Camera and Microphone Before a Video Call. If the app hears you but people say you are quiet, read Microphone Too Quiet on Windows 11. If your camera works but the image looks poor, see Improve Webcam Lighting for Video Calls. If the device is fine but calls still freeze or sound robotic, read Why Video Calls Still Lag on Fast Internet.

Frequently Asked Questions

Get CallReady

Windows 10 version 2004+ and Windows 11 on x64 and ARM64. 7-day full trial, then a lifetime purchase.