How to fix "This device cannot start" (Code 10)
DeviceInBox editorial team · Last updated September 17, 2026
"This device cannot start. (Code 10)" means Windows found a driver for the device and loaded it, but the driver couldn't get the device running. That makes it different from missing-driver errors: Windows knows what the device is, and something goes wrong while it starts. Typical reasons are an incompatible or corrupted driver, a device that doesn't respond, or another driver getting in the way.
Look at the device details first
Open the device's Properties in Device Manager and note a few things:
- The full status text on the General tab. Sometimes Windows adds a reason, such as "{Operation Failed} The requested operation was unsuccessful".
- The driver provider, date and version on the Driver tab. A driver that predates your Windows version by many years is a strong hint.
- The hardware ID on the Details tab. You will need it to find the right driver (how to find it).
- The Events tab, which shows when the problem began. That helps you connect it to a specific update.
Restart and reconnect
For an external device, unplug it, restart Windows and connect it to another port. For an internal one, do a full shutdown (hold Shift while clicking Shut down), unplug the power for 30 seconds and start again.
Roll back or reinstall the driver
- If the error appeared after an update, open Properties, go to the Driver tab and click Roll Back Driver.
- Otherwise, right-click the device, choose Uninstall device, tick "Attempt to remove the driver for this device" (Windows 10: "Delete the driver software for this device"), confirm and restart.
- After the restart, check whether the driver Windows installed by itself works before you install anything else.
Get the driver that matches the hardware ID
Very often Code 10 comes from a driver written for a similar but different chip, or for an older version of Windows. Search by hardware ID and choose a driver whose supported ID list includes yours and which fits your Windows version and architecture. Almost every current PC runs 64-bit Windows.
Drivers made only for Windows XP or Vista rarely work on Windows 10 or 11. On Windows 11, also open Windows Security, go to Device security and then Core isolation. If Memory integrity lists incompatible drivers, the device needs a newer driver; turning the protection off is not a good fix.
After a Windows upgrade, Code 10 shows up most often on USB-to-serial adapters, Wi-Fi and network adapters, and audio devices:
| Hardware ID | Device | Drivers |
|---|---|---|
| USB\VID_067B&PID_2303 | PL2303 Serial Port | 9 |
| USB\VID_1A86&PID_7523 | HL-340 USB-Serial adapter | 7 |
| USB\VID_0BDA&PID_8179 | RTL8188EUS 802.11n Wireless Network Adapter | 12 |
| PCI\VEN_10EC&DEV_8168 | RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller | 33 |
| PCI\VEN_8086&DEV_24FD | Dual Band Wireless-AC 8265 | 15 |
| PCI\VEN_168C&DEV_0036 | QCA9565 / AR9565 Wireless Network Adapter | 17 |
Check the optional driver updates
In Settings, open Windows Update, then Advanced options, then Optional updates. The Driver updates section lists drivers from hardware makers that Windows doesn't install automatically. Install the one for your device and restart.
Remove leftover filter drivers (advanced)
Some programs, such as CD burning tools, virtual drive software, older antivirus products and audio enhancers, install filter drivers that attach to a whole class of devices. If such a program wasn't removed cleanly, every device in that class can fail with Code 10.
- Uninstall utilities you recently added that relate to the failing device, then restart.
- If that doesn't help and you are comfortable with the registry, create a restore point first. In
regedit, go toHKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Classand find the subkey whose Class value matches your device type. Export it as a backup, and delete the UpperFilters and LowerFilters values only if they point to software you no longer have. Restart afterwards.
Rule out a hardware fault
Try the device in another port, slot or computer. If it fails with Code 10 everywhere, or the BIOS doesn't detect it either, the device is most likely defective.
More guides
- Find your hardware ID
- Unknown USB Device (Device Descriptor Request Failed)
- Code 43: device reported problems
- SM Bus Controller driver
- PCI Simple Communications Controller
- PCI Data Acquisition and Signal Processing Controller
- Base System Device driver
- PCI Device driver missing
- Ethernet Controller driver missing
- Network Controller driver missing
- Unknown device in Device Manager
- Code 28: drivers are not installed
- Code 31: Windows cannot load the drivers
- Code 39: driver corrupted or missing
- Code 52: digital signature problem
- USB device not recognized
- Install a driver from an INF file
- Wi-Fi gone after a Windows update
- Bluetooth missing from Windows
- SD card reader not working