Fix laptop webcam not detected or not working

What is going wrong

A laptop camera that “is not working” is usually one of three different problems: Windows never sees the camera, an app is blocked from using a camera that is present, or the app is pointed at the wrong device. Those are detection, permission, and input selection. They look similar in a video call, and they need different next steps.

This guide is about the built-in webcam (video). A working picture with silent or missing sound is a microphone problem, not a camera-detection problem. Treat those as separate devices even when they sit in the same bezel.

Two conditions change the answer before any driver work. If the lens is covered by a privacy shutter, slider, or sticker, no software fix will restore an image. If another app already has exclusive use of the camera, a second app can fail even though the device is healthy. On some business laptops the camera can also be disabled in firmware; that is a detection failure, not an app setting.

Checks that narrow the cause

Work one layer at a time. Each check only supports a claim about that layer. A black preview in one chat app does not prove the camera is missing from the PC, and a missing Device Manager entry does not prove the module is electrically dead.

Physical camera and keyboard controls

Look at the bezel camera: open any shutter fully and remove anything covering the lens. Then try the camera function key if the keyboard has one (often a camera icon, used with Fn). That key can disable the device at a hardware or firmware level on some models. This check only tells you whether the lens is uncovered and whether a kill-switch is engaged. It does not test drivers, app permissions, or which camera an app selected.

Is the camera detected in Windows?

On Windows, open Device Manager and look under Imaging devices, Cameras, and (if present) Sound, video and game controllers. Also scan Universal Serial Bus controllers for a yellow warning on an unknown USB device. Internal laptop cameras are almost always USB devices attached to the motherboard, so a detection failure often shows up as a missing imaging device, an unknown USB device, or a device with a warning icon.

If the camera is listed without a warning, Windows has enumerated it. That result does not prove any particular app can open it, does not prove the sensor produces a good image, and does not prove the microphone works. If it is missing entirely, or shown as unknown with an error, the problem is below the app: connection, firmware disable, driver binding, or the USB camera function itself. Device Manager also does not test the calling app’s camera picker or OS privacy toggles on Windows 10 and 11.

A related symptom is vendor camera software reporting “no supported device” (Dell Webcam Central is a common example). That message means that program did not find a camera it is written to control. It is not a hardware autopsy. The same PC can still expose a generic USB camera to the Windows Camera app or to a browser even while the vendor utility refuses to attach.

Permission versus exclusive access

If Device Manager lists the camera cleanly but apps cannot open it, check access next. On Windows 10 and 11, camera access is a system privacy switch plus per-app permission (Settings, then Privacy & security, then Camera). Desktop programs and Microsoft Store apps are listed separately. Older Windows versions do not use that privacy page; on those systems, skip this check and treat the failure as driver, exclusive lock, or the app.

Close every app that might hold the camera: Camera, Skype, Teams, Zoom, browsers with camera tabs, conferencing overlays, and vendor utilities. Then open only the Windows Camera app, or a single browser tab. A second app failing while the first still shows live video supports exclusive access, not a dead sensor. This check does not prove which physical camera is selected if the laptop or a dock exposes more than one.

Is the app using this camera?

In the app that fails, open its device or settings panel and confirm the selected video device is the built-in camera, not an IR/Windows Hello camera, a virtual camera, a phone, or a dock/monitor camera. Start a test preview in that same app. Success in Camera and failure in one browser or meeting app points at that app’s picker, site permission, or capture path. Failure in every app, including Camera, points back to detection, a system privacy block, or the device itself.

Browsers add a fourth gate: the site must be allowed to use the camera, and the page must request video rather than only the microphone. Denying camera permission on a site produces a blocked-preview symptom even when Windows and other apps work. That result is scoped to that browser profile and site. It does not mean Device Manager is wrong.

