The message has several forms — Your camera is being used by another application, We can't find your camera, error 0xA00F4243 in the Camera app, a black rectangle where your face should be — and one meaning. Some process on this machine has the camera open, and Windows will not hand it to a second one.
If the call is imminent, work down this list and stop when the preview appears.
The fast path
- 1. Close the other meeting apps. Teams, Zoom, Meet in a browser tab, Webex, Discord, Slack huddles. Not minimised: closed, including from the system tray, where Teams and Zoom both keep running after the window is gone. This resolves most cases on its own, because meeting apps hold the camera for the whole session rather than only while you are on video.
- 2. Close the Windows Camera app. The most common accidental holder, usually opened minutes earlier to check that the camera worked.
- 3. Check for virtual camera software. OBS Studio, NVIDIA Broadcast, Snap Camera, XSplit, ManyCam and Logitech's own utilities all open the physical device to present a processed version of it. If one is running, it owns the camera and everything else sees a virtual one, or nothing.
- 4. Ask Windows who used it. Settings → Privacy & security → Camera, scroll to Recent activity. Windows lists the applications that have recently used the camera and says which one has it now. While the camera is in use the taskbar also shows a small camera indicator, and hovering over it names the application.
- 5. End the process. Task Manager (Ctrl+Shift+Esc), find the application from step 4, end the task. Check Background processes as well as Apps: the holder is often a background instance of something you thought you had closed.
- 6. Confirm it is not the permission. Same Settings page: Camera access on for the device, Let apps access your camera on, and the individual application enabled below. A denied permission produces a similar-looking failure with no useful message. For browser calls the browser needs the permission and the site needs it inside the browser.
- 7. Restart the camera device. Device Manager → Cameras (or Imaging devices) → right-click the webcam → Disable, wait two seconds, Enable. This releases the device from whatever was holding it, without a reboot.
- 8. Reboot. It works, it takes three minutes you do not have, and it is the reason to do step 1 before the call rather than during it.
Why it happens at all
Most webcams are exclusive devices. One process opens the stream and the driver does not multiplex it to a second. Windows added a frame server that allows some sharing, but whether it applies depends on the camera, the driver and how each application asks for the stream, which is why two apps sometimes coexist and sometimes do not.
Three patterns produce almost all of the surprises.
- Meeting apps do not release on window close. Teams and Zoom keep running in the tray, and the camera stays claimed.
- Browser tabs hold the camera indefinitely. A Google Meet tab left open in a background window is still on the call as far as the camera is concerned. Browsers mark such a tab with a recording indicator; look for it before hunting through Task Manager.
- Virtual camera software claims the device at startup. If OBS or NVIDIA Broadcast launches with Windows, the physical camera has been claimed since you logged in, and nothing you close later helps until you close that.
The two-camera problem on docked laptops
A laptop on a dock with an external webcam has two cameras, and the failure looks different: the camera works, but the meeting app is looking at the wrong one, showing the closed lid, a black frame, or a view of the ceiling.
Windows and the meeting application each keep their own device selection and they do not agree by default, so set it in both. Some corporate images disable the built-in camera in Device Manager, and then if the external one is unplugged or fails to enumerate there is no fallback and you get "no camera found". Undocking and re-docking changes which devices are present, which is enough for an application to fall back to a different choice than the one you made last week.
What actually prevents this
Everything above is recovery under time pressure. The error is not hard to fix; it is stressful because you meet it at the moment you have no minutes to spend.
The fix is to move the discovery earlier. Anything that opens the camera fails in exactly the same way a meeting app does, so opening a preview two minutes before the call surfaces the conflict while there is still time to close OBS.
CallReady is built around that. One click from the system tray opens a live camera preview, confirms the camera starts, and reports the active device, resolution and frame rate, alongside microphone signal, speaker availability, lighting on your face, and network latency and jitter. The whole check takes about ten seconds. It also remembers the devices from your last successful check and warns you when Windows has switched to a different camera, microphone or speaker, which is the docked-laptop failure above.
It will not name the process holding the camera; Recent activity in Settings is the tool for that. What it does is tell you there is a problem while you can still act on it.
Ninety seconds before anything that matters
- Close every meeting app you are not about to use, including from the tray.
- Close stray browser tabs that had camera access.
- Open a preview and confirm you see yourself, in the right camera, the right way up.
- Say a sentence and confirm the microphone level moves.
- Then join.