Fix ERROR_WRONG_DISK (0X00000022) on Windows 10/11

Quick Answer

Open Command Prompt as admin and run mountvol /e then mountvol [drive letter] /d for the stuck drive. That unmounts the ghosted disk and usually kills the error instantly.

What Actually Causes This Error

I know this error is infuriating — you just plugged in a USB drive or put a DVD in the tray, and Windows screams “Wrong disk is in the drive.” The error code 0X00000022 means the system tried to access a drive letter that used to point to one disk, but now there's a different one there, or nothing at all. This tripped me up the first time too.

It's common when you hot-swap USB drives or eject an optical disc without using the “Safely Remove Hardware” option. Windows keeps the old drive letter mapping in its registry, and when a new disk shows up at the same port, it gets confused. You'll see it most often with external hard drives, SD card readers, or even internal optical drives after a burn failure. On Windows 10 version 22H2 and Windows 11 23H2, I've also seen it appear after a boot failure where the drive letter cache gets corrupted.

The fix is straightforward: clear the stale drive letter mapping and let Windows reassign it fresh. Don't bother reformatting or running CHKDSK — that's overkill and won't solve the root cause.

Step-by-Step Fix (Main Method)

1. Identify the stuck drive letter. Open File Explorer and check which drive shows the error. For example, if your DVD drive is listed as F: but trying to access it gives the error, that's your target.
2. Open Command Prompt as admin. Hit the Start button, type cmd, right-click Command Prompt, and pick “Run as administrator.” Accept the UAC prompt.
3. List all mounted volumes. Run mountvol by itself. You'll see a list of all drive letters and their GUID paths. Find the line matching your stuck drive letter. It'll look something like \??\Volume{abcdef12-3456-7890-abcd-ef1234567890}\ mounted at, say, F:\.
4. Clear that drive letter mapping. Run mountvol [drive letter]: /d. For drive F, that's mountvol F: /d. This deletes the stale mount point.
5. Reassign the drive letter (optional but recommended). Open Disk Management (right-click Start → Disk Management), find the physical disk (like your USB drive or optical drive), right-click its volume, choose “Change Drive Letter and Paths,” then assign a new letter — or assign the same one if you prefer. This forces Windows to treat it as a fresh device.
6. Test the drive. Double-check in File Explorer that the error is gone. If it still shows, reboot — the registry changes need a restart sometimes.

Alternative Fixes (If Step 1–6 Doesn't Work)

Option A: Use Diskpart

If mountvol fails (say the drive letter isn't listed), use Diskpart instead.

diskpart
list volume
select volume X (replace X with the number of the stuck drive)
remove letter=F (or whatever letter is stuck)
exit

This is more aggressive — it removes the letter without confirmation. Then go to Disk Management and assign a new letter.

Option B: Delete the Registry Key (Advanced)

For persistent cases, especially after a system crash, mount points get buried in HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices. Back up this key first (Export it). Then delete the value named \DosDevices\F: (adjust for your drive). Restart. This is nuclear — don't do it unless the other methods fail.

Option C: Check Device Manager for Conflicting Drivers

Rarely, a corrupted driver for your USB controller or optical drive can cause this. Open Device Manager, expand “Universal Serial Bus controllers,” right-click each “Generic USB Hub” and “USB Root Hub,” pick “Uninstall device,” then restart. Windows reinstalls them fresh. I've only seen this fix the error on Windows 11 23H2 with certain Realtek card readers.

Prevention Tips

You won't see this error again if you do one thing: always use “Safely Remove Hardware” before unplugging a USB drive. I know it's annoying, but it tells Windows to flush the drive letter cache. For optical drives, press the eject button in File Explorer instead of the physical button on the drive — that gives Windows a heads-up. Also, avoid swapping USB drives between different machines without first running mountvol /e on the original PC to clear orphaned mount points.

One more thing: if you're running an older BIOS-based system (pre-UEFI), the drive letter assignments can get wonky after a boot from a recovery USB. In that case, just reboot twice — the second boot often clears the ghosted mapping.

That's it. You're done. The error should be gone, and your drive should show up normally. If it doesn't, let me know the exact make and model of your drive (e.g., Seagate Backup Plus 2TB or ASUS 24x DVD writer) — that helps narrow down driver-specific issues.