0x80070057 or 'The volume mount point is not valid'

Volume mount point inaccessible – fix when Windows won't mount your drive

Hardware – Hard Drives Intermediate 👁 11 views 📅 Jun 21, 2026

Your drive's mount point got corrupted after a bad shutdown or drive swap. Quick fix: reassign the mount path in Disk Management. No data loss, but act fast.

Quick answer: Open Disk Management (diskmgmt.msc), right-click the partition, select Change Drive Letters and Paths, click Add, and assign a drive letter or mount path. No formatting needed.

Why this happens

I see this a lot with external drives that got unplugged mid-write or after a Windows update botched the boot. The mount point – that link between the drive and a letter like F: or a folder path like C:\Mount\Data – gets corrupted. Windows still sees the partition, but can't open it. You get the error "The volume mount point is not valid" (code 0x80070057). It's not the drive dying, just Windows losing its map. I had a client last month whose backup drive showed up in Disk Management but wouldn't show in File Explorer. Took me two minutes to fix.

Step-by-step fix

  1. Open Disk Management. Press Win + R, type diskmgmt.msc, hit Enter.
  2. Find your drive. Look for the partition that shows a file system (like NTFS) but no drive letter. If it shows RAW, that's a different problem – skip this fix.
  3. Right-click the partition (not the disk bar on the left), choose Change Drive Letters and Paths.
  4. Check the current path. If it's blank or shows an invalid path like a broken folder, select it and click Remove.
  5. Click Add. Pick Assign the following drive letter and pick something like E: or F:. Avoid letters already used or reserved for floppy drives (A, B).
  6. Click OK. Windows should immediately mount the drive. Open File Explorer – it shows up.

If that doesn't work

Sometimes the mount point file on the system partition is actually missing. Here's Plan B:

  • Use a mount point folder. In step 5, choose Mount in the following empty NTFS folder instead of a drive letter. Pick an existing empty folder (like C:\MountPoint). This forces Windows to rebuild the link.
  • Check disk for errors. Open Command Prompt as admin and run chkdsk /f on the affected drive. But be careful – if the drive is RAW, chkdsk can make things worse. Only run it if the file system still shows NTFS.
  • Restart after adding. I've seen cases where Disk Management says it worked, but the drive still doesn't appear until a reboot. Try that before anything drastic.
  • If the drive shows as RAW – that means the file system header is gone. You'll need data recovery tools like TestDisk, but that's a whole different article. For now, stop using the drive and don't format it.

Prevention tip

Always safely remove external drives before unplugging. For internal drives, avoid yanking power during writes. If you use mount points in folders (like on a server), keep a backup of the folder structure. I tell my clients to map drives by letter – it's more resilient to corruption. Also, run sfc /scannow every few months to keep system files clean. This fix works on Windows 10, 11, Server 2016/2019/2022. No special tools needed.

That's it. No need to format, no data loss, no stress. If you hit this error again, you know the drill.

Was this solution helpful?