Skip to content
littleden.blogEvidence-led Windows troubleshooting, without the guesswork
FixesError codesComponentsCommandsWindows updatesWindows 11
Research statusMethodology
Devices & drivers · reviewed troubleshooting

Camera not working in Windows 11: check privacy, app scope and driver state

Separate a disabled camera, permission problem, app-only failure and driver issue before reinstalling anything.

Applies to: Windows 11Change risk: Low to mediumReviewed: 2026-09-17
Do this first
  1. Check any physical camera shutter, switch or Fn-key camera control.
  2. For USB cameras, reseat the connection and try another USB port.
  3. Open Settings > Privacy & security > Camera and confirm the required access is enabled.
  4. Test the camera in the Windows Camera app to see whether the failure is app-specific.

What this problem usually means

A Windows camera problem can be physical, permission-related, app-specific or driver-related. Microsoft’s current path starts by checking the connection or hardware switch, camera privacy permissions and whether the Windows Camera app itself can see the device.

Ordered repair path

Work from the narrowest fix to the broader one.

1

Run the Camera troubleshooter

Low risk

Why this belongs here: Windows 11 provides a Get Help camera diagnostic before driver changes are needed.

  1. Open Get Help.
  2. Run the Camera troubleshooter.
  3. Apply only the identified changes and retest the Camera app.
2

Check Windows Update and optional driver updates

Low risk

Why this belongs here: Microsoft includes Windows and optional driver updates in the camera troubleshooting sequence.

  1. Open Settings > Windows Update.
  2. Check for updates.
  3. Open Advanced options > Optional updates and review relevant driver updates.
  4. Restart after installing a camera-related update.
3

Use rollback only when the failure started after a driver change

Medium risk

Why this belongs here: Driver rollback is useful when the timing points directly to a new driver rather than a permissions or app problem.

  1. Open Device Manager and find the camera.
  2. Open Properties > Driver.
  3. Choose Roll Back Driver if the option is available and the issue began after a driver update.
  4. Restart and test again.
Stop condition

When this guide stops being the right path

If Windows never detects the camera in Device Manager and an external camera also fails on another PC, stop treating the problem as a Windows setting issue.

If the problem is still not fixed

If the camera works in the Camera app but not in one program, troubleshoot that program’s camera selection and permissions rather than reinstalling the camera driver again.

Evidence

Sources reviewed for this page

Primary technical guidance is preferred. A source supports the scope stated here; it does not imply that every possible cause is covered.

Related authority records

Continue with the same failing system

These links share the same component or repair context; they are not generic keyword suggestions.

ErrorCode 10 — Device Manager Code 10: “This device cannot start”

Code 10 means the device could not start; Microsoft’s primary resolution begins with the device driver.

ErrorCode 12 — Device Manager Code 12: Windows cannot find enough free resources for the device

Code 12 is a resource-allocation problem; confirm the exact device before changing other hardware or firmware settings.

ErrorCode 22 — Device Manager Code 22: the device is disabled

Code 22 means Windows sees the device but it has been disabled; enable the device before reinstalling drivers.

ErrorCode 28 — Device Manager Code 28: drivers are not installed

Code 28 means Windows does not have the driver installed for the device; reinstall the device driver rather than applying unrelated fixes.

ErrorCode 31 — Device Manager Code 31: Windows cannot load the required drivers

Code 31 is a device-driver loading failure; keep the troubleshooting scoped to the affected hardware.

ErrorCode 43 — Device Manager Code 43: Windows stopped a device after it reported a problem

Code 43 means a driver controlling the device told Windows that the device failed in some way; driver and hardware context both matter.