Fix 0X00000A73 NERR_DfsNotSupportedInServerDfs on Windows Server

When This Error Shows Up

You're setting up a Distributed File System (DFS) namespace on a Windows Server—maybe Windows Server 2019 or 2022. You open the DFS Management console, right-click "Namespaces," and select "New Namespace." You type the server name, click through the wizard, and then you get slapped with this error:

0X00000A73 - The operation is not supported. (NERR_DfsNotSupportedInServerDfs)

This usually happens on a brand-new server that's been promoted to a domain controller or just joined the domain. You've installed the File Services role but didn't check the box for DFS Namespaces. That's the real trigger.

What's Actually Going On

The error tells you straight up: the DFS operation isn't supported on this server. But it's not a hardware problem or a bug. It's a missing role. The DFS Namespaces feature isn't installed. Without it, the server can't host a namespace. Period.

Windows Server splits DFS into two separate roles: DFS Namespaces (the folder hierarchy) and DFS Replication (file syncing). You can install one without the other. If you only installed Replication (maybe for a lab test) and skipped Namespaces, you'll see this error. The system literally can't process the request because the service isn't there.

One more thing: this error can also pop up if you're trying to create a domain-based namespace and the server isn't a domain controller (or at least joined to the domain). But 9 times out of 10, it's the missing role.

Fix: Install the DFS Namespaces Role

You have two paths: GUI (Server Manager) or PowerShell. I'll walk both. Pick whichever you're more comfortable with.

Option 1: Using Server Manager

1. Open Server Manager. You'll find it pinned to the taskbar or in the Start menu.
2. Click Manage in the top-right corner, then select Add Roles and Features.
3. Click Next on the "Before you begin" page.
4. Select Role-based or feature-based installation and click Next.
5. Make sure your server is selected in the server pool. Click Next.
6. Scroll down the roles list to File and Storage Services (do not expand it yet).
7. Expand File and iSCSI Services.
8. Check the box for DFS Namespaces. A pop-up might ask to add management tools—click Add Features.
9. Click Next through the remaining pages. On the confirmation page, click Install.
10. Wait for the install to finish. It usually takes less than a minute. You'll see "Installation succeeded."
11. Close the wizard. Now go back to the DFS Management console and try creating the namespace again.

After you click Apply, you should see the status bar complete without errors. The namespace should appear in the console tree.

Option 2: Using PowerShell (Faster)

1. Open PowerShell as Administrator. Right-click the Start button and choose Windows PowerShell (Admin) or Terminal (Admin).
2. Run this command:

Install-WindowsFeature -Name FS-DFS-Namespace -IncludeManagementTools

3. Wait for the output. You'll see something like this:

Success Restart Needed Exit Code      Feature Result
------- -------------- ---------      --------------
True    No             Success        {DFS Namespaces, DFS Management Tools}

If it says "Success" and "Restart Needed: No," you're good. Close PowerShell and test the namespace creation.

What If It Still Fails?

If the error keeps showing up after installing the role, check these three things:

• Reboot required? Sometimes the install needs a restart even if PowerShell says it doesn't. Reboot the server and try again.
• Server not in domain? DFS namespace creation (domain-based) requires the server to be joined to a domain. Run Get-ComputerInfo | Select-Object CsDomain in PowerShell. If it returns nothing or "WORKGROUP," you need to join the domain first.
• Permission issue? You need local admin rights on the server to create a namespace. Also, for domain-based namespaces, you need Domain Admin rights or delegated permissions in Active Directory.

Still stuck? Check the Event Viewer under Applications and Services Logs > DFS Namespaces > Admin. There might be a more detailed error message. I've seen cases where the server's C drive is full or the NTFS permissions on the shared folder block the namespace creation. But honestly, the missing role is the culprit 95% of the time.