0XC0000012

Fix STATUS_WRONG_VOLUME (0xC0000012) Wrong Volume Error

Hardware – Hard Drives Intermediate 👁 6 views 📅 Jul 2, 2026

The drive has the wrong volume label or serial. Usually happens after swapping drives between PCs or restoring backups. Remount or reassign the volume letter.

Quick answer: Run mountvol [drive:] /d then mountvol [drive:] [volume-path] to remap the volume—fixes it 90% of the time.

What is STATUS_WRONG_VOLUME (0xC0000012)?

This error pops up when Windows expects a specific volume (by its unique serial number or label) in a drive slot, but finds something else instead. The volume label or serial in the drive doesn't match what the OS stored in its mount point database.

Real-world trigger: You plug an external USB drive into a different PC, or you swap internal drives between bays. The system remembers the old volume serial, but the new drive has a different one. Boom—0xC0000012.

The culprit is almost always a stale mount point or a mismatched volume GUID. Don't bother reinstalling drivers or running chkdsk—that rarely helps here.

How to Fix It (Step by Step)

Step 1: Open Disk Management

Press Win + X and select Disk Management. Or type diskmgmt.msc in Run.

Step 2: Check the drive letter and volume label

Right-click the problematic drive in the lower pane. Choose Properties. Look at the General tab—does the volume label match what you expect? The serial number (shown in Volume Serial Number) is what Windows actually checks. If the label or serial doesn't match the drive you meant to use, that's the issue.

Step 3: Remove the current mount point

Open Command Prompt as Administrator (right-click Start > Terminal Admin). Type this, replacing E: with your actual drive letter:

mountvol E: /d

This deletes the mount point for that drive letter. Don't worry—it doesn't erase data.

Step 4: Reassign the drive letter

Back in Disk Management, right-click the drive again and choose Change Drive Letter and Paths. Click Add, pick a drive letter, click OK. If the drive still shows the error, pick a different letter than before—sometimes the old letter is cached.

Step 5: Verify

Open File Explorer. The drive should now appear with the correct label and access your files. If not, reboot and check again.

Alternative Fixes If Step 1–5 Fail

Fix A: Use diskpart to clean the volume mount

Run Command Prompt as Admin. Type these commands one by one:

diskpart
list volume
select volume X   (replace X with your volume number)
remove letter=E   (replace E with your drive letter)
exit

Then go back to Disk Management and assign a new letter.

Fix B: Check for hidden partitions or volume shadow copies

Sometimes a hidden recovery partition grabs the same drive letter. In Disk Management, look for any partition without a letter—if it's small and says System Reserved or Recovery, leave it alone. But if it's a data partition, right-click and assign a letter.

Fix C: Reset the mount point database (last resort)

This wipes all custom mount points, so only do this if you're comfortable re-mapping everything:

  1. Open regedit as Admin.
  2. Go to HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices.
  3. Export that key as a backup (File > Export).
  4. Delete all values under that key (but not the key itself).
  5. Reboot. Windows will re-create mount points on next boot.

Caution: This can break USB drive letters and network drives. Use only if you're desperate.

Prevention Tip

When you plug external drives into a different PC, always let Windows assign a new letter. Don't manually set a letter that might conflict. For internal drives, label each drive with a unique volume name in Disk Management—that way you'll spot the mismatch fast.

Also, if you clone a drive, the clone gets the same volume serial. Windows will see two drives with the same ID. Use a tool like Macrorit Partition Expert or MiniTool Partition Wizard to change the serial of the clone—it's a checkbox during clone. Saves you this headache later.

The mountvol command is your best friend here. Learn it, use it. It's way faster than GUI tools for this specific error.

Was this solution helpful?