Fix 0X00000230 GUID Translation Error in Windows

This error pops up when Windows can't match a GUID to a readable name. You'll see it during backup or disk management. The fix is usually a registry tweak or a driver update.

You're in the middle of a backup or checking disk volumes, and then you get slapped with ERROR_NO_GUID_TRANSLATION (0X00000230). Windows is basically saying: "I see this GUID (that long string of numbers and letters), but I have no clue what device or drive it belongs to." Annoying, right? Let's fix it.

The Direct Fix: Registry Tweak

This error almost always traces back to a corrupted or missing entry in the Volume{...} registry keys. Volume Shadow Copy (VSS) uses GUIDs to identify storage volumes. If Windows can't translate one, it throws 0X00000230.

Press Win + R, type regedit, hit Enter.
Click Yes if UAC asks.
Go to:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{71A27CDD-812A-11D0-BEC7-08002BE2092F}
(That's the GUID for Volume Manager class.)
Right-click the {71A27CDD-812A-11D0-BEC7-08002BE2092F} key, select Export, save a backup somewhere safe.
While still on that key, look in the right pane for a value named UpperFilters or LowerFilters. If you see either, right-click it and delete it. (Do not delete the entire key — just those two values.)
Close regedit. Restart your computer.

After reboot, try the operation that gave you 0X00000230 again. You should see it work now. If it still fails, move to the next section.

Why That Works

The UpperFilters and LowerFilters registry values tell Windows which drivers to load for storage devices. If a filter driver (like an old backup tool or antivirus) gets removed but leaves an orphaned entry, the translation between GUID and device name breaks. Deleting those values forces Windows to rebuild the filter chain fresh. It sounds scary, but it's safe — Windows will recreate them as needed. Nine times out of ten, this is the culprit.

Less Common Variations

If the registry fix didn't do it, here are three other things to check.

1. Update or Reinstall the Disk Driver

Open Device Manager (right-click Start > Device Manager).
Expand Disk drives.
Right-click each drive listed, choose Update driver > Search automatically.
If Windows finds nothing, go to your PC or motherboard manufacturer's site and grab the latest storage controller drivers (for example, Intel Rapid Storage Technology or AMD SATA drivers). Install them manually.

2. Check Volume Shadow Copy Service

Open Services.msc (Win + R, type services.msc).
Find Volume Shadow Copy. Double-click it.
If it's not Running, click Start. Set Startup type to Automatic.
Also check Microsoft Software Shadow Copy Provider — same settings.

3. Run VSS Diagnostics

Open an administrator command prompt and run:

vssadmin list shadows
vssadmin list writers

If you see any writer with a state of Failed or Stable (but non-retryable error), that writer's service needs manual restart. Note the writer name (like "System Writer" or "SQL Server Writer"), then restart its related service in Services.msc.

Prevention for Next Time

This error usually happens after you uninstall a backup program (like old Norton Ghost or Acronis) incorrectly, or after a failed Windows Update that involved storage components. To avoid this mess:

Always use the program's official uninstaller, not just delete folders. Many backup tools hook into the Volume Manager filter chain.
Keep your chipset and storage drivers current. Outdated Intel RST drivers have been a known cause of this error on Windows 10 version 22H2 and Windows Server 2019.
Schedule regular system file checks: run sfc /scannow once a month, and DISM /Online /Cleanup-Image /RestoreHealth after any big update.

If you're still stuck after all this, check the Windows Event Viewer (Applications and Services Logs > Microsoft > Windows > VolumeShadowCopy). Look for event IDs 12289 or 12290 — those will point you to the exact volume causing the GUID translation failure. Sometimes you just need to note that GUID and check if its disk is disconnected or has a bad cable.