Windows 11 Camera Not Working: Clear Fixes for Every Cause

Windows 11 camera not working — showing a black screen in Teams or Zoom, giving an error when apps try to access it, or not appearing in Device Manager — has several distinct causes. The right starting point depends on whether your camera has ever worked in Windows 11, or whether it worked before and has recently stopped. This fits into the wider topic we cover in our Complete Guide to Fixing Windows, Browser, and Software Errors.

Camera has never worked: driver issue or Windows permission. Start with Fix 1 (privacy settings) and Fix 3 (driver).

Camera stopped working suddenly: most likely a Windows Update replaced your driver, or a privacy permission was reset. Fix 1 is almost always the cause here.

Camera works in one app but not another: per-app permission issue. Fix 2.

Fix 1: Check Windows camera privacy settings

This is the single most common cause of camera not working on Windows 11. Windows has a layered permission system for camera access, and a Windows Update can reset these settings without warning.

Settings → Privacy and security → Camera. Check all three levels:

• “Camera access” at the top — must be On
• “Let apps access your camera” — must be On
• “Let desktop apps access your camera” — must be On (this is the one that controls Teams, Zoom, and most third-party apps)

Scroll down to see per-app permissions. If the app you’re trying to use appears with “Off”, toggle it on.

After enabling, you usually don’t need to restart — reopen the app and try the camera again.

Fix 2: Per-app camera permission

If camera access is enabled globally (Fix 1 is all On) but one specific app still can’t see it: check whether that app has been granted camera permission specifically. In the Settings → Privacy and security → Camera page, scroll down to the “Let apps access your camera” section — each app that has requested camera access appears here. Find the problematic app and enable its toggle.

Note: apps must have requested camera access at least once for them to appear here. If the app doesn’t appear, try opening it and triggering camera use — it should then show in the permissions list for approval.

Fix 3: Update or reinstall the camera driver

Device Manager → Cameras (or Imaging Devices) → right-click the camera device → Update driver. If the camera doesn’t appear in Device Manager at all, check View → Show hidden devices — it may be disabled or unrecognised.

For laptops with built-in cameras: the best driver comes from your laptop manufacturer’s support page, not from Windows Update or a generic driver download. Manufacturer drivers include firmware-specific configurations for your exact webcam hardware.

For external USB webcams: check the manufacturer’s website for Windows 11 compatible drivers. Some older webcams have no Windows 11 driver but still work with Windows 10 drivers installed manually — Device Manager → right-click → Update driver → Browse my computer → select the downloaded driver folder.

Fix 4: Physical check and camera selector

Before going deeper into software fixes:

• Open the Windows Camera app (search “Camera” in Start) — if it works there, the camera hardware is fine and the issue is app-specific
• For laptops with a privacy shutter: check that it’s physically open (some laptops have a mechanical slider over the camera lens)
• For laptops with a camera selector key or function key: some models have a Fn+F key that toggles the camera. Check whether pressing it changes anything
• For external USB webcams: try a different USB port, preferably USB 2.0 — some older webcams don’t initialise correctly on USB 3.0 ports

Fix 5: Windows Camera app troubleshooter

Settings → System → Troubleshoot → Other troubleshooters → Camera → Run. This automated troubleshooter checks for common camera configuration problems including driver status, privacy settings, and service dependencies. It won’t fix everything, but it’s fast (about 2 minutes) and handles the most common misconfigurations automatically.

Fix 6: Camera in Device Manager — yellow triangle or missing

If the camera appears in Device Manager with a yellow warning triangle:

1. Right-click → Properties → read the specific error code
2. Code 43 (Device descriptor request failed): USB power issue or driver corruption. Try the device on a different USB port; then reinstall the driver
3. Code 10 (This device cannot start): driver problem. Uninstall the device → restart → let Windows reinstall
4. Code 28 (drivers not installed): download driver from manufacturer and install manually

If the camera is completely missing from Device Manager: scan for hardware changes (Action → Scan for hardware changes). If it still doesn’t appear, the camera may be disabled in BIOS — check laptop BIOS settings for an “Internal camera” or “Webcam” option.

Fix 7: Exclusive camera access conflicts

Unlike audio devices, only one application can use the camera at a time on Windows 11. If Teams has the camera open and you try to open Zoom or the Camera app, they’ll see “no camera” or an access denied error even though the camera is working fine.

Close all applications that might be using the camera, wait a few seconds, then open just the one you want to test. Check the taskbar for camera indicator lights or running app icons. Teams and Skype in particular continue running in the background after you close the visible window and may retain camera access.

Fix 8: Windows Hello and camera conflicts

On machines with Windows Hello facial recognition: the IR camera used for face recognition is separate from the RGB camera used for video calls. If Windows Hello was recently configured or reset, it may have locked the camera driver in a state that conflicts with regular webcam use. Settings → Accounts → Sign-in options → Windows Hello Face → Remove → confirm. After removing Windows Hello Face recognition, test the camera in a video app. If it works, you can re-configure Windows Hello Face setup afterward.

Our guide on Teams audio and video setup covers the Teams-specific camera configuration and per-meeting device selection. For camera issues during Zoom specifically, the Zoom guide includes camera permissions within its troubleshooting steps. Microsoft’s camera troubleshooting documentation covers the UVC (USB Video Class) driver and the specific Windows Camera Frame Server service that manages camera access between multiple applications.

Corporate managed devices and camera restrictions

In enterprise environments, IT administrators can disable camera access through Group Policy or Intune device management. If the camera worked on a previous Windows version but doesn’t after a device management enrollment, check with IT. Signs of policy-based restriction:

• The camera toggle in Settings is greyed out with “Managed by your organisation” label
• Camera works in some apps (Teams, which IT has explicitly permitted) but not others
• The camera works in a local administrator account but not in your domain account

