There’s a special frustration to a camera that Windows can see but can’t use. Device Manager lists it cheerfully, no yellow warnings, drivers “up to date” — and every app insists no camera exists. This is the detected-but-dead scenario, and it sits one layer above the total-detection failures covered in our full camera troubleshooting guide . If your camera doesn’t appear in Device Manager at all, start there; if it appears but won’t produce an image, you’re in the right place.

The fixes below are ordered by effectiveness, not by depth. A working technician tries the high-probability wins first — privacy resets, driver replacement, the frame server — because those resolve the overwhelming majority of these cases in minutes.

Why this happens

  • The driver enumerates but can’t initialize the sensor. A generic driver loads fine yet lacks the vendor-specific commands to actually start the camera.
  • Camera privacy permissions are denied. Windows blocks all app access while the device itself looks healthy in Device Manager.
  • The Windows Camera Frame Server crashed. This background service brokers camera access; when it hangs, apps see nothing.
  • Another app holds an exclusive lock. Some camera software grabs exclusive access, starving every other app.
  • Antivirus webcam protection is silently blocking. Security suites can intercept camera access without a visible prompt.
  • Corrupted driver files after an update. The driver entry survives but its binaries are damaged, so initialization fails.
  • Conflicting virtual camera software. OBS virtual cameras and similar tools can hijack the camera pipeline.

How to fix it

Work through these in order — diagnose first, then act.

Fix 1: Reset camera privacy permissions

The single most common cause. Windows can deny camera access so completely that apps report the camera as missing.

  1. Open Settings > Privacy & security > Camera.
  2. Toggle Camera access off, wait five seconds, and toggle it back on.
  3. Enable Let apps access your camera and Let desktop apps access your camera.
  4. Open the built-in Camera app and test before trying any third-party app.

Testing with the built-in Camera app matters: if it works there but not in your meeting app, the device is fine and the problem is per-app permission. Grant the specific app access in the same settings page.

Fix 2: Restart the Windows Camera Frame Server

The Frame Server (WindowsCameraFrameServer) brokers camera streams. When it wedges, every app fails identically.

  1. Press Win + R, type services.msc, and press Enter.
  2. Find Windows Camera Frame Server, right-click it, and choose Restart.
  3. If it’s stopped, set Startup type to Manual and start it.
  4. Test the Camera app again immediately.

This service starts on demand, so a manual start followed by a test tells you instantly whether it was the blocker. If the camera works after the restart but fails again later, something is crashing the service — usually a bad driver, which Fix 3 addresses.

Fix 3: Replace the driver with the vendor’s package

“Up to date” in Device Manager means “newest Microsoft has,” not “correct for your sensor.” Install the vendor driver.

  1. In Device Manager, right-click the camera under Cameras or Imaging devices and choose Uninstall device, ticking Attempt to remove the driver if offered.
  2. Download the camera driver for your exact model from the manufacturer’s support site (Dell , HP , or Lenovo ).
  3. Install the vendor package and restart.
  4. Verify the camera now shows the vendor’s device name rather than “USB Video Device.”

To stop Windows from replacing it again, consider disabling automatic driver updates — the generic-driver swap is a repeat offender after feature updates.

Fix 4: Check for exclusive-access locks

One misbehaving app can monopolize the camera, leaving others with a “not found” error.

  1. Close every app that might use the camera: meeting apps, OBS, Discord, browser tabs with camera permission.
  2. Check the system tray and Task Manager for lingering processes (Teams and Zoom love to linger).
  3. In Device Manager > camera Properties > Details, there’s no exclusive-mode toggle for cameras, so the fix is purely about closing holders.
  4. Test with the Camera app after a clean boot if the culprit isn’t obvious (msconfig > selective startup).

Virtual camera tools deserve special suspicion: uninstall or disable the virtual camera in OBS/Streamlabs temporarily and retest. If the physical camera springs to life, reinstall the virtual camera software fresh.

Fix 5: Inspect antivirus webcam shields

Security suites increasingly ship camera guards that fail closed — blocking everything, silently.

  1. Open your antivirus settings and look for webcam protection, camera guard, or privacy sections.
  2. Temporarily disable the webcam shield (not the whole antivirus) and test the camera.
  3. If it works, add your meeting apps to the shield’s allowlist rather than leaving protection off.
  4. Check Windows Security too: Device security has no camera toggle, but third-party suites sometimes register there.

This fix feels unlikely until you’ve seen it three times in one week. Corporate-managed laptops are especially prone: IT may have deployed a camera-blocking policy you can’t see from the user side.

Fix 6: Repair system files and re-register the camera stack

If the driver is correct and permissions are open, corrupted system components are next.

  1. Open an elevated Command Prompt and run sfc /scannow, then DISM /Online /Cleanup-Image /RestoreHealth.
  2. In Settings > Apps > Installed apps, find the Camera app, open Advanced options, and use Repair then Reset.
  3. Restart and test with the Camera app.
  4. As a deeper step, run the Hardware and Devices troubleshooter via msdt.exe -id DeviceDiagnostic from Run.

The Camera app reset clears its local cache and permission state, which fixes cases where the app itself — not the driver — is the broken layer. For broader driver hygiene after this, our missing drivers guide covers keeping the whole stack healthy.

Fix 7: Test in a new user profile

A corrupted user profile can break camera access in ways that follow the account but not the machine.

  1. Open Settings > Accounts > Other users and add a new local user.
  2. Log into the new account and test the Camera app there.
  3. If the camera works in the new profile, your main profile’s permission store or registry is damaged — migrate to the new profile rather than fighting it.
  4. If it fails in the new profile too, the problem is system-wide: consider an in-place repair install of Windows.

Profile corruption is rare but real, and this test takes five minutes. It’s the cleanest way to separate “my Windows is broken” from “my account is broken” before committing to bigger repairs.

Closing

Detected-but-dead cameras are almost always a software layer problem — permissions, the frame server, or a driver that loads but can’t initialize. The order above reflects that: the quick permission and service checks first, the vendor driver reinstall as the heavy hitter, and the profile test as the final separator before a Windows repair. Somewhere in that sequence, your camera almost certainly comes back to life.

Frequently asked questions

Why does my camera appear in Device Manager but not work in any app?
The device enumerating only proves Windows loaded a driver for it — not that the driver can actually talk to the sensor. A mismatched driver, a blocked permission, or a crashed camera frame server can all leave the device listed but non-functional. Each layer needs its own check, which is why this guide works through them in order.
Should I use the manufacturer's driver or the Windows one?
Use the manufacturer’s driver. Microsoft’s generic USB Video Class driver handles basic sensors, but vendor drivers include the initialization sequences for IR cameras, Windows Hello, and model-specific sensors. If Windows Update replaced your vendor driver with a generic one, reinstalling the vendor package is often the entire fix.
Can antivirus software block my camera?
Yes. Several security suites include webcam protection that blocks all camera access by default, sometimes without an obvious notification. If the camera works in the built-in Camera app but not in Zoom or Teams, check your antivirus privacy or webcam-shield settings before reinstalling anything.
Will resetting Windows fix a broken camera?
It can, but it’s the last resort. A reset fixes software-side causes — corrupted drivers, broken permissions, damaged system files — but not hardware faults. Work through this guide first: most detected-but-dead cameras are fixed by a driver reinstall or permission reset, neither of which requires reinstalling Windows.