‘We can’t find your camera’ is Windows telling you the device is not on the bus at all. This is a step beyond the black-screen problem: there, Windows sees the camera but gets no frames; here, Windows does not see a camera, period. The distinction matters because the fix ladder is different — detection failures start at the firmware and enumeration layer, not the app layer.

The order is: confirm it is truly missing (hidden devices), check the BIOS toggle, repair the driver stack, then test the hardware. Each step answers whether the camera exists at progressively deeper layers of the machine.

Why this happens

  • Camera disabled in the BIOS/UEFI firmware settings.
  • Driver failed so badly the device cannot enumerate.
  • Windows Update replaced the camera driver with an incompatible one.
  • Sensor ribbon cable disconnected, often after hinge damage or drops.
  • Camera disabled in Device Manager and hidden from normal view.
  • Privacy kill switch (Fn key) cutting the camera at the embedded-controller level.
  • Corrupted USB device enumeration for internally USB-attached cameras.
  • Failed camera sensor module — rare, but real.

How to fix it

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

Fix 1: Show hidden devices in Device Manager

Open Device Manager, choose View > Show hidden devices, and expand Cameras and Imaging devices. A greyed-out camera here means Windows knows the hardware but something disabled it — right-click and enable it. If the camera appears with a warning icon, that is a driver problem (skip to Fix 3). Only if it is absent even among hidden devices do you continue down this guide. This view takes ten seconds and prevents misdiagnosing a merely-disabled camera as a dead one.

  1. Open Device Manager > View > Show hidden devices.
  2. Expand Cameras and Imaging devices.
  3. Enable any greyed-out camera entry.
  4. Note warning icons for the driver fix later.

Fix 2: Check the BIOS camera toggle

Reboot into the BIOS/UEFI setup and find the integrated camera setting — usually under Advanced, Security, or Devices. Confirm it is enabled; firmware updates and resets do flip this toggle, and a disabled camera never enumerates no matter what Windows does. While here, note whether the BIOS lists the camera in its device inventory at all. Save, boot into Windows, and recheck Device Manager. If the BIOS has no camera toggle and no camera in its inventory, continue — the hardware may not be announcing itself. Lenovo documents this toggle on Lenovo support .

  1. Enter the BIOS setup on boot.
  2. Find and enable the integrated camera.
  3. Check the BIOS device inventory for the camera.
  4. Save, boot, and recheck Device Manager.

Fix 3: Reinstall the camera driver from the maker

If the camera appears flagged — or appeared after the BIOS fix but still fails — the driver stack needs rebuilding. Uninstall the camera device in Device Manager, ticking ‘Delete the driver software’, then install the camera driver from the laptop maker’s support page for your exact model and reboot. Maker drivers include the sensor-specific INF and firmware interface that generic Windows drivers lack, which is exactly what failed enumeration needs. The step-by-step detection guide walks the Device Manager sequence.

  1. Uninstall the camera device, deleting the driver software.
  2. Install the maker’s camera driver for your exact model.
  3. Reboot and check for a clean Cameras entry.
  4. Test in the Windows Camera app.

Fix 4: Reset USB enumeration for the camera

Built-in cameras usually attach via an internal USB bus, and corrupted USB enumeration can hide them. In Device Manager, expand Universal Serial Bus controllers and uninstall the USB Root Hub entries (not the host controllers themselves), then reboot — Windows rebuilds the entire USB device tree on boot, which re-discovers the camera. Also try fully shutting down (not restarting), unplugging AC, holding the power button 30 seconds to drain fleets, then booting — the embedded controller re-enumerates everything from cold. Microsoft’s device guidance is in the Windows support hub .

  1. Uninstall USB Root Hub entries in Device Manager.
  2. Reboot and let Windows rebuild the USB tree.
  3. If still missing, do a full cold boot with fleets drained.
  4. Recheck Device Manager for the camera.

Fix 5: Check the Fn kill switch and privacy settings

