0XC0000086

STATUS_INVALID_VOLUME_LABEL (0XC0000086) – Fixes for a Bad Volume Label

This error means you tried to mount or access a drive with a label that Windows can't parse. Usually happens after a rename or partition tool botches the label. Here's how to fix it fast.

What triggers this error

The STATUS_INVALID_VOLUME_LABEL error (0XC0000086) pops up when you try to access a drive—usually an external USB drive, an internal secondary disk, or a flash drive—and Windows throws a fit about the volume label. The exact moment it hits is when you open File Explorer, double-click the drive letter, and get a popup saying something like "E:\ is not accessible. An invalid volume label has been specified." You can't browse the drive, but it still shows up in Disk Management with a weird name like "" (empty) or garbage characters.

Root cause

What's actually happening here is that the volume label stored in the NTFS (or FAT32/exFAT) metadata is corrupted or contains a character Windows can't handle. The label isn't just a name—it's stored in the volume boot record and in the root directory index. If a partition tool (like a Linux fdisk, a third-party partition manager, or even a bad script) wrote a label with a non-ASCII byte sequence, or if a power loss interrupted a rename operation, the label becomes malformed. The kernel, when trying to mount the volume, reads this label and fails the validity check—hence the 0xC0000086 status code.

Label corruption is more common on drives that have been used across multiple operating systems (dual boot with Linux, or a drive formatted on a NAS). Windows is strict: labels can only contain letters, numbers, spaces, and underscores—nothing like colons, tabs, or unicode control characters. Surviving characters that look normal to you might be a different encoding underneath.

The fix

You don't need to reformat—the data is still there. The label is just metadata. Two commands will fix it.

Step 1: Identify the problem drive

Open a command prompt as Administrator. Run:

wmic logicaldisk where drivetype=3 get caption, volumename

Look for the drive that shows a blank VolumeName or garbage characters. Note its drive letter—say E:.

Step 2: Remove the bad label

This is the key command that wipes the label entirely. Windows will then assign a default label (like "Local Disk") or you'll set one yourself.

label E: ""

The empty quotes tell Windows to delete the label. You might get an error like "The parameter is incorrect" if the existing label is really messed up—don't worry, move to step 3.

Step 3: Force a label reset via diskpart

If the label command fails, use diskpart:

diskpart
list volume
select volume X   (replace X with the volume number of drive E:)
attributes volume clear readonly   (in case it's read-only)
set id=07 override   (for NTFS; forces a refresh of volume metadata)
exit

The reason step 3 works is that set id=07 override rewrites the partition type byte and triggers a metadata rebuild. After this, the label is gone. Back at the command prompt, run label E: MyDrive to set a clean label.

Step 4: Verify

Open File Explorer and try accessing the drive. It should open normally now. If it still fails, run a quick chkdsk:

chkdsk E: /f

This will fix any file system corruption that might have caused the label issue in the first place.

What to check if it still fails

If after all that the error persists, the volume label isn't the only problem. Could be deeper corruption in the $Volume file or the VBR. Boot from a Windows PE USB, run chkdsk E: /r (takes hours on large drives). If that fails, the partition table might be hosed—use TestDisk or bootrec /fixboot to rebuild the boot sector. Worst case, you're looking at data recovery tools like Recuva or DMDE. But 90% of the time, the label wipe is all you need.

Related Errors in Hardware – Hard Drives
Drive Shows Wrong Capacity After Clone? Fix It Here Storage Pool Capacity Exhausted: Free Up Space Now Google sends you in circles? Fix the search redirect loop 0X00000462 Fix ERROR_FLOPPY_ID_MARK_NOT_FOUND 0X00000462 in 3 Steps

Was this solution helpful?

EP
Erropedia Team
Tech Support Editors
The Erropedia editorial team researches and documents real-world tech errors from across Windows, Linux, macOS, networking, databases, cloud platforms, and more. Every solution is reviewed for accuracy and updated as software and systems evolve.