0XC0130006: Cluster network already exists fix

You get error 0XC0130006 - STATUS_CLUSTER_NETWORK_EXISTS when you're trying to add a new node to a Windows Server Failover Cluster (WSFC), or when you're creating a cluster network interface that should be new but the cluster says it's already there. I see this most often after a node was evicted from the cluster but its network adapter configuration didn't get cleaned up properly. Example: you've got a two-node cluster, one node dies hard, you force remove it, then try to add a replacement node with the same IP subnet. The cluster still sees the old network object and throws this error.

Root cause

The cluster stores network definitions in its configuration database. Each network is identified by its subnet and name. When a node leaves the cluster ungracefully (no shutdown, no Remove-ClusterNode), the cluster doesn't delete the associated network objects. They're orphaned. Later, when you try to bring in a new node that uses the same subnet, the cluster sees the existing record and refuses to create a duplicate. The error code 0xC0130006 is STATUS_CLUSTER_NETWORK_EXISTS. Straightforward: the record is still there.

Fix: Remove the stale cluster network

You'll need to remove the orphaned network from the cluster configuration. Do this from an existing cluster node that's still healthy. You don't need to touch the new node yet.

Open PowerShell as Administrator on any node that's part of the cluster and online.
List all cluster networks with this command:
```
Get-ClusterNetwork | Select Name, Address, AddressMask
```
You'll see a table of networks. Look for the one that matches the subnet you're trying to add. There might be multiple entries with the same address mask but different names — that's your problem. Example output:
```
Name                     Address       AddressMask
----                     -------       -----------
Cluster Network 1        192.168.10.0  255.255.255.0
Old Network from Node2   192.168.10.0  255.255.255.0
```
The second one is orphaned.
Identify the orphaned network. Check the Name column carefully. Sometimes it's obvious like "Cluster Network 1" duplicated, sometimes it's got a weird name. If you're not sure, run:
```
Get-ClusterNetwork | fl
```
to see all properties. Look at State — if it's Down but the subnet is active, that's a clue it's stale.
Remove the stale network using this command, replacing <NetworkName> with the exact name from step 2:
```
Get-ClusterNetwork "<NetworkName>" | Remove-ClusterNetwork
```
You'll get a confirmation prompt. Type Y and press Enter. If you want to skip the prompt, use:
```
Get-ClusterNetwork "<NetworkName>" | Remove-ClusterNetwork -Force
```
After a second, you should see no error returned — that means it worked.
Verify the removal. Run Get-ClusterNetwork again and confirm the stale entry is gone. Only the active networks should remain.
Try your original operation — add the node or create the network interface again. The error 0XC0130006 should not appear this time.

What if it still fails?

If you still get the error after removal, check these things:

Did you remove the right network? Run Get-ClusterNetwork again and compare subnets. Sometimes there are three or four copies. Remove all stale ones.
The new node might have a leftover cluster configuration. On the node you're trying to add, open PowerShell and run Get-ClusterNode — if it returns anything, the node thinks it's already in a cluster. Clean it with Remove-ClusterNode or evict it from the cluster using the Failover Cluster Manager on a healthy node.
Network adapter names might mismatch. If the old network was tied to a specific adapter name that no longer exists on the new node (like "Ethernet 2" vs "Ethernet"), the cluster might still see the object but not associate it. In that case, delete the network object and also check Get-ClusterNetworkInterface for stale entries. Remove those too with Remove-ClusterNetworkInterface.
Use the GUI as a backup. Open Failover Cluster Manager, go to Networks in the left pane. If you see a network with status Unavailable or Down and it's the one causing trouble, right-click it and choose Remove. This does the same as the PowerShell command but some people prefer the visual confirmation.
Reboot the node you're adding. Sometimes a stale ARP cache or DHCP lease confuses the cluster. A clean boot helps.

If none of that works, you're looking at a deeper cluster database corruption. In those rare cases, you might need to destroy and recreate the cluster. But that's a last resort — the steps above resolve 95% of 0XC0130006 errors.