Some laptops cut the camera at the embedded-controller level via an Fn key or dedicated switch — deeper than a driver disable, invisible to Device Manager until toggled back. Press the camera Fn combination and watch for an indicator. Then check Settings > Privacy & security > Camera to confirm access is enabled; while a permission block does not usually hide the device, some maker utilities tie the kill switch to the permission state. The 24H2 detection guide documents brand-specific kill switches.

  1. Press the camera Fn-key toggle and watch for an indicator.
  2. Check for a dedicated physical camera switch.
  3. Confirm camera access in Privacy & security settings.
  4. Recheck Device Manager after toggling.

Fix 6: Roll back the triggering update

If the camera vanished within a day of a Windows update, the update is the prime suspect. In Device Manager, use Roll Back Driver on the camera if available; otherwise uninstall the current driver and install the laptop maker’s version from before the update. Check Update history to identify the exact update, and consider pausing updates briefly while you stabilize. If a bad driver keeps returning via Windows Update, block driver delivery for the camera’s hardware ID — the procedure is in the driver-update control guide .

  1. Identify the update in Update history.
  2. Roll back or replace the camera driver.
  3. Pause updates while stabilizing.
  4. Block the bad driver via hardware ID if it returns.

Fix 7: Confirm hardware failure with a live USB

Boot a Linux live USB and check for the camera (lsusb in a terminal, or the Cheese app). Absent in Linux, absent in the BIOS inventory, absent in Device Manager with hidden devices shown — that triad is a hardware verdict: the sensor module or its ribbon cable through the display hinge has failed. Hinge flexing breaks these cables over time, and drops accelerate it. The module is cheap but the hinge cable run is fiddly; get a repair quote. Present hardware — seen anywhere — means Windows software is still the fault, so loop back to the driver fixes.

  1. Boot a Linux live USB and check for the camera.
  2. Absent everywhere = sensor or cable hardware failure.
  3. Present anywhere = Windows software fault; revisit drivers.
  4. Get a repair quote for module/cable replacement.

Closing

‘Camera not detected’ is an enumeration problem, and enumeration has a fixed hierarchy: firmware toggle, bus discovery, driver binding. The BIOS check comes early because no Windows fix can conjure a device the firmware hides; the hidden-devices view comes first because a merely-disabled camera is a ten-second fix. The Linux live USB is the final arbiter — hardware that never announces itself on any OS is failed hardware, and everything else is software you can fix. Work the hierarchy in order and you always know which layer failed, which is the difference between a twenty-minute repair and an afternoon of reinstalling drivers for a cable that came unplugged in the hinge.

Frequently asked questions

What does 'camera not detected' mean?
It means Windows cannot see the camera hardware at all — not as a working device, not even as a flagged one. This is different from a black screen, where Windows sees the camera but gets no video. ‘Not detected’ points at the BIOS toggle, a disconnected or failed sensor, or a driver so broken the device cannot enumerate. The fix ladder runs from firmware to hardware.
Why is my camera missing from Device Manager?
A missing camera means the hardware is not enumerating on the USB/internal bus: it is disabled in the BIOS, its driver failed so completely that no device node was created, or the sensor/cable has failed. First check Device Manager with hidden devices shown, then the BIOS camera toggle. Absent in both places means the hardware is not announcing itself.
Can a Windows update make the camera disappear?
Yes. Updates can install an incompatible camera driver that fails enumeration, or flip firmware-adjacent settings that disable the device. If the camera vanished within a day of an update, roll back the camera driver or reinstall the laptop maker’s version. The timing correlation is the strongest diagnostic clue in ’not detected’ cases.
How do I know if my camera is a hardware failure?
The decisive test is a Linux live USB: if the camera is absent there too, and the BIOS shows no camera device, the sensor or its cable has failed — Windows drivers cannot fix hardware that never enumerates. If Linux sees the camera, the hardware is fine and the fault is Windows software, which is fixable.