“Camera not detected” is a different beast from “camera not working.” When an app can’t access the camera, the usual suspect is a permission. When Windows can’t even see the device — nothing in Device Manager, no Imaging devices section at all — you’re dealing with a detection failure, and the fixes live at a lower level: physical switches, BIOS toggles, USB enumeration, and drivers. The good news is that most detection failures are configuration, not dead hardware.

This guide works top-down from the simplest checks (shutter, privacy kill switches) to the deeper ones (BIOS, driver stacks, hardware). It pairs naturally with our companion walkthrough on the best way to fix a camera that’s present but failing , which picks up once the device actually appears in Device Manager. For a related visibility problem, see also our guide on Wi-Fi adapters that vanish from Device Manager .

Why this happens

  • The physical privacy shutter or kill switch is engaged. Many laptops disconnect the camera electrically when the shutter slides closed or a function key disables it.
  • The camera is disabled in BIOS/UEFI. Some firmware has a dedicated camera toggle; if it’s off, Windows never sees the device.
  • A Windows update replaced the driver with an incompatible one. The new driver fails to initialize the sensor, so the device never enumerates.
  • The internal USB connection is loose or failed. Laptop cameras sit on the internal USB bus routed through the display hinge — a damaged ribbon cable breaks enumeration silently.
  • Camera privacy settings block all access. Windows may hide the device from apps entirely when camera access is denied system-wide.
  • Corrupted USB controller drivers. If the host controller driver is broken, everything attached to it — including the camera — can disappear.
  • Antivirus or enterprise policy disabled the camera. Security software and managed-device policies can disable camera hardware at the driver level.

How to fix it

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

Fix 1: Check the physical shutter, switch, and function key

Before touching software, rule out the hardware controls designed to make the camera invisible.

  1. Look for a physical shutter slider above the lens — slide it fully open.
  2. Check for a camera kill switch on the laptop’s side edge and make sure it’s in the “on” position.
  3. Try the camera function key (often Fn + F8 or Fn + F10 — look for a camera icon) and watch for an on-screen indicator.
  4. Open Device Manager and press Action > Scan for hardware changes after each toggle to see if the camera appears.

This resolves a surprising number of cases. If the camera appears in Device Manager only with the shutter open, that’s the intended behavior — the shutter is wired to a hardware disconnect.

Fix 2: Enable the camera in BIOS/UEFI

If no physical control changes anything, check whether the firmware itself has disabled the camera.

  1. Restart and enter BIOS/UEFI (usually F2, F12, or Del at the manufacturer’s splash screen).
  2. Look under Advanced, Security, or Integrated Peripherals for a Camera or Webcam toggle.
  3. Set it to Enabled, save, and exit.
  4. After booting, open Device Manager and scan for hardware changes again.

On business-class laptops (ThinkPad, Latitude, EliteBook), BIOS camera toggles are common and can be flipped by IT policy or accidentally. If the option is grayed out, a supervisor password may be set — that’s an IT conversation, not a Windows one.

Fix 3: Verify camera privacy permissions

Windows can suppress the camera so thoroughly that apps report it as absent. Check the permission layer before assuming hardware failure.

  1. Open Settings > Privacy & security > Camera.
  2. Turn on Camera access and Let apps access your camera.
  3. Scroll down and enable access for desktop apps too — many video apps are desktop apps.
  4. Test with the built-in Camera app rather than a third-party one to isolate permission issues.

If the Camera app works but Zoom or Teams doesn’t, the device is fine — it’s an app permission problem. The same permission screen also reveals whether an administrator has disabled camera access via policy.

Fix 4: Show hidden devices and reinstall the driver stack

A driver that failed to load can hide the camera from the default Device Manager view. Reveal it and rebuild.

  1. In Device Manager, click View > Show hidden devices.
  2. Look under Imaging devices, Cameras, and Universal Serial Bus controllers for grayed-out or error-flagged entries.
  3. Right-click any camera entry and choose Uninstall device (tick Attempt to remove the driver if offered).
  4. Restart — Windows will re-detect and reinstall on boot.

