0X00000A6A

Fix 0X00000A6A: DFS leaf volume error on Windows Server

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

This error means you're trying to create a DFS link on a folder that's already a DFS root target. The fix is simple: remove the conflicting DFS role or use a subfolder.

Quick Answer

Remove the DFS namespace role from the server hosting the folder, or create the DFS link in a subfolder that isn't a root target.

What's Really Happening Here

I've seen this error pop up most often when someone tries to add a DFS link pointing to a shared folder that's already a DFS namespace root target. The error code 0X00000A6A maps to NERR_DfsNotALeafVolume, which is Windows's way of saying "you can't put a leaf (link) on top of a root (namespace target)." The DFS namespace structure is strict — a folder can serve as either a root target OR a link target, but not both. This usually happens during migrations or when someone reorganizes file shares without cleaning up old DFS configs first.

Fix Steps

  1. Identify the conflicted folder. Open DFS Management console (dfsmgmt.msc). Check both the Namespace Roots and Links sections. Find the exact folder path throwing the error.
  2. Check if the folder is a DFS root target. In the console, right-click the namespace root → Properties → References tab. If the server appears in the list of root targets, that's your conflict.
  3. Remove the root target role. Select the server and click Remove. This folder is no longer a namespace root. Apply the change.
  4. Or move the link target to a subfolder. If you need to keep the root target, create a subfolder under it (e.g., \server\share\subfolder) and point the DFS link there instead.
  5. Verify the fix. Try adding the DFS link again. It should complete without error. Run dfsutil /pkginfo to confirm the namespace is clean.

Alternative Fixes If the Main One Fails

  • Recreate the DFS namespace from scratch. If removing the root target doesn't work, delete the namespace root on that server and create a new one on a different folder. Then add your link target. This burns 5 minutes but guarantees a clean state.
  • Check for stale DFS references in AD. Old DFS objects can linger in Active Directory. Run dfsdiag /testdcs to find orphaned entries. Use ADSI Edit to remove them — but only if you're comfortable with AD surgery.
  • Reboot after changes. Sounds dumb, but I've seen the DFS service cache root target info. A reboot flushes it. Try net stop dfs && net start dfs first if you don't want a full restart.

How to Prevent This Going Forward

Plan your namespace structure before you start clicking. Decide which servers host root targets and which host link targets. They should never overlap. Use naming conventions — for example, prefix root target shares with DFSROOT_ and link targets with DFSLINK_. Document the mapping. If a server needs to serve both roles (rare but happens in branch offices), create separate shares on different volumes. The error 0X00000A6A is 100% preventable with a little planning.

One last thing: don't bother trying to force the link creation with dfsutil — it'll silently fail or corrupt the namespace. You've been warned.

Was this solution helpful?

0X00000A6A NERR_DfsNotALeafVolume DFS error DFS leaf volume DFS namespace error Windows Server DFS fix DFS root target conflict DFS link creation failed Server 2012 DFS Server 2016 DFS Server 2019 DFS DFS namespace troubleshooting DFS replication error 0X00000A6A fix DFS management console error