How to Fix Code 10 This Device Cannot Start in Windows

What Code 10 tells you — and what it does not

Code 10 is deliberately vague: Windows is only saying that it asked the driver to start the device and the start failed. The details hide in the driver itself — some log a precise reason, most just fail — so the fix is a process of elimination rather than a one-click cure. The error sits on the General tab of the device's Properties, and the device usually carries the yellow warning triangle next to it.

Two families of causes cover almost every case: a broken, mismatched or half-installed driver, and a resource conflict — no free IRQ, memory range or DMA channel, typically after long uptime or a messy wake from sleep. Physical failure is possible too, but it is far down the list; start with software.

• A driver that failed during its own startup — corrupted install or a bad version
• No free system resources (IRQ, memory ranges) after weeks of uptime or a failed wake
• A version conflict between two drivers fighting over the same device
• Outdated BIOS or firmware that initializes the device incorrectly — typical on laptops
• Genuinely failing hardware — possible, but the last suspect

The fixes, from fastest to deepest

Restart first — a full shutdown and boot, not Sleep — because that alone resets the resource table and cures the after-uptime variant. Then, in Device Manager, right-click the device, choose Uninstall device, and restart so Windows reinstalls it during boot; for USB devices, also try a different port. Next, update the driver with intent: open Settings > Windows Update > Advanced options > Optional updates > Driver updates and install what Microsoft offers, but prefer the vendor's own package — Realtek, Intel, Dell, HP and Lenovo all ship driver installers on their support pages that beat the generic driver search.

On a laptop that shows Code 10 on the same device after every boot, do a power drain: shut down, unplug the charger and (if removable) the battery, hold the power button for 30 seconds, then boot again. If the error dates back to a Windows update, roll the driver back on the Driver tab or uninstall the update in Settings > Windows Update > Update history. The remaining depth move is a BIOS update from the manufacturer — a real fix for Code 10 on integrated sensors, card readers and touchpads, but strictly from the vendor's own utility with the battery charged.

If Code 10 keeps coming back

Recurring Code 10 usually means the driver store or system files are damaged, and that is what the built-in repair tools are for. Run sfc /scannow in an elevated Terminal first, then DISM /Online /Cleanup-Image /RestoreHealth to repair the component store that SFC draws from; reboot and check the device again. Both commands are safe, take 10–20 minutes together and fix the corruption layer that no driver reinstall can touch.

If the code still returns with a fresh vendor driver on a repaired system, the balance tips toward hardware: test the device on another PC if you can, and check whether the error disappears when you move it to another port or cable. For built-in devices on a laptop, that is the moment to use the warranty or a repair shop rather than fighting Device Manager.

Questions and Answers

Read next

All articles · FAQ