These aren’t fixable by users — they require IT policy changes. However, IT can create exceptions for specific approved applications while keeping the camera blocked for general use.

Camera Frame Server service

Windows 11 uses the Camera Frame Server service to manage camera access between multiple applications. When this service crashes or fails to start, all camera access fails simultaneously even though the hardware and drivers are fine.

Services.msc → find “Windows Camera Frame Server” → check its status. If stopped: right-click → Start. If it fails to start, look at its event log entries in Event Viewer → Windows Logs → System → filter for “FrameServer” source. Common causes of Frame Server failure: corrupted Windows system files (run sfc /scannow) or a driver conflict.

OBS, streaming software, and virtual camera conflicts

OBS Studio, XSplit, and similar streaming applications install virtual camera devices. When these virtual cameras are active, they sometimes conflict with how Windows routes camera access to other applications. If camera problems started after installing streaming software:

1. Open the streaming software and deactivate any virtual camera features
2. Restart the application needing the real camera
3. If the real camera now works, configure the streaming software to not run its virtual camera on startup

Testing camera hardware independently

To definitively confirm whether the camera hardware is functional: open the Windows Camera app (press Win → type “Camera” → open). If it shows a live image, the camera hardware and its Windows driver are working — the problem is either permissions for other apps or those apps’ own configuration.

If the Camera app shows a black screen or an error:

• Error 0xa00f4244 (NoCamerasAreAttached): Windows can’t find the camera — driver or hardware issue
• Error 0xa00f4271 (InitializeMediaCaptureFailed): driver initialisation failed — update or reinstall driver
• Error 0xa00f424f (CreateFailed): another app is using the camera exclusively — close other apps

The error code tells you whether the problem is hardware/driver-level or access/permission-level, which guides which fix path to follow.

SFC for camera system file corruption

Administrator Command Prompt:

sfc /scannow

If Windows reports finding and repairing corrupted files, restart and test the camera. Camera-related system files (Windows.Media.Camera DLLs, the UVC driver stack) can be corrupted by failed Windows Updates or disk errors. SFC restores them from the Windows component store, which is more reliable than reinstalling a driver on top of corrupted system files.

Camera quality and performance issues

If the camera works but shows low quality, bad lighting, or poor focus, these are separate from the camera “not working” problem:

• Camera auto-exposure struggles in low light — improve room lighting rather than adjusting software settings
• Many built-in laptop cameras are fixed-focus — blurriness for close-up use is a hardware limitation
• Apps like Teams apply their own compression and processing — the camera may look better in the Windows Camera app than in video calls due to call-quality compression
• Webcam software from the manufacturer (Logitech Capture, Dell PremierColor) provides much more control than the default Windows camera interface for adjusting brightness, contrast, and focus settings

Camera issues are almost always solvable. The privacy settings check (Fix 1) alone resolves more than half of “camera not working” reports on Windows 11, particularly after major Windows updates. If that doesn’t fix it, the Device Manager driver approach combined with manufacturer drivers resolves most of the rest.

Dual-camera laptops: which camera is active?

Some laptops have two cameras — a front-facing webcam and a rear-facing camera (common in convertible/tablet models). Video conferencing apps default to one of them, and switching is done within the app’s video settings, not in Windows. If you’re seeing the wrong camera’s view:

• In Teams: Settings → Devices → Camera dropdown — both cameras appear by name; select the correct one
• In Zoom: Settings → Video → Camera dropdown — same approach
• In the Windows Camera app: click the camera flip icon in the interface to switch between front and rear cameras

This is particularly relevant on Surface devices, Dell XPS with an optional rear camera, and Lenovo Yoga models with dual-camera configurations.

IR camera vs RGB camera in Device Manager

On modern laptops with Windows Hello, Device Manager often shows two separate camera entries: one for the standard RGB webcam (used for video calls) and one for the IR camera (used for facial recognition). They appear similarly in Device Manager but serve different purposes.

If you see “USB2.0 HD UVC WebCam” and “HP HD Camera” (or similar dual entries), the first is likely the IR camera and the second the standard webcam. If you disable the wrong one, you might disable video call capability while Windows Hello still works. Check which camera is which by noting which Device Manager entry disappears when you cover the camera physically. Related: Discord Screen Share Not Working.

The camera on Windows 11 is now more permission-locked than any previous Windows version — by design, for privacy. Understanding the three-level permission hierarchy (Fix 1) is the most important knowledge for diagnosing camera issues on Windows 11, because it’s the change that catches most people off guard after upgrading from Windows 10. If this sounds familiar, Copy Paste Not Working on Windows 11 is worth a look.

Quick diagnosis reference

Symptom	Likely cause	Fix
Camera black in Teams/Zoom, works in Camera app	Per-app permission off	Privacy Settings → Camera → enable for that app
Camera black everywhere including Camera app	Driver issue or privacy master toggle off	Privacy settings check; driver reinstall
Camera missing from Device Manager	Disabled in BIOS, or no driver installed	BIOS check; scan for hardware changes; install driver
Yellow triangle in Device Manager	Driver error (check error code)	Reinstall driver from manufacturer page
Camera works sometimes, not others	Another app has exclusive access	Close all camera-using apps before testing
Greyed out in Settings	Corporate policy restriction	Contact IT

One final note: the Windows Camera app (built into Windows 11) is genuinely useful as a diagnostic tool, not just for photos and videos. If it shows a live feed, hardware and drivers are working. If it shows an error code, that code tells you the exact failure type. Using the Camera app as your first test step — before troubleshooting any specific app — saves significant time by immediately identifying whether you’re dealing with a hardware/driver problem or an app-level permission issue. Our guide on Windows 11 PIN Not Working covers an adjacent issue.