This Device Cannot Start? Fix Code 10 Errors

If Windows shows “This device cannot start. (Code 10)” in Device Manager, the device driver failed to start, usually because of a corrupt, missing, or incompatible driver, a hardware conflict, or a failing device. The fix is typically to update, roll back, or reinstall the driver, but the exact steps depend on which device is affected and whether the problem started after a Windows update, a new install, or a hardware change.

What Code 10 Actually Means

Device Manager assigns error codes to hardware that fails to start. Code 10 is the generic “cannot start” message—it appears when Windows loads the driver but the driver returns an error during its initialization routine. That error can come from the driver itself, from a conflict with another driver, from a corrupted registry entry, or from the hardware not responding to the driver’s commands.

The same code appears across all device categories: USB controllers, network adapters, graphics cards, audio devices, Bluetooth radios, and even system devices like the ACPI fan. Because the message is generic, the first step is always to identify the specific device showing the error, then work through the causes in order of likelihood.

Why the Driver Fails to Start

Drivers are small programs that translate Windows instructions into hardware commands. When you plug in a device, Windows looks for a matching driver, loads it into memory, and calls its start routine. Code 10 means that start routine returned an error—the driver loaded but could not initialize the hardware.

Common triggers include:

• A Windows update replaced a working driver with an incompatible version.
• A driver update from the manufacturer was interrupted or installed incorrectly.
• Another device is using the same IRQ, I/O port, or memory range (rare on modern systems but still possible with legacy hardware).
• The device’s firmware or hardware is failing, so it does not respond to the driver’s commands.
• Registry entries for the device are corrupted, often after an improper uninstall or a system restore.
• Power management settings are turning off the device to save power, and it fails to wake correctly.

Note that Code 10 is not the same as Code 43 (“Windows has stopped this device because it has reported problems”), which indicates the hardware itself reported a failure. Code 10 is more often a software or configuration issue, though a dying device can also produce it.

How to Fix Code 10 Step by Step

Work through these in order. Most cases resolve at step 2 or 3.

1. Restart the computer. A simple reboot clears transient driver states and re-enumerates all hardware. This fixes a surprising number of Code 10 errors, especially after a sleep/wake cycle.
2. Uninstall and reinstall the driver. Open Device Manager (right-click the Start button, select Device Manager), find the device with the yellow exclamation mark, right-click it, choose “Uninstall device,” and check “Delete the driver software for this device” if that option appears. Then restart. Windows will attempt to reinstall the driver automatically. If it does not, right-click the device and choose “Scan for hardware changes.”
3. Update the driver manually. Right-click the device, select “Update driver,” then “Browse my computer for drivers,” then “Let me pick from a list.” If multiple drivers are listed, try the one marked “Microsoft” or the generic driver, not the manufacturer’s. A generic driver often works when a vendor driver is corrupted.
4. Roll back the driver. If the error started after a driver update, go to the device’s Properties → Driver tab → “Roll Back Driver.” This restores the previous working version. The button is greyed out if no previous driver is saved.
5. Check for Windows updates. Some Code 10 errors are fixed by a cumulative update that includes a new driver or a bug fix. Go to Settings → Windows Update and install all pending updates, then restart.
6. Disable and re-enable the device. In Device Manager, right-click the device, select “Disable device,” wait a few seconds, then right-click again and select “Enable device.” This resets the device’s power state and often clears a transient failure.
7. Change power management settings. Open the device’s Properties → Power Management tab, uncheck “Allow the computer to turn off this device to save power,” and click OK. This is especially relevant for USB devices and network adapters that fail after sleep.
8. Remove hidden devices. Open Device Manager, click View → Show hidden devices, then expand the relevant category and uninstall any greyed-out entries. These are ghost devices left behind by old hardware or failed uninstalls. Restart afterward.

If none of these work, the device itself may be failing. Test it on another computer if possible. If it fails there too, replace the hardware.

Common Problem Areas and Their Specific Fixes

USB devices (flash drives, external drives, hubs): Try a different USB port, especially a port directly on the motherboard rather than a front-panel port or hub. In Device Manager, expand “Universal Serial Bus controllers,” uninstall every entry under “USB Root Hub” and “Host Controller,” then restart. Windows will rebuild the USB stack. Also check for a “Selective Suspend” setting in Power Options that may be cutting power to the port.

Network adapters (Wi-Fi or Ethernet): Run the network troubleshooter (Settings → System → Troubleshoot → Other troubleshooters → Network Adapter). If that fails, uninstall the adapter from Device Manager and restart. For Wi-Fi, also check that the adapter is not disabled by a physical switch or a function key (often F2, F12, or a dedicated key with a radio tower icon).

