Camera Not Working in Teams? Fix Device Selection, Privacy Settings and Cache Fast
Launch Companion Diagnostic Tool
Test your hardware right now in your browser with zero install:
Open Meeting Readiness CheckYour Teams camera is broken because Windows 11 is either blocking app-level camera access, Teams has cached a stale device GUID pointing to a disconnected peripheral, or the wrong capture device is selected in Teams settings. These three causes account for roughly 90% of camera not working Teams reports. The hardware itself is almost never the failure point — integrated webcams use a UVC-compliant USB descriptor that Windows enumerates at boot, and external webcams like the Logitech C920 or Elgato Facecam use the same path. What breaks is the software layer sitting between the physical sensor and the Teams renderer.
Verify the Camera Is Actually Functional Before Touching Teams
Before adjusting a single Teams setting, confirm the sensor is alive at the OS level. A dead camera looks identical to a blocked one inside Teams, and chasing software fixes on dead hardware wastes time.
- Press Win + R, type
camera, hit Enter. The Windows Camera app opens and immediately requests the default capture device. If you see a live preview, the sensor and UVC driver are functional. If you see error code 0xA00F4244, the device is either physically disconnected or the driver is corrupt — skip to the driver section below. - Open Device Manager: Win + X > Device Manager > Cameras. Your webcam should appear without a yellow exclamation mark. If it shows Code 43, right-click > Uninstall device, tick "Delete the driver software for this device", reboot, and let Windows re-enumerate the UVC driver from its built-in store.
- Run a live frame-rate and resolution check using the Webcam Test tool. It uses the browser's MediaDevices API and bypasses Teams entirely, so a clean result here proves the camera is healthy at the OS level.
If the webcam test shows a live image, the camera hardware is not your problem. Continue below.
Fix Windows 11 Camera Privacy Settings
Windows 11 introduced granular app-level camera permissions under Settings > Privacy & Security. Teams — both the classic Win32 version and the new Teams (work or school) MSIX package — can be individually blocked here, and a blocked state produces no error inside Teams itself. It simply shows a black preview or a generic "camera not found" message.
- Open Settings > Privacy & Security > Camera.
- Confirm Camera access is toggled On at the top of the page. This is the master switch; if it is Off, no app gets camera access regardless of individual toggles.
- Scroll to Let apps access your camera and toggle it On.
- Scroll further to Let desktop apps access your camera and toggle it On. The new Teams MSIX installs as a packaged desktop app and appears in the list above this section. Classic Teams (the Electron-based version) falls under the desktop apps umbrella.
- If you see Microsoft Teams listed individually, confirm its toggle is On.
After changing any of these toggles, do not just switch back to Teams — fully quit Teams from the system tray (right-click the tray icon > Quit), then relaunch it. The permission token is read at process startup.
Select the Correct Camera Inside Teams and Clear the Cache
Teams stores the selected device GUID in a local settings file. If you have ever connected a different webcam, a capture card, or a virtual camera like OBS Virtual Camera or NVIDIA Broadcast, Teams may be pointing at a GUID that no longer exists. This is the most common cause of camera not working Windows 11 Teams reports on machines that previously had a working setup.
Select the correct device:
- In Teams, click your profile picture (top right) > Settings > Devices.
- Under Camera, open the dropdown. You will see every enumerated UVC device. Select your actual webcam by name.
- A live preview thumbnail appears immediately below the dropdown if the selection is valid. No thumbnail means Teams cannot open that device — it is either in use by another process or the GUID is stale.
Kill competing processes: Open Task Manager (Ctrl + Shift + Esc) and end any process that holds the camera: Zoom, Discord, OBS, NVIDIA Broadcast, Snap Camera, XSplit VCam. Windows 11 does not allow two processes to hold an exclusive camera lock simultaneously on most UVC devices.
Clear the Teams cache:
- Fully quit Teams from the system tray.
- Press Win + R, type
%appdata%\Microsoft\Teams, hit Enter. - Delete the following folders entirely: Cache, blob_storage, databases, GPUCache, IndexedDB, Local Storage, tmp.
- Relaunch Teams. It will rebuild these folders on first run. Sign in again if prompted.
For the new Teams (MSIX), the cache path is %localappdata%\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams. Delete the same folder types there.
Pre-Join Camera Check and Full Meeting Readiness Test
Teams shows a pre-join screen before every meeting where you can confirm audio and video before entering. If your camera is working at the OS level but the pre-join preview is black, the issue is almost always the stale GUID or a competing process as described above.
Use the Meeting Check tool to validate camera, microphone, and speaker output together before your next call. It runs entirely in the browser and surfaces device selection conflicts that Teams hides behind generic error messages.
| Symptom | Most Likely Cause | Fix Location |
|---|---|---|
| Black preview in Teams, camera works in Windows Camera app | Stale device GUID in Teams cache or competing process lock | Teams Settings > Devices, then clear cache |
| Camera dropdown in Teams shows no devices | Windows privacy block or UVC driver failure | Settings > Privacy & Security > Camera |
| Camera works in Teams but not in pre-join screen | OBS Virtual Camera or NVIDIA Broadcast selected as default | Teams Settings > Devices, select physical camera |
| Error 0xA00F4244 in Windows Camera app | UVC driver corrupt or device physically disconnected | Device Manager > Cameras > Uninstall and rescan |
| Camera works alone, fails when mic is also active | USB bandwidth saturation on a shared hub | Connect webcam directly to a motherboard USB-A port |
Also confirm your microphone is passing signal using the Mic Test tool. A camera not working Teams situation is frequently accompanied by audio issues from the same root cause — a permission block applied to both devices at once.
Frequently Asked Questions
Why does my Teams camera work in one meeting but not the next?
A virtual camera application like OBS or NVIDIA Broadcast is most likely starting between sessions and grabbing the device lock before Teams does. Set those applications to not launch at startup: Task Manager > Startup apps, then disable OBS Virtual Camera and any NVIDIA Broadcast entries.
Does reinstalling Teams fix camera not working issues?
Rarely. Reinstalling Teams does clear the cache, which is the useful part, but the privacy settings and driver state are untouched by a reinstall. Clear the cache manually first as described above — it produces the same result without the 15-minute reinstall cycle.
My camera shows in Device Manager but Teams still cannot find it. Why?
The device is enumerated but the Windows camera privacy master switch is Off. Teams does not receive the device list at all when that switch is Off — Device Manager is irrelevant to that check. Go to Settings > Privacy & Security > Camera and turn on the top-level toggle first.
Can a USB hub cause camera not working in Teams?
Yes. USB 2.0 hubs have 480 Mbps of shared bandwidth. A 1080p30 webcam at uncompressed YUY2 uses roughly 1.5 Gbps, so it must use on-device MJPEG compression, which still pushes 100-200 Mbps. Add a headset, keyboard, and mouse to the same hub and you can hit saturation. Connect the webcam directly to a rear motherboard port and test again.
The new Teams (work or school) has a different cache location than classic Teams?
Correct. Classic Teams (Electron) caches under %appdata%\Microsoft\Teams. The new Teams MSIX package caches under %localappdata%\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams. Clearing the wrong path does nothing. Check which version you have under Teams > Settings > About Teams — it will say "new Teams" explicitly if you are on the MSIX build.
How do I test my full meeting setup before an important call?
Use the Meeting Check tool. It verifies camera resolution and frame rate, microphone input level, and speaker output in a single browser session without requiring a test call or a second participant.
Launch Companion Diagnostic Tool
Test your hardware right now in your browser with zero install:
Open Meeting Readiness Check