If the camera reappears briefly then vanishes, note any error code: Code 43 or Code 45 point to driver/hardware handoff failures, which our Code 43 GPU guide explains in a different context but with overlapping driver-stack techniques.

Fix 5: Install the vendor’s camera driver manually

The generic driver Windows auto-installs doesn’t initialize every sensor correctly. Get the vendor package.

  1. Find your exact laptop model on the manufacturer’s support site — Lenovo support , Dell support , or HP support .
  2. Download the camera driver for your Windows version (11 or 10, matching your architecture).
  3. Run the installer; if it offers a “clean” or “repair” option, take it.
  4. Restart and check Device Manager — the camera should now enumerate as the vendor-named device.

Vendor camera drivers include the sensor-specific initialization sequences that generic USB Video Class drivers sometimes miss, particularly for IR cameras used by Windows Hello.

Fix 6: Reset the USB host controllers

Because the camera rides the internal USB bus, a corrupted USB controller driver can take it down silently.

  1. In Device Manager, expand Universal Serial Bus controllers.
  2. Right-click each USB Root Hub and USB Host Controller entry and choose Uninstall device — do them one at a time.
  3. Restart the laptop. Windows rebuilds the entire USB stack on boot.
  4. After logging in, scan for hardware changes and check whether the camera appears.

Your keyboard and mouse may freeze momentarily during this — that’s normal, as they’re USB devices too. Use the power button if you need to force the restart.

Fix 7: Test with a live USB and check the ribbon cable

If software has been exhausted, confirm whether the hardware itself is visible to a different operating system.

  1. Create a bootable Linux USB (Ubuntu works fine) and boot from it without installing.
  2. Open the camera app or run lsusb in a terminal and look for the camera module.
  3. If it’s absent in Linux too, the module or its ribbon cable through the hinge has failed — contact the manufacturer’s service.
  4. If it appears in Linux, the hardware is fine and the problem is purely Windows-side — revisit Fixes 4–6, or consider a repair install.

A failed hinge cable typically shows warning signs first: the camera cutting out when you adjust the screen angle. If you noticed that pattern before it died completely, mention it to the repair technician — it narrows the diagnosis to the cable.

Closing

Camera detection failures follow a predictable ladder: physical switch, BIOS toggle, permissions, driver stack, USB bus, hardware. Most cases resolve at Fix 1 or Fix 2 — which is exactly why those come first. If you made it all the way to Fix 7 with no camera in two operating systems, you’ve done the full diagnostic work a technician would do, and you can hand the laptop to service with confidence that it’s a hardware fault, not a setting you missed.

Frequently asked questions

Why does Device Manager not show any camera at all?
A completely missing camera in Device Manager usually means the hardware is disabled at a lower level — a BIOS/UEFI toggle, a physical privacy shutter or kill switch, or a failed USB connection inside the hinge. Driver problems, by contrast, usually still show the device, often with a yellow warning icon or an error code.
Can a Windows update make the camera disappear?
Yes. Feature updates sometimes replace a vendor camera driver with an incompatible generic one, or reset camera privacy permissions so apps see nothing. If the camera vanished right after an update, check Device Manager for driver errors first, then verify the camera access toggle under Settings > Privacy & security > Camera.
Does the privacy shutter affect device detection?
On some laptops, yes. Most shutters only block the lens optically, but certain models wire the shutter to a hardware disconnect that removes the camera from the USB bus entirely. If toggling the shutter makes the camera appear and disappear in Device Manager, that’s by design — leave the shutter open while troubleshooting.
When should I assume the camera hardware is dead?
Consider hardware failure only after the camera is enabled in BIOS, the shutter is open, drivers are reinstalled from the vendor’s official package, and Device Manager still shows nothing — including no unknown devices. Also test a Linux live USB: if the camera is absent there too, the module or its ribbon cable has likely failed.