Fix STATUS_MOUNT_POINT_NOT_RESOLVED 0XC0000368 on Windows

What's actually happening here

0XC0000368 is Windows's way of saying "I know this drive letter exists, but the volume it points to isn't there anymore." The registry still holds a mapping, but the physical or logical volume is gone, renamed, or not connected. This shows up when you try to open a drive in Explorer, run an app from a shortcut, or boot into a program that references a specific drive path.

The typical trigger: you unplug an external drive, change drive letters, or a USB enclosure died mid-session. The drive letter stays in the registry but points to nothing. On internal drives it can also happen after a failed disk clone or a partition table rewrite.

The fix is to make Windows drop the stale mapping and re-create it. There's a 30-second version, a diskpart version, and a registry version. Start with the first one. If that doesn't work, move down the list.

Fix 1: The 30-second reassignment

Open Disk Management (diskmgmt.msc) and look for the drive that's giving you trouble. It'll either show as unallocated space, or it'll have a drive letter but show "removable" or "no media."

1. Right-click the drive and choose Change Drive Letter and Paths.
2. Click Remove to delete the current letter.
3. Click Add and assign a new letter (pick something that isn't in use).
4. Try opening the drive again.

Why this works: removing the letter deletes the registry mount point. Adding a new one creates a fresh mapping. If the volume is actually present, this resolves the error immediately.

If that doesn't solve it, or the drive doesn't show up at all, move to the next fix.

Fix 2: diskpart cleanup (5 minutes)

When Disk Management won't let you remove the letter, diskpart will. Open an elevated Command Prompt (search cmd, right-click, Run as administrator) and run:

diskpart
list volume
select volume X   (X = the volume number from list)
remove letter=Z   (Z = the problem letter)
exit

Then reassign the letter using assign letter=Y or go back to Disk Management and do it there.

What often happens here is the volume shows as healthy but the letter is in a weird state—half-assigned, or duplicated. diskpart's remove forces a clean unlink, and assign re-creates the mount point properly.

If diskpart says "no volume selected" or the volume isn't listed, the drive might be offline. Type list disk, then select disk N, and run online disk.

Fix 3: Registry surgery (15+ minutes)

This is for when the error persists even after reassigning letters, or when the drive is an internal one that's clearly visible in Disk Management but still throws 0XC0000368 on access. The stale mapping is buried in the registry.

Backup the registry before touching it. In regedit, navigate to:

HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices

Look for a value named \DosDevices\Z: (where Z: is your problem letter). Right-click and delete it. If you don't see that exact letter, look for any value with a partial GUID or a strange binary blob that matches the drive's serial number.

After deleting, restart the PC. Windows will rebuild the mount point when it detects the volume. Then assign a fresh letter.

The reason this works: the registry caches the volume GUID and the drive letter. If the GUID is stale (the volume was recreated during a clone or a partition format), deleting the entry forces Windows to re-enumerate the disk and create a valid mapping. Without this, every boot will try to resolve a nonexistent GUID and you'll keep getting the error.

When to stop and check the hardware

If none of these fixes work, the volume itself might be corrupted or the cable/port is flaky. Try the drive on a different USB port or a different PC. Check if the drive shows in BIOS/UEFI. If it doesn't, it's dead or the enclosure is fried. Replacing the enclosure is cheaper than data recovery, so do that first.

For internal drives, run chkdsk /f /r on the drive from a recovery environment if you can see it there. But if it doesn't even appear in diskpart, that's a hardware failure, not a mount point issue.

What usually trips people up

Most people jump straight to reinstalling Windows or buying a new drive. That's overkill. The error is almost always a logical mapping problem, not physical damage. The 30-second fix resolves it in 8 out of 10 cases. The registry fix gets the rest.

One more thing: if you use a drive caddy or a dock, power cycle it. A warm dock can hold onto a stale mount point even after you switch drives. Unplug it, wait 10 seconds, plug it back in, and run the diskpart fix.

That's the whole flow. Start with the letter reassignment, move to diskpart, and only touch the registry if you're comfortable with regedit. You'll get your drive back without a single reboot in most cases.