Start with this check.
Check the physical shutter and open Camera from Start. If it shows a picture, investigate the calling app or website. If it also fails, check the device, permissions and exact error code.
This test may activate your local camera. Point it somewhere without private information. You do not need to upload images here or install an external tester.
Which situation matches yours?
Let’s go step by step.
0 of 5 checks completedMark each check to keep track during this visit.
Inspect physical controls
Check the laptop shutter, switch or privacy key. For a USB camera, check its cable and try a direct connection where possible. Use the manual to identify the key; not every model has one.
Record whether Windows detects the camera and whether its indicator changes. A covered lens is different from a missing device.
Compare the Camera app
Close the video call and open Camera from Start. Record whether there is an image or an error code. Close Camera afterwards so the next comparison does not leave another app using it.
A correct preview establishes that this local workflow works. It does not establish the meeting website has permission.
Review the relevant access
Open Settings → Privacy & security → Camera. Check device and app access, including the separate control for desktop apps. If an administrator locks an option, do not try to bypass it.
Reopen only the app being tested and compare. Changing permission without repeating the test does not confirm a fix.
Identify the selected camera
Use Settings → Bluetooth & devices → Cameras to identify available devices. In the meeting app, choose the device that worked in the test rather than a virtual or disconnected camera.
With several cameras, the comparison is valid only when using the same input. Record its name.
Keep the error before updating
If Camera also fails, save the code and review the corresponding official help. Save work before restarting and use Windows Update or manufacturer support for updates, not advertised universal driver repair bundles.
If only Chrome fails, move to the browser permission guide. For failure everywhere, the code and model are the basis for support.
When to stop and ask for help
A camera still missing after connection checks or access restricted by policy needs manufacturer or administrator support. Avoid registry changes or driver removal without an appropriate procedure for your device.
Does a step differ from what you see? →Common questions
Does 0xA00F4244 prove the camera is broken?
Microsoft associates it with a camera not being detected. Checks still need to separate connections, configuration and possible hardware failure.
Can I leave Camera open during the meeting?
Close it after the comparison to avoid another app interfering with the test.
Must I allow every website?
No. System and website permissions are different controls. Review only the app and website you need.
Sources and review
Project owner: Eudald Ferrer Ibáñez. Report a correction.
This guide uses official documentation and our own troubleshooting sequence. Menus may change between versions. Documentation reviewed on September 28, 2026; practical device testing is still pending.
How we review and correct guides →Have you identified the problem?
Your answer only appears in this browser. It is not sent or saved.