You plug in a drive, a webcam, or a printer, and Windows throws 0x000010DF — "The device is not ready for use." It's infuriating because the device is clearly plugged in. I've seen this on Windows 10 22H2 and Windows 11 23H2 with external SSDs and USB hubs. The root cause is almost never the device itself — it's Windows losing track of the hardware stack.
The real fix (works 90% of the time)
Skip all the driver downloads and chkdsk nonsense. Here's what you do:
- Open Device Manager (Win + X → Device Manager).
- Find the device showing the error — it'll have a yellow exclamation mark or be under "Unknown devices" or "Universal Serial Bus controllers."
- Right-click the device and select Uninstall device. Do not check "Delete the driver software for this device" — you want Windows to keep the driver, just reload the hardware stack.
- With the device still physically connected, go to Device Manager's Action menu and click Scan for hardware changes.
- Wait 10-15 seconds. Windows will re-enumerate the USB bus, redetect the device, and reinstall the driver. The error should disappear.
If it doesn't work on the first try, repeat steps 3-4 two more times. Sometimes the USB hub needs a full power cycle.
Why this fix works
What's actually happening here is that Windows's Plug and Play manager (PNP) cached a stale device state. The driver is loaded, but the hardware descriptor got corrupted or the device entered a D3 (sleep) power state that the bus driver can't wake. By uninstalling without deleting the driver, you force PNP to re-query the device's descriptor and renegotiate the power state. The reason step 3 works better than just restarting is you don't lose the driver settings — if you had a custom USB transfer size or a specific driver version for a legacy device, it stays intact.
I've seen this fix work on a Logitech C920 webcam that stopped working after Windows Update, a Sandisk Extreme SSD that worked on one PC but not another, and a Wacom tablet that refused to wake from sleep. In every case, the hardware was fine — it was Windows's USB stack that needed a reset.
When that doesn't work: less common causes
USB selective suspend is killing your device
Windows 10 and 11 have a feature called USB selective suspend that puts idle USB ports into a low-power state to save battery. Problem is, some devices — especially external drives and older printers — don't respond well to this. When they wake up, the driver thinks they're still sleeping and throws 0x10DF.
To disable it:
- Open Control Panel → Power Options → Change plan settings → Change advanced power settings.
- Find USB settings → USB selective suspend setting → set to Disabled.
- Click Apply, reboot.
This is especially common on laptops with USB-C hubs. If you're running a Dell XPS or Lenovo ThinkPad, this is often the culprit.
Driver mismatch after Windows Update
Sometimes Windows Update pushes a generic USB driver that doesn't match the hardware's required driver version. This happened a lot on Windows 11 22H2 with Realtek USB audio devices and some older HP printers. The fix is to force the correct driver:
- In Device Manager, right-click the device → Update driver → Browse my computer for drivers → Let me pick from a list.
- Select USB Mass Storage Device (or the manufacturer-specific driver if listed), not the generic Microsoft USB driver.
- If you see two entries for the same device, pick the one with a manufacturer name (e.g., "SanDisk" instead of "Microsoft").
I've seen this fail because people pick the wrong driver. Match the hardware ID (in Details → Hardware IDs) against the driver's INF file if you're unsure.
Faulty USB port or cable — but you can test without replacing
Before you buy a new cable, check if the error appears on all ports or just one. If it's specific to a front-panel USB port on a desktop, the port's voltage regulator might be failing. Quick test: plug into a rear port directly on the motherboard. If it works there, the front panel wiring is the issue (happens on cheap cases). If no port works, it's almost certainly a driver or power management problem, not hardware.
Prevention: keep the USB stack clean
Most people get this error once or twice a year and it fixes itself after a reboot. But if you're seeing it repeatedly, check these:
- Don't yank USB devices without using "Safely Remove Hardware" — doing so leaves the device in a pending I/O state that can corrupt the stack.
- Update chipset drivers from your motherboard manufacturer, not from Windows Update. Intel and AMD both publish USB driver updates that fix enumeration bugs. On a Ryzen system, I've seen this error disappear after installing the latest AMD chipset driver (v6.02.28.112 as of October 2024).
- Disable fast startup in Power Options if the error happens after wake-from-sleep. Fast startup hibernates the kernel, and on some hardware, the USB host controller can't resume properly. Go to Control Panel → Power Options → Choose what the power buttons do → Change settings that are currently unavailable → uncheck Turn on fast startup.
One more thing: if you're using a USB hub, make sure it's powered (has its own mains adapter). Passive hubs share power across ports, and a device drawing too much current can kick the hub into a fault state that causes 0x10DF on all ports. That's a hardware-level problem no driver can fix.