STATUS_DEVICE_REMOVED (0XC00002B6) – USB drive yanked mid-read

You're copying files off a USB stick, the progress bar is crawling, and you look away for a second. Then bang—a dialog pops up saying "STATUS_DEVICE_REMOVED (0XC00002B6)". The drive is still plugged in, but Windows has declared it dead. I see this most often with cheap USB flash drives, external hard disks that bump against a desk leg, or when someone yanks a cable without clicking "Safely Remove Hardware". Had a client last month whose entire backup drive got this error after their cat knocked it off the desk. The drive worked fine after a reboot, but the file copy? Gone.

Why does this happen?

Windows uses a thing called a "plug-and-play" driver stack. When you connect a USB device, the system assigns it a device object—think of it like a ticket number. If that device gets physically disconnected (even for a split second), the ticket gets canceled. The error 0XC00002B6 is Windows saying "I can't find the ticket anymore, so I'm giving up." It's not a corruption issue—usually. It's a connection glitch.

Sometimes it's a bad cable. Sometimes it's a loose port. Sometimes it's the Windows power management deciding to cut power to a USB port to "save energy". That last one is infuriating because you didn't do anything wrong.

The fix: step by step

1. Replug the device – Unplug it, wait 10 seconds, plug it back in. Try a different USB port (preferably on the back of the PC if you're on a desktop). If the error disappears, you're golden. If not, move to step 2.
2. Check power management – Open Device Manager (right-click Start > Device Manager). Expand "Universal Serial Bus controllers". Right-click each "USB Root Hub" and "Generic USB Hub", go to Power Management tab, and uncheck "Allow the computer to turn off this device to save power". Do this for every entry. I've seen Windows 10 and 11 randomly kill USB ports during file transfers. Disabling this stops it.
3. Run CHKDSK if the drive shows up but won't read – Open Command Prompt as Admin (search cmd, right-click, Run as administrator). Type chkdsk E: /f (replace E: with your drive letter). This scans and fixes file system errors that might have happened when the connection dropped. Most times it's clean, but sometimes the sudden disconnect corrupts the index.
4. Use a different cable – If you're on an external hard disk, swap the USB cable. USB cables fail internally without visible damage. I keep a spare USB 3.0 cable in my bag for exactly this reason.
5. Update or reinstall USB drivers – In Device Manager, right-click each "USB Root Hub" and select "Update driver" > "Browse my computer" > "Let me pick" > select a compatible driver (usually the same version). Or just uninstall the device (right-click > Uninstall device), then restart. Windows will reinstall it fresh.

If it still fails

Try the drive on another computer. If it works there, your USB controller might be failing. If it still gives 0XC00002B6 on other PCs, the drive's logic board is dying. For USB flash drives, that's often a lost cause—clone it with something like ddrescue if you need the data. For external hard disks, you can sometimes swap the controller board if you're handy with a screwdriver, but it's usually cheaper to replace the drive.

One more thing: if you see this error regularly with a specific USB port, clean the port with compressed air. Dust and lint can cause intermittent disconnects. I've fixed three "dead" USB ports just by blowing them out.

Real talk: this error is almost never a Windows problem. It's a physical connection problem. Fix the connection, and the error goes away.