Graphics cards: If the display adapter shows Code 10, boot into Safe Mode (hold Shift while clicking Restart, then Troubleshoot → Advanced options → Startup Settings → Restart → press 4). In Safe Mode, uninstall the graphics driver, then restart and install the latest driver from the manufacturer’s website. Do not rely on Windows Update for GPU drivers.

Audio devices: Right-click the speaker icon in the system tray, select “Sound settings,” then “More sound settings.” On the Playback tab, right-click the default device and choose “Properties.” If the device shows “This device cannot start (Code 10),” uninstall it from Device Manager and restart. For Realtek audio, also check that the “Realtek Audio” entry in Device Manager is not disabled.

Bluetooth: Bluetooth adapters often show Code 10 after a Windows update. In Device Manager, expand “Bluetooth,” uninstall the adapter, then restart. If the problem persists, go to the manufacturer’s support site and download the latest Bluetooth driver—do not use the generic Microsoft driver unless it is the only option.

When to Use the Registry Fix

Some Code 10 errors are caused by a corrupted registry entry under the device’s hardware key. This is more common with older devices or after a failed driver uninstall. The fix involves deleting the problem value, but it is risky if done incorrectly.

To try it, open Device Manager, double-click the failing device, go to the Details tab, and select “Device instance path” from the dropdown. Copy that path (e.g., PCI\VEN_8086&DEV_153B&SUBSYS_00008086&REV_04\4&2e6b0c7b&0&00E5). Then open Registry Editor (type regedit in Start), navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\ and paste the path at the end of the address bar. Under that key, look for a value named ConfigFlags or DeviceProblemCode. If DeviceProblemCode is set to 0x0000000a (10), you can try deleting that value, then restart. Back up the key first by right-clicking it and choosing Export. If you are not comfortable editing the registry, skip this step—it rarely fixes the problem when the driver itself is at fault.

How to Read the Error Details

Device Manager gives you more information than just the code. Open the device’s Properties, go to the Details tab, and select “Device status” from the dropdown. The full message often includes a second line like “The device cannot start because it is not properly configured” or “The device cannot find enough free resources.” That extra line points to the cause:

• “Not properly configured” → driver or registry issue; try uninstall/reinstall.
• “Cannot find enough free resources” → resource conflict; try disabling other devices or moving the device to another slot/port.
• “The driver returned an error” → driver bug or hardware failure; update the driver or test the hardware elsewhere.
• “The device is not working properly because Windows cannot load the drivers” → corrupt driver files; reinstall the driver.

Also check the “Events” tab in Properties. It lists driver installation and removal events with timestamps. If the Code 10 appeared immediately after an event labeled “Device Configured,” the driver that was just installed is the culprit.

Frequently Asked Questions

Will a system restore fix Code 10? Yes, if the error started after a recent change—a driver update, a Windows update, or a software install. System Restore reverts the registry and system files to an earlier point, which can undo the change that broke the driver. It will not fix a hardware failure or a driver that was already corrupt before the restore point. Try it if the error appeared in the last few days and you have a restore point from before that time.

Is Code 10 a sign my device is dead? Not necessarily. Most Code 10 errors are software-related and fixable with a driver reinstall. However, if the error persists after trying all the steps above, and the device does not work on another computer, the hardware is likely failing. Devices with moving parts (hard drives, fans) and older electronics are more prone to this.

Why does my USB device work on another computer but not mine? That points to a driver or USB controller issue on your computer, not the device. Try the USB-specific steps above: uninstall all USB controllers, restart, and check power management settings. Also try a different USB port, ideally a USB 2.0 port if your device is older.

Can I just ignore Code 10 if the device works anyway? If the device is functioning, the error may be a false positive from a secondary function (like a fingerprint reader on a laptop that also has a camera). Some devices have multiple functions, and only one fails. If the main function works, you can leave it, but the failing function will not work until fixed. For example, a network adapter that shows Code 10 but still connects to Wi-Fi is rare but possible—check if the Bluetooth function of the same adapter is the one failing.

Does uninstalling the driver delete my data? No. Uninstalling a driver removes software, not your files. For storage devices, uninstalling the driver does not delete data on the drive. However, if you are dealing with a USB flash drive or external drive that shows Code 10, do not format it—formatting erases data. Try the driver fixes first.

What if the device is not listed in Device Manager at all? If the device does not appear even with “Show hidden devices” enabled, Windows is not detecting it. That is a different problem—often a hardware connection issue, a disabled device in BIOS/UEFI, or a completely dead device. Check physical connections, try another port, and check BIOS settings for built-in devices like Wi-Fi or Bluetooth.

Related

• How Ransomware Spreads Through Business Networks
• Office Repair Genius: Is It Worth Buying?
• How to Run Ollama on Multiple Computers