Browser Permissions & WebRTC Diagnostics
How to Fix `NotFoundError: Requested Device Not Found` Webcam Test Error
NotFoundError means no camera matching the browser's request exists at all — either genuinely disconnected hardware, a camera disabled at the operating system level, or a driver that failed to register the device correctly. This is meaningfully different from NotReadableError: there's no working device sitting there being blocked by another app, there's simply nothing found to connect to.
What Causes WebRTC `NotFoundError`?
Before a browser can request access to a camera, it first has to discover that a camera exists at all, through the operating system's own device enumeration. NotFoundError specifically means that discovery step came back empty — from the browser's perspective, no camera is currently available to grant access to, regardless of what the user's actual physical hardware situation looks like.
The most literal cause is genuinely disconnected hardware: an external USB webcam unplugged, or a laptop's internal camera lacking a functioning connection due to a hardware fault. But a significant share of NotFoundError cases involve hardware that's physically present and functioning, just not currently visible to the OS — disabled in Device Manager on Windows, blocked by a privacy toggle at the system level, or affected by a driver that failed to load correctly after a recent update.
A smaller number of cases are caused by the requesting website itself, asking for an overly specific device ID that no longer matches any currently connected camera — for instance, if a site remembers a specific camera by its unique identifier and that exact device has since been replaced with a different one, even of the same model.
Step-by-Step Fixes for Unrecognized Webcams
Step 1: Confirm the camera is physically connected
And, for an external USB webcam, try a different USB port.
Step 2: Check your OS device list
— Device Manager on Windows, System Information on Mac — to confirm the camera is detected at the hardware level at all.
Step 3: If it's missing from that list entirely, check for a physical privacy shutter or function-key kill switch
That might be disabling it before Windows or macOS ever sees it.
Step 4: If it appears in your OS device list but Chrome/Firefox/Safari still can't find it, restart your browser fully
Rather than just reloading the tab, since browsers cache their device list and don't always refresh it automatically.
Step 5: Restart your computer
If the previous steps don't resolve it, which forces a completely fresh hardware and driver re-enumeration. ↑ Test with the widget above.
Distinguishing This From a Permission Problem
It's worth deliberately checking your browser's own error console (F12, then Console tab) to confirm you're actually dealing with NotFoundError specifically, rather than NotAllowedError — the two produce visually similar "nothing works" symptoms to a casual glance, but point toward completely different fixes. NotFoundError means no device was ever discovered; NotAllowedError means a device exists but access was refused. Confusing the two leads to troubleshooting the wrong layer entirely.
If you've recently reinstalled your operating system or performed a major system update, a fresh driver reinstallation for your specific camera model, downloaded directly from the manufacturer's website rather than relying solely on what Windows Update provides automatically, is worth trying if the steps above don't resolve it — generic in-box drivers don't always fully support every feature of every camera model.
A Few More Things to Check on Windows
How do I reset the Windows Camera app itself?
Go to Settings → Apps → Installed apps, find Camera, open its three-dot menu, and choose Advanced options → Reset. This clears the built-in Camera app’s own cache and settings without uninstalling it, which can fix a stuck, frozen, or permanently black preview even when the underlying device and driver are both working correctly. It only resets that one app — not your camera driver, and not other applications that use the camera.
Could my antivirus be silently blocking my camera?
Many third-party security suites — Bitdefender, Kaspersky, Norton, and ESET among others — include their own webcam-protection feature that runs independently of Windows’ own privacy settings. That means Windows can show camera access as fully permitted while the antivirus software blocks it anyway, at a layer Windows has no visibility into. Check the antivirus program’s own settings, usually under a Privacy, Webcam Protection, or similarly named section, and confirm your browser or conferencing app is on its allow-list.
How do I re-enable my camera in Device Manager if it's disabled?
Right-click the Start button → Device Manager, expand Cameras or Imaging devices, and look for a greyed-out icon or a small down-arrow badge. Right-click that entry and choose Enable device. This is a different action from updating a driver — a disabled device won’t respond to any other fix until it’s explicitly re-enabled here first, so it’s worth checking before assuming the problem is a driver or a permission.
Is Windows' own camera privacy toggle blocking access, separately from anything else?
Windows keeps a system-level camera permission at Settings → Privacy & security → Camera, completely separate from Device Manager, the Camera app, and any antivirus software. This one screen has a master Camera access switch plus a per-app list beneath it — both need to be on. It’s worth checking directly, since a camera can show as fully enabled and working in Device Manager while this toggle silently blocks every app from reaching it.
For a full check of resolution, frame rate, and audio together, not just this one issue, the free webcam test covers all of it in one place.