0X800300FC

STG_E_INVALIDNAME (0X800300FC): Fix Invalid Drive Name Error

Hardware – Hard Drives Intermediate 👁 12 views 📅 May 28, 2026

This Windows error means the drive name or path is corrupted or unsupported. Quick fix: rename the drive letter or volume label in Disk Management.

Quick Answer

Open Disk Management, right-click the drive, choose Change Drive Letter and Paths, assign a new letter, then reboot. If that fails, run chkdsk /f X: (replace X with the drive letter) from an admin command prompt to fix underlying file system corruption.

Why This Error Happens

STG_E_INVALIDNAME (0X800300FC) pops up when you try to access a drive—usually an external USB or internal partition—and Windows can't resolve its name or path. I've seen this most often after a bad eject, a power failure during a write, or a third-party partition tool messing up the volume label. The error text says "The name %1 is not valid," which is Microsoft's way of saying the volume label, drive letter, or mount point is corrupted or has illegal characters (like trailing spaces or special symbols).

This tripped me up the first time too—I thought the drive was dead. But it's almost always a soft logic issue in the file system table, not hardware failure.

Step-by-Step Fix

Step 1: Rename the Drive Letter

  1. Press Win + X and select Disk Management.
  2. Find the problematic drive (it may show as RAW or have a weird label).
  3. Right-click the partition and choose Change Drive Letter and Paths.
  4. Click Change, pick a new letter (say from E: to F:), then hit OK. Confirm the warning about programs using the old letter.
  5. Reboot your PC. The error typically vanishes.

Step 2: Fix the Volume Label

If the drive letter is fine but the label is garbage (like a rectangle character or blank), fix it in Disk Management or command line:

label X: NewName

Replace X with the drive letter and NewName with something simple, like Backup or Data. No spaces or special characters—keep it alphanumeric.

Step 3: Run Chkdsk

When renaming doesn't work, the file system itself is corrupted. Open Command Prompt as administrator (Win + XTerminal (Admin)) and run:

chkdsk /f X:

Replace X with the trouble drive's letter. If it's your boot drive, it will schedule a scan on next reboot. This fixes corrupted master file table entries that mess up the volume name.

Step 4: Remove Hidden Mount Points

Sometimes Windows has stale mount points (folders linked to a drive) that conflict with the name. In Disk Management, right-click the drive, select Change Drive Letter and Paths, and delete any mount points listed in a folder path. Stick to drive letters.

Alternative Fixes if the Main One Fails

  • Check for hidden drives: Run fsutil fsinfo drives in an admin prompt. If you see duplicate letters (like two F: drives), use mountvol to delete the phantom one: mountvol F: /d.
  • Update USB controllers: If this is an external drive, open Device Manager, expand Universal Serial Bus controllers, right-click each USB Root Hub, and select Update driverSearch automatically.
  • Test on another PC: Plug the drive into a different computer. If it works there, the issue is your Windows registry—try a system restore point from before the error started.
  • Clean the registry (advanced): Open Regedit, navigate to HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices, and back it up first. Delete any entries with the offending drive letter. Reboot and let Windows reassign it. Don't touch this unless you know what you're doing—messing up here can corrupt your volume mappings.

Prevention Tips

  • Always safely eject USB drives before unplugging. That little icon in the system tray isn't optional—it flushes pending writes and closes the file system handle cleanly.
  • Avoid special characters in volume labels. Stick to letters, numbers, underscores, and hyphens. Spaces at the end of a label are a silent killer.
  • Run chkdsk monthly on external drives you use heavily. A quick chkdsk /f can catch MFT corruption before it turns into a STG_E_INVALIDNAME nightmare.
  • Keep Windows updated. I've seen a cumulative update from 2022 (KB5026361) fix a whole class of volume name bugs on Windows 10 22H2.

Let me know if the error still sticks after these steps—I've got a few registry tricks that aren't for the faint of heart, but they've worked on stubborn cases.

Was this solution helpful?