0X000002E7

Fix ERROR_VOLUME_MOUNTED 0X000002E7 Fast

Hardware – Hard Drives Intermediate 👁 7 views 📅 Jun 24, 2026

ERROR_VOLUME_MOUNTED means Windows already sees that drive. The fix is to unmount it properly or reassign the drive letter. Real fix below.

Ran into this error on a client's Windows 11 machine last week. External USB drive showed in Disk Management but wouldn't let you access it. Just threw ERROR_VOLUME_MOUNTED (0X000002E7). Annoying. But the fix is simple.

The Quick Fix

Open Command Prompt as Administrator. Type this:

diskpart
list volume
select volume X  (replace X with the volume number that has the error)
remove letter=E  (or whatever letter is assigned)

Then close diskpart with exit. Now go to Disk Management and assign a new drive letter. Right-click the volume, Change Drive Letter and Paths, Add, pick a letter, OK. 

That's it. The volume is no longer mounted under the old letter. Windows sees it fresh. If the error was stopping you from formatting or using the drive, this clears it.

Why This Works

ERROR_VOLUME_MOUNTED means the NTFS journal thinks the volume is already mounted somewhere, but the mount point is stale or corrupt. Windows won't let you touch it. Removing the drive letter via diskpart deletes the mount point cleanly. Then you reassign a new letter, and the volume mounts normally.

I've seen this happen when you yank an external drive without safely removing it. Or after a bad USB hub disconnection. The file system records the mount but the actual connection is lost. Next time you plug it in, Windows sees the volume but can't reconcile the old mount info.

Real Scenario

Had a client whose backup drive died after a power outage. The drive was fine but every time they plugged it in, they got 0X000002E7. Tried chkdsk — no luck. Removed the drive letter and reassigned — worked instantly. Backup restored.

Less Common Variations

Sometimes the error pops up on internal drives, especially after cloning a system drive. The cloned volume might have the same GUID as the original, causing a mount conflict. Here's what I do:

  • Check for duplicate volume GUIDs: Open regedit, go to
    HKLM\SYSTEM\MountedDevices
    . Look for entries with the same GUID. Delete one (make a backup first).
  • Use diskpart to clean the volume: If the drive is empty and you don't need data, you can run clean on it, then create a new partition. This nukes the mount info.
  • Check if the drive is hidden: Sometimes the volume is mounted but has no drive letter. Use Disk Management to assign a letter.

Another variation: the error might show in backup software like Acronis or Macrium when trying to access a volume that's already mounted by Windows. In that case, close the backup software, unmount the drive with diskpart, then reopen the software.

Prevention

Don't yank USB drives without safely removing them. Use the 'Safely Remove Hardware' icon or run eject from the taskbar. Power outages? Get a UPS for sensitive drives. And if you clone drives, always use a tool that assigns new GUIDs, like Clonezilla with the -g option.

One more tip: If you regularly swap external drives, assign them static drive letters via Disk Management. That way Windows doesn't get confused when you plug them back in.

That's it. Five minutes, no headache. ERROR_VOLUME_MOUNTED is just a stubborn mount point. Kill it, reassign, move on.

Was this solution helpful?