Finding	What it supports	What to check next
Lens covered or camera Fn/kill-switch on	Image cannot appear even if the device is healthy	Uncover the lens, toggle the key, retest in one app
Missing or erroring device in Device Manager	Windows did not bind a working camera driver to the USB camera function	Firmware camera setting, USB errors, driver bind; do not tune app pickers yet
Listed cleanly; every app black or “in use”	Permission, privacy off, or exclusive lock	Windows camera privacy (10/11), close other capture apps
Camera app works; one meeting app or site fails	Input selection, site permission, or that app	That app’s camera list and browser site permission
Vendor utility: no supported device	That utility’s supported-device list, not proof the sensor is dead	Windows Camera or Device Manager, then a current UVC/inbox driver path
Video works, no sound	Microphone path, not webcam detection	A separate microphone check; do not replace the camera for audio

What to change, and how you know it worked

Change only the layer the check implicated. Start with reversible steps. After each change, retest the original symptom in the same app and scene you care about (the meeting tool, not only Device Manager). Stop when the preview is live and the correct camera is selected, or when the remaining work is firmware, parts, or a vendor repair path you have not verified for this chassis.

If the lens or kill-switch was the finding

Open the shutter, remove the cover, and press the camera function key once if you changed it. Retest immediately in one app. Success is a live image. If the image returns only after the key press, leave the camera enabled and treat further “not working” reports as a different layer.

If Windows does not detect the camera

In Device Manager, use Scan for hardware changes. If an unknown USB device or a camera with a warning is present, open it and try Uninstall device, then scan again so Windows can rebind. On Windows 10 and 11 you can also try disabling and re-enabling the camera device. Uninstalling a device is reversible in the sense that a rescan or reboot usually rediscovers it; it can still leave the camera unbound until a matching driver is installed.

If the laptop has a firmware (BIOS/UEFI) camera or USB camera option, set it to enabled. Firmware changes can affect boot security options on some machines; record the current value before you change it and change only the camera-related item. This article does not include a verified, model-specific BIOS procedure for the ASUS N550JV, Acer Aspire 5600U, Razer Blade 15, or the Dell Latitude/Inspiron/Precision models in related reports. Use the firmware screens actually present on that unit, or the maker’s hardware manual for that exact model.

Driver or firmware packages from the PC maker are the usual next step when the device stays missing or erroring. No official driver version, BIOS version, or reset procedure for these models was verified for this article, so do not treat a generic “update the driver” instruction as confirmed for a given chassis. If you install a maker package, use the camera or chipset package listed for that exact model and operating system. Side effects can include a reboot, a temporary loss of the camera during install, and, for a BIOS update, a failed flash if power is lost. After any of those, retest in Device Manager first, then in one capture app.

If the camera is detected but apps cannot open it

• On Windows 10 and 11, turn on camera access for the device, allow desktop apps if you use a Win32 meeting client, and allow the specific Store app if that is what fails.
• Close every other capture app and browser tab, then open only the app you need.
• Sign out or reboot once if an app crashed while holding the camera; that drops a stuck exclusive lock without changing drivers.
• In the failing app, select the built-in camera explicitly and start its own preview.

You will know it worked when that app shows a live preview from the built-in camera, not a still frame, a black tile, or another device. If Camera works and only one site fails, change that site’s camera permission in the browser and retest that site. If every app still fails with a clean Device Manager entry, you have exhausted permission and selection; remaining causes are a hung USB camera function, a bad driver bind, or the module. That is the point to move to a maker driver package or service, not more app toggles.

If only vendor camera software fails

When a utility such as Dell Webcam Central reports no supported device, stop using that utility as the test. Confirm the camera in Device Manager and in the Windows Camera app (or a current meeting app). If those work, the hardware path is fine for generic Video-class use and the vendor program is the wrong tool for that camera. Replacing or “updating” that utility will not fix a Device Manager miss, and uninstalling it will not by itself break a working UVC camera. If Camera also fails, ignore the utility message and follow the detection steps above.

When to stop

Stop software troubleshooting when the camera is still absent after a hardware rescan, the correct firmware camera option is enabled, and a driver bind still fails—or when every app is black despite a clean device entry and open permissions. Those outcomes support a cable/module fault, a failed USB camera function, or a maker-supported repair. They are not proven by a single app’s error message. Do not keep swapping random camera drivers once Device Manager already lists a healthy imaging device and the remaining failure is clearly one application’s picker.

If you also need audio, run a microphone test after video works. Enabling the webcam, granting camera permission, or selecting a camera in a meeting app does not select or unmute the microphone.