Camera video is missing or access is denied in Windows 11
What to do first
For camera problems, check the shutter, Windows permissions, desktop app permissions, and whether the device is enabled, then use the built-in Camera app for a baseline test.
This is a general troubleshooting guide, not an announcement of a current outage.
Affected products and symptoms
- Product
- Windows 11 Camera
- Versions and conditions
- Windows 11
- Error codes and identifiers
- 0xA00F42440x800700050xA00F4292
Symptoms
- The camera image is black
- A message says the camera cannot be found
- An app reports access denied
Causes and conditions
Possible causes include a physical shutter, Windows camera permissions, desktop app permissions, another app using the camera, or a disabled device.
Before you start
- Close other meeting and recording apps that use the camera
- For an external camera, check the cable
- Locate the PC's camera key or shutter
Precautions
- Do not allow camera access for apps or sites that do not need it
- If permissions are grayed out, do not change organization policies without authorization
Tools and official pages used in this guide
Check the official requirements, screen names, and limitations for this procedure.
Step-by-step instructions
Open the lens slider and enable the camera using any side switch or Fn camera key. Reconnect an external camera directly to the PC without a hub and, if possible, try another USB port.
First close meeting apps and browser tabs using the camera. A slider covering the lens is separate from software permissions, so enabling access will not open it. Check whether the indicator is lit and consult the device manual to interpret its status.
Under Settings > Privacy & security > Camera, turn on Camera access and Let apps access your camera, and also enable the affected Store app.
For Teams and browsers, turn on Let desktop apps access your camera. For web meetings, also allow the camera in the browser's site permissions.
Official links for this step
- Camera doesn't work in Windows
Check the official requirements, screen names, and limitations for this procedure.
- Camera doesn't work in Windows
Open Camera from Start. If it works here, Windows and the device are functioning, so reselect the correct camera name in the affected app's settings. If it does not work here either, continue to the next step.
Search for "Camera" in Start and select the Windows Camera app. If you have multiple cameras, use the switch button to select the intended one. If video appears, close Camera before opening the meeting app so you can compare without two apps using the camera simultaneously.
Right-click Start > Device Manager > Cameras, then right-click the affected camera. If Enable device appears, select it. If there is a warning symbol, run Update driver.
Double-click the device entry and also check its status on the General tab. Record any warning number. Work only on the affected camera instead of removing working devices in bulk. After restarting, first check whether the built-in Camera app displays video.
Check the result
- Video appears in the built-in Camera app
- The preview appears when you select the correct camera in the affected app
If the problem continues
- Test an external camera on another PC to isolate a camera hardware fault
- For 0xA00F4243-related errors, restart and try only the built-in Camera app without opening other apps
Scope of this guide
Troubleshooting guide — Ensure that the intended camera image appears in both the Windows Camera app and the affected app.
Frequently asked questions
The Camera app works, but web meetings show no video.
Check the browser's site permissions and the camera selection in the meeting screen. Windows permission alone does not grant site permission.
The permission switch is grayed out.
It is controlled by an administrator or organization policy. Tell the device administrator the affected app's name and displayed code.
Official sources and dates
Source publication or resolution date: Not specified. Sources checked: 2026-09-05. The check date is not the date the problem first occurred. Interface labels can vary between versions and display languages.
Related troubleshooting guides
- WSL 2 error 0x80370102 prevents a distribution from starting
- Restore the WSL optional component when error 0x8007019e appears
- WSL alone cannot resolve names while a VPN is connected
- Hyper-V is missing from Windows Features or cannot be enabled
- WSL 2 or Hyper-V cannot run inside a Hyper-V virtual machine
- Windows Sandbox is missing or cannot start