STATUS_NO_GUID_TRANSLATION 0XC000010C Fix – File Server Crash

When This Error Hits

You're managing a Windows Server 2022 or 2019 file server. Users start complaining they can't access a shared folder. Then you check Event Viewer and see STATUS_NO_GUID_TRANSLATION (0XC000010C) logged against the file system. Sometimes the server even blue-screens with the same code. Had a client last month whose entire DFS-N namespace broke because of this. The trigger? A volume mount point got orphaned after a failed drive replacement. Or a broken symbolic link inside a shared folder.

Root Cause in Plain English

Windows uses GUIDs (Globally Unique Identifiers) to track drives and volumes internally. Every volume gets a GUID when you format it. The file system driver uses that GUID to find the physical location of files. When something corrupts that mapping—like a bad cluster on the NTFS volume, a missing volume mount point, or a DFS link pointing to a deleted share—the driver can't translate the GUID back to a real path. That's the 0XC000010C error. It's not a driver bug. It's a data structure corruption inside the volume's metadata.

The Fix – Step by Step

Check the Volume GUIDs with diskpart.
Open Command Prompt as admin. Run diskpart, then list volume. Note the Volume ### column, not the drive letter. Then run detail volume X (replace X with the volume number showing the error). Look for GUID line. If it shows No GUID or a garbled string, that's your problem.
```
diskpart
list volume
select volume 3
detail volume
```
Run chkdsk with /f and /r.
This fixes NTFS metadata corruption. On a server, schedule it at reboot unless you can take it offline. chkdsk C: /f /r. For a volume mount point (like D:\Mount\Data), run chkdsk D: /f /r. The /r flag locates bad sectors and recovers readable info.
```
chkdsk E: /f /r
Y (schedule at next reboot)
```
Check for orphaned volume mount points.
Go to Disk Management. Look for volumes mounted as folders (right-click a volume, choose Change Drive Letters and Paths). If you see a mount path that points to a missing volume, remove it. Re-add after fixing the destination volume. I once found a dead mount point to an old backup drive that caused this error on every file access.
```
# PowerShell: find mount points without a backing volume
Get-Volume | Where-Object {$_.DriveType -eq 'Fixed' -and $_.DriveLetter -eq $null} | fl
```
Delete and recreate the broken GUID.
If chkdsk didn't fix it, the volume GUID itself might be corrupt. Use diskpart to assign a new GUID. Warning: This can break volume-specific settings like BitLocker or pagefile paths. Do this only if you have a backup.
```
diskpart
select volume X
uniqueid disk
# If it shows a GUID, note it. Then set a new one:
uniqueid disk id=12345678-1234-1234-1234-123456789abc
```
Remove and re-add the shared folder.
Sometimes the share's metadata (stored in the registry under HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Shares) points to a corrupted GUID. Go there, delete the broken share entry (after exporting it as a .reg backup), then re-create the share through net share or the GUI.
```
net share DeleteName /delete
net share NewName=C:\SharedFolder /grant:everyone,FULL
```

What to Check If It Still Fails

If none of that worked, you likely have deeper hardware issues. Run a full SMART check on the disk (wmic diskdrive get status). Replace the drive if you see Bad or Caution. Also check for DFS link problems: open DFS Management, right-click the namespace, choose Check Namespace. If you find dead folder targets, remove them. One last thing: this error can also come from antivirus scanning file servers in real-time—had a client whose Symantec Endpoint Protection caused this by locking volume handles. Try disabling AV temporarily to rule that out.