Can't Eject USB Drive – 0x000010EA Error Fix
Getting ERROR_UNABLE_TO_EJECT_MOUNTED_MEDIA? It's usually a process holding onto the drive. We'll walk through quick checks to deeper fixes.
The 30-Second Fix: Close Everything and Try Again
This error means Windows thinks something is still using the drive. Most of the time, it's just a file explorer window or a program you forgot about.
- Close all open folders, files, and programs. That includes things like Excel, Word, or Photoshop that might have saved something to the drive.
- Open Task Manager (Ctrl+Shift+Esc). Look under Processes for anything related to your drive name – sometimes a background process like
SearchIndexer.exeholds onto it. - Right-click and End task on anything suspicious.
- Try ejecting again from the system tray. Right-click the USB icon and select Eject.
Had a client last month whose entire print queue died because of this – he had a PDF on the drive that a print spooler was holding onto. A simple close fixed it.
The 5-Minute Fix: Use Disk Management or Safe Remove
If the quick fix didn't work, the drive has a handle that won't let go. Here's what I do next:
Option 1: Disk Management Eject
- Press Win + X and select Disk Management.
- Find your USB drive. It'll show as Removable and usually has drive letter like D: or E:.
- Right-click the drive's partition (the colored bar area, not the disk number) and select Eject.
This often works because it bypasses the normal safe-remove path. If it says Offline or No Media, you're in a trickier spot – move to the advanced fix.
Option 2: Use a Third-Party Tool
Grab USB Safely Remove or EjectUSB. These tools can force-stop handles. I've used them on stubborn drives that Disk Management couldn't touch. Free trials are available.
The 15+ Minute Fix: Force Eject via Command Line or Registry
When nothing else works, you go deep. This involves using the diskpart utility to offline the drive, or editing the registry to disable write caching.
Method 1: Diskpart Offline
- Open Command Prompt as Administrator. Win + X → Command Prompt (Admin) or Windows Terminal (Admin).
- Type
diskpartand hit Enter. - Type
list disk. Note the disk number of your USB drive. It's usually the last one, and size matches your drive. - Type
select disk X(replace X with your disk number). - Type
offline disk. This forces Windows to release all handles. - Now you can physically unplug the drive. Don't forget to re-enable it later with
online diskin diskpart if you need to use it again.
I've used this on a client's system where a corrupted video file on the drive kept the whole system from ejecting. Offline forced it clean.
Method 2: Registry Edit (Disable Write Caching)
This is for drives that constantly give this error. Write caching can cause the OS to lock the drive.
- Press Win + R, type
regedit, and hit Enter. - Go to:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\STORAGE\ - Find your USB drive's entry. It's listed by vendor and product ID (e.g.,
USB\VID_0781&PID_5551). - Expand it, then expand Device Parameters.
- Look for WriteCacheEnabled. Double-click it and set value to 0.
- Reboot. This disables write caching for that drive only, making eject smoother.
Heads up: Disabling write caching might slow down file transfers slightly. Only do this on drives that need frequent ejections.
Method 3: Check for Corrupted System Files
Sometimes the error is a symptom of a deeper issue. Run SFC and DISM:
- Open Command Prompt as Admin.
- Type
sfc /scannowand wait for it to finish. - Then type
DISM /Online /Cleanup-Image /RestoreHealth. This can take 15-20 minutes. - Reboot and try ejecting.
I had one case where a corrupted Windows file was causing handle locks on every USB drive. After SFC fixed it, the error stopped.
Quick Reference Table
| Solution | Time | What It Does |
|---|---|---|
| Close programs | 30 seconds | Releases handles held by open apps |
| Disk Management Eject | 5 minutes | Bypasses normal safe-remove path |
| Diskpart Offline | 15+ minutes | Forces Windows to drop all locks |
| Registry Write Cache | 15+ minutes | Prevents caching locks for that drive |
| SFC/DISM scan | 20+ minutes | Repairs corrupted system files |
When None of This Works
If you've tried everything and still see error 0x000010EA, the drive might be failing physically. I've seen this on dying USB sticks where the controller chip starts locking up. In that case, copy your data off ASAP and replace the drive. Don't risk data loss just because you can't eject it – sometimes a forced unplug is better than waiting for a fix that never comes.
Was this solution helpful?