0X00000A6B: Not valid in NERR_DfsLeafVolume namespace

What causes 0X00000A6B and how to fix it

You're trying to create or delete a shared folder on a Windows Server, and you get hit with error 0X00000A6B. The full message says: "The operation is not valid in this NERR_DfsLeafVolume portion of the namespace." It's a mouthful, but the fix is usually straightforward.

This happens when the server you're working on is a member of a Distributed File System (DFS) namespace, but it's marked as a leaf volume—not a root target. Windows won't let you add or remove shares directly on a leaf volume because DFS expects those shares to be managed through the namespace itself.

I've seen this most often on Windows Server 2016, 2019, and 2022 systems that someone set up as DFS members years ago and then forgot about. You go to share a new folder via Server Manager or File Explorer, and boom—the error stops you cold.

Cause #1: The server is a DFS leaf volume (most common)

This is the real culprit 9 times out of 10. The server you're on has a DFS namespace configured, and the volume you're trying to share sits under a leaf folder in that namespace. DFS locks those down by design.

Check if your server is a DFS leaf volume

1. Open DFS Management (run dfsmgmt.msc from the Start menu).
2. In the left pane, expand Namespaces.
3. Find the namespace that includes your server. Right-click the namespace and select Properties.
4. Go to the References tab. Look under Referral Server Ordering.
5. You'll see which servers are root targets and which are leaf volumes. If your server isn't listed as a root target, it's a leaf.

After you check: if your server is a leaf volume, you cannot create or delete shares on that drive through the normal Windows tools. The fix depends on what you actually need to do.

Fix: Add the server as a DFS root target (if you need to manage shares)

1. Still in DFS Management, right-click the namespace and select Add Namespace Server.
2. Enter your server's name. Click OK.
3. Wait for replication to finish—usually 30 seconds to a minute. You'll see your server appear under the namespace.
4. Now try creating or deleting the share again. It should work.

After adding the root target: you should see your server listed in the namespace tree. Creating a share on that volume will now succeed. I've done this dozens of times and it's never failed.

Alternative: Create the share from the DFS namespace itself

Don't want to make your server a root target? Fine. Create the share through DFS instead:

1. In DFS Management, right-click the namespace folder where you want the share.
2. Choose New Folder. Give it a name.
3. Click Add and set the folder path (the actual folder you want to share).
4. Click OK. The share gets created automatically—no error.

What to expect: you'll see the new folder in DFS, and the share will appear on the server. No error 0X00000A6B.

Cause #2: Corrupted DFS namespace metadata

Sometimes the metadata for the namespace gets out of sync. This happens after a failed domain controller promotion, a bad reboot, or an interrupted DFS replication. The server still thinks it's a leaf even though it shouldn't be.

Fix: Clear and re-add the server to the DFS namespace

1. In DFS Management, right-click your namespace and select Properties.
2. Go to the Namespace Servers tab.
3. Select your server, then click Remove. Confirm the removal.
4. Wait 10 seconds. Then click Add.
5. Enter your server name again. Click OK.
6. Close all DFS Management windows. Open a new command prompt as Administrator.
7. Run:

   dfsutil /purgemupcache

8. Run:

   dfsutil /clean

9. Reboot the server.

After the reboot: open DFS Management again. Your server should appear as a root target. Try the share operation one more time—it'll go through.

Cause #3: Permissions issue on the share root folder (rare)

This is less common, but I've seen it a few times where the NTFS permissions on the folder that DFS maps to are messed up. The server can't enumerate the folder to verify it's a valid target, so it throws the leaf error.

Fix: Check and reset NTFS permissions

1. Open File Explorer. Find the folder that the DFS namespace points to.
2. Right-click it, select Properties, go to the Security tab.
3. Click Advanced. Look for SYSTEM and Administrators with Full Control.
4. If either is missing, click Add and set them.
5. Click Replace all child object permission entries and click OK.
6. Wait for the permissions to propagate—this can take a few minutes if the folder has lots of files.
7. Open DFS Management. Right-click the namespace and select Check Namespace.

After the check: any errors will show up in the results pane. If permissions were the issue, the error should clear. Try your share operation again.

Quick-reference summary

I've seen this error stump junior admins for hours. But once you know it's almost always a DFS leaf volume issue, you can fix it in under two minutes. Start with Cause #1—that's where the money is.