Code 10 is one of the most misunderstood errors in Windows 11. It simply means the device failed to start — Windows found the hardware, loaded a driver for it, and then the driver could not bring the device into a working state. The fix is rarely the same twice, because a USB controller, a Bluetooth radio, a network adapter, and a storage controller all fail to start for different reasons. This guide walks you through each branch in the order a help desk would actually work it.
Before You Change Anything
Create a restore point first. Search "Create a restore point" in the Start menu, select your system drive, and click Create. This is your undo button if a registry or driver change goes wrong.
Back up anything irreplaceable before touching storage controllers or BIOS settings. A bad storage driver change can leave a machine unbootable.
Note the exact device name and error from Device Manager before you change anything — you will need it to confirm the fix worked.
Do not download "driver updater" utilities. They bundle adware and install the wrong drivers. Use Windows Update, the manufacturer's site, or Windows' own tools.
Work one change at a time. Change one thing, reboot, and re-check. Stacking changes makes it impossible to know what fixed it.
If this is a work machine under IT management, check with your admin before editing the registry or BIOS — some of these steps may be locked by policy.
Having this problem on your own PC?
Describe what's happening and get a real AI diagnosis in seconds — no account needed.
Confirm You Have This Problem
Open Device Manager (right-click Start → Device Manager, or run devmgmt.msc). Look for a device with a yellow warning triangle. Double-click it and read the Device status box under the General tab. You have Code 10 if it reads:
> This device cannot start. (Code 10)
> {Operation Failed} The requested operation was unsuccessful.
You can also confirm it from a command line. Open Terminal (Admin) and run:
pnputil /enum-devices /problemThis lists every device Windows currently flags with a problem, along with its instance ID and problem code. If your device appears with Problem Code: 10, you are in the right place. Note the instance ID — it is the fastest way to identify the exact hardware later.
Possible Causes
| Evidence Observed | Likely Cause | Next Check |
|---|---|---|
| Error appeared right after a Windows or driver update | New driver is incompatible or corrupt | Roll back the driver (Step 1) |
| Device worked, then failed after sleep or a reboot | Driver failed to reinitialize; stale power state | Disable/re-enable device, then power cycle (Step 2) |
| USB device fails only on certain ports | Port or hub controller issue, not the device | Test on a rear/direct port (Step 3) |
| Bluetooth or Wi-Fi fails after a Windows feature update | Radio driver/firmware mismatch | Reinstall the OEM driver (Step 4) |
| Storage controller fails after a chipset update | Wrong or generic controller driver | Check driver provider and version (Step 5) |
| Device fails on every port and every PC | Hardware fault in the device itself | Test on a second machine (Step 6) |
| Error returns immediately after every fix | Corrupted registry entries for the device | Clean reinstall via registry (Step 7) |
Step-by-Step Diagnostic
Work these in order. The first steps are reversible and low-risk; the later ones touch drivers, the registry, and hardware.
Step 1 — Roll back the driver (lowest risk)
If the error appeared after an update, this is almost always the fix. In Device Manager, right-click the failing device → Properties → Driver tab → Roll Back Driver. If the button is greyed out, no previous driver is stored, so skip to Step 2. Reboot and re-check the device status.
Step 2 — Disable, re-enable, and power cycle
Right-click the device → Disable device, wait ten seconds, then Enable device. If that does not clear it, shut down completely (not restart), unplug the power for 30 seconds, and boot again. This clears the stale power state that causes many Code 10 errors after sleep.
Step 3 — Isolate the port or slot
For USB and Bluetooth, move the device to a different port — ideally a rear port directly on the motherboard rather than a front-panel or hub port. If it starts working, the problem is the port or hub, not the device. For internal cards, reseat them in a different slot if one is available.
Still unsure what's causing the issue? Run a free AI diagnosis at DiagnoseMyPc.com — no download required, 5 free analyses per month.
Step 4 — Reinstall the correct OEM driver
Windows Update often installs a generic driver that a device refuses to start with. Go to the manufacturer's support page (Dell, HP, Lenovo, Intel, Realtek, etc.), download the driver for your exact model and Windows 11 build, and install it. In Device Manager you can also right-click → Uninstall device, tick Delete the driver software for this device, reboot, and let Windows reinstall cleanly.
Step 5 — Check the driver provider and version
In Device Manager → Properties → Driver tab, look at the Driver Provider and Driver Version. A generic "Microsoft" provider on a storage or network controller is a red flag. Compare the version against the OEM's latest release. For storage controllers, a wrong driver here can cause boot failures, so create a restore point before changing it.
Step 6 — Test the hardware on another machine
If the device fails on every port and every PC, the fault is in the hardware, not Windows. Test a USB device on a second computer. For internal cards, this is harder, but a known-good spare card is the definitive test. If it fails elsewhere, replace it — no software fix will help.
Step 7 — Clean the device out of the registry (highest risk)
Only do this after a restore point. Corrupted registry entries under the device's class key can make Code 10 return after every fix. Open Registry Editor (regedit) as admin, back up the key you are about to touch (File → Export), then navigate to:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\EnumFind the device by its instance ID (from pnputil earlier), export that key as a backup, then delete it. Reboot — Windows will re-detect the device and rebuild its entries. This is the step most likely to fix a stubborn, recurring Code 10, and also the one most likely to cause damage if you delete the wrong key.
How to Know It's Fixed
The yellow warning triangle is gone from Device Manager.
The Device status box reads "This device is working properly."
pnputil /enum-devices /problem no longer lists the device.
The device actually functions — the USB drive mounts, Bluetooth pairs, Wi-Fi connects, or the storage controller reports healthy in Disk Management.
The fix survives a full shutdown and a reboot, not just a re-enable.
When to Stop and Get Help
Stop and escalate if the device fails on a second known-good machine (that is a hardware fault), if a storage controller change leaves the PC unable to boot, or if the error returns after a clean registry reinstall. On a managed work machine, hand it to your IT team rather than editing the registry or BIOS yourself — policy and warranty may both be at stake. And if you have spent more than an hour cycling through these steps without a clear result, a structured diagnosis will save you time.
Dealing with this one-time? The $4.99 Fix Pass gives you 7 days of full Pro access — no subscription needed.
Found this helpful?
Share it with someone who could use it.
DiagnoseMyPC Team
Expert PC diagnostics and troubleshooting guides to help you keep your Windows system running smoothly.
Get the free Windows Troubleshooting Checklist
Subscribe and instantly download our 50-point Windows troubleshooting checklist — plus practical fixes, performance tips, and security alerts from the DiagnoseMyPC team.
No spam. Unsubscribe anytime.
Frequently Asked Questions
How do I find out exactly what's causing my PC problem?
The fastest way is to let an AI analyzer read your actual system data instead of guessing. You can paste an error message, upload a screenshot, or run a quick diagnostic and get the specific cause ranked by severity. Try a free AI diagnosis at diagnosemypc.com — no account needed to get started.
Is it safe to run fix commands on my own PC?
Yes, as long as you understand what each command does. PC Diagnostic Analyzer always shows you the exact fix script first so you stay in full control of what runs on your computer — nothing is executed automatically without your review.
Do I need to reinstall Windows to fix this?
Usually not. Most performance, crash, driver, and startup problems can be fixed with targeted steps once you know the real cause. A full reinstall should be a last resort — start with a proper diagnosis before wiping anything.
When should I take my PC to a repair shop instead?
If a diagnosis points to failing hardware (a dying drive, bad RAM, or overheating components) and you're not comfortable opening the case, a shop is worth it. For software, driver, and configuration issues, you can almost always fix it yourself with step-by-step guidance.
