Before you change anything, find out which of two failures this is. Open the Windows Camera app. If it shows you, the camera works and the problem belongs to the app that was showing black. If it fails too, the problem is between Windows and the hardware, and nothing you change inside Teams will touch it.
| What you see | Where the problem is |
|---|---|
| Camera app works, Teams or Zoom is black | Inside that app — its device picker or its permission |
| Camera app fails too | Between Windows and the camera |
0xA00F4243, or “being used by another application” | Another process has the camera open |
0xA00F4244, or “we can’t find your camera” | Windows is not seeing a camera device at all |
| Preview appears, then goes black after a second | Usually a second app grabbing the device, or a privacy shutter |
When Windows cannot find the camera
Work down this list and stop when the Camera app shows you.
- 1. Look at the lens. Many laptops have a sliding cover over the camera, and many keyboards have a function key with a crossed-out camera on it. Both produce a black picture with no error, and both are invisible from software. Check them before you open any settings.
- 2. Turn the camera on in Windows. Settings → Privacy & security → Camera. Camera access must be on for the device, and Let apps access your camera must be on below it. These are two separate switches and either one alone is enough to produce a camera that “does not work”.
- 3. Close whatever already has it. A webcam may be available to only one program at a time. If Teams, Zoom, OBS or a browser tab with a video call is running, it may have the camera, leaving other applications unable to use it. Finding and freeing the holder is its own short job.
- 4. Check the device is enabled. Device Manager (right-click Start → Device Manager) → Cameras, or Imaging devices on older systems. A camera with a small down-arrow on its icon is disabled; right-click → Enable device. Corporate laptops are sometimes shipped this way on purpose.
- 5. Restart the device. Same place: right-click the camera → Disable device, wait two seconds, Enable device. This releases the camera from anything holding it and reloads the driver without a reboot.
- 6. Roll the driver back if this started after an update. Device Manager → right-click the camera → Properties → Driver tab → Roll Back Driver. If the button is greyed out there is no previous driver to return to, and the next step is the one to use.
- 7. Reinstall the driver — but get the replacement first. Uninstalling the device in Device Manager and then choosing Scan for hardware changes makes Windows install its own driver again. Usually it does. When it does not, you need the camera driver from your laptop maker’s support page, and downloading it while you have no camera and no meeting is much easier than downloading it afterwards. Fetch it before you uninstall anything.
- 8. Check your antivirus. Several security suites ship webcam protection that blocks camera access by default and reports nothing to the application it blocked. If yours has such a feature, look for your meeting app in its allow list.
- 9. For an external webcam, change the port. Move it to a port directly on the computer rather than a hub or monitor, and try a different cable. A USB camera that enumerates intermittently looks exactly like a broken camera.
When only the meeting app is black
The Camera app works, so the hardware and its driver are fine. Two things are left, and each meeting app has its own copy of both.
- The app is pointed at a different camera. Teams, Zoom, Meet and Discord each keep their own device selection. On a laptop in a dock this is the usual cause: the app is still looking at the built-in camera behind a closed lid.
- The app is missing its own Windows permission. Settings → Privacy & security → Camera lists every application separately below the two master switches. A single app switched off there fails while everything else works.
For a call in a browser there is a third copy of the same question: the browser needs the Windows permission, and the site needs permission inside the browser. The full split between Windows and the meeting app covers where each setting lives.
The laptop traps that look like broken hardware
- Two cameras, one lid. A docked laptop with an external webcam has both. Undocking and re-docking changes which devices exist, which is enough for an application to quietly fall back to a different choice than the one you made last week.
- A disabled built-in camera with no fallback. If IT disabled the internal camera and the external one is unplugged or fails to enumerate, there is no camera at all and the error says so.
- Windows Hello still working. Face sign-in uses the infrared camera, which is a separate device. Hello working tells you nothing about whether the colour camera does.
If the call starts in five minutes
Do steps 1, 2 and 3 and nothing else. The shutter, the two privacy switches and other apps using the camera are quick to check and take about ninety seconds between them. Driver work is for afterwards, because a driver reinstall that goes wrong leaves you with no camera at all rather than a broken one.
Finding out while it still matters
These fixes address failures that appear under time pressure. The difficulty is that the error often appears just before a call, and Windows does not warn you between calls that something changed.
CallReady sits in the system tray and answers the question in about ten seconds. One click opens a live preview, confirms the camera starts, and reports the active device, resolution and frame rate. It also checks microphone signal, speaker availability, the light on your face, and network latency and jitter. It remembers the devices from your last successful check and reports when Windows has switched to a different camera, allowing you to catch the docked-laptop failure before the call.
It does not name the process holding your camera or reinstall a driver. It lets you find the problem earlier, when closing OBS takes ten seconds.