Skip to content
littleden.blogEvidence-led Windows troubleshooting, without the guesswork

Devices & drivers troubleshooting

Device Manager errors, missing hardware, driver rollback, cameras and peripheral failures.

Start here

Isolate the physical device/port first, then preserve the Device Manager status or error code before changing drivers.

Escalation boundary

Update, roll back or reinstall only the affected device driver; avoid broad driver-store changes.

Devices & drivers

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.

Reviewed 2026-09-17 · Low to medium
Devices & drivers

Driver problem after Windows Update: update, roll back or reinstall the right device

Use timing and Device Manager status to choose between a newer driver, rollback and device-specific reinstall.

Reviewed 2026-09-17 · Medium
Devices & drivers

USB device not recognized in Windows 11: separate the port, device and driver

Use another port and a direct connection first, then check Device Manager before reinstalling drivers.

Reviewed 2026-09-17 · Low to medium
Devices & drivers

USB mouse or keyboard not working in Windows 11: test the hardware path first

Reconnect, change ports and bypass hubs before changing Windows drivers.

Reviewed 2026-09-17 · Low
Devices & drivers

Network adapter missing in Windows 11: prove device detection before TCP/IP repair

If Windows cannot enumerate the Wi-Fi/Ethernet adapter, DNS flushes and browser resets are the wrong layer; focus on Device Manager, hardware detection and the correct driver.

Reviewed 2026-09-17 · Low to medium
Devices & drivers

Driver install failed or changed unexpectedly: inspect SetupAPI.dev.log before reinstalling everything

Use Windows’ device-installation log to verify what driver package Windows tried to install, when it happened and whether signing/install errors were recorded.

Reviewed 2026-09-17 · Low
Devices & drivers

Driver problem or hardware failure? Build the evidence before replacing parts or reinstalling Windows

Use device state, driver chronology, repeatability and vendor diagnostics to decide when Windows troubleshooting should hand off to hardware support.

Reviewed 2026-09-17 · Low
Scoped errors

Error records in this system

Windows 11 Device ManagerCode 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.

Open error record →
Windows 11 Device ManagerCode 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.

Open error record →
Windows 11 Device ManagerCode 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.

Open error record →
Windows 11 Device ManagerCode 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.

Open error record →
Windows 11 Device ManagerCode 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.

Open error record →
Windows 11 Device ManagerCode 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.

Open error record →
Windows 11 Device ManagerCode 45

Device Manager Code 45: hardware is not connected

Code 45 is a connection/presence state; reconnect or power the hardware before changing drivers.

Open error record →