Fix ERROR_CLUSTER_IPADDR_IN_USE 0x13C1

This error means Windows thinks the cluster IP is already assigned to another network adapter. Fix it by removing the stale IP from the cluster resource or releasing it from the OS.

You see ERROR_CLUSTER_IPADDR_IN_USE (0X000013C1) when you try to bring a cluster IP address online, and Windows Server Failover Cluster (WSFC) says the IP is already assigned to another network adapter. This typically happens after a node reboot, or when you move the cluster IP from one subnet to another, or when the DHCP lease expired and a different system grabbed the same IP. A common real trigger: you added a second IP to the same cluster resource, then deleted the first one without stopping the resource first.

Root Cause

What's actually happening here is that Windows still has the IP registered in the TCP/IP stack, even though the cluster resource stopped holding it. The cluster tries to take ownership of the IP, but the OS says 'hey, that address is already on adapter XYZ'. The cluster resource does a simple check — it calls GetIpAddrTable to see if the IP is alive on any adapter. If it finds a match, it bails out with 0x13C1.

The reason this happens: the cluster resource didn't properly clean up the IP when it went offline. This can happen if the cluster service crashed, or if you forced a resource offline without using the proper Cluster Manager. The IP stays in the OS as a manual address assignment on the network adapter.

Fix: Remove the Stale IP

You have two paths. Try the first one — it's cleaner.

Option 1: Delete IP from the Cluster Resource

Open Failover Cluster Manager. Connect to your cluster.
Go to Roles, find the role (client access point) that owns the failing IP.
Right-click the role, select Properties.
In the General tab, you'll see the IP addresses listed. Select the one giving you trouble.
Click Remove. Then click OK.
Now bring the role online. It should create a new IP from DHCP or static config.

If it fails, the IP might be stuck on the NIC. Move to option 2.

Option 2: Release the IP from the OS

Log into the node that currently hosts the role (check with Get-ClusterGroup -Name "YourRoleName" in PowerShell).

Open Command Prompt as Administrator.
Run netsh interface ip show config to list all adapters and find the adapter that has the conflicting IP.
Note the adapter name (something like "Cluster Interface" or "Ethernet").
Delete the IP: netsh interface ip delete address "Cluster Interface" 192.168.1.100 (replace IP and name with yours).
Confirm deletion. Then back in Failover Cluster Manager, try to bring the IP resource online again.

The reason step 3 works is that netsh ip delete address fully removes the address from the TCP/IP stack, even if the cluster resource doesn't own it anymore. Cluster sees a clean slate and claims it.

What to Check If It Still Fails

If the error persists after doing both options, check these:

Duplicate IP on another node — the IP might be assigned to a network adapter on a different cluster node. Ping the IP before bringing it online. If you get a reply from a different machine, you have a real IP conflict, not just a stale cluster resource. Fix it there first.
DHCP reservation — if you use DHCP, ensure the reservation matches the MAC address of the cluster's network adapter. If the lease expired and another device grabbed it, you'll get this error too. Renew the lease or use a static IP for the cluster.
Cluster service log — check %SystemRoot%\Cluster\Reports\Cluster.log for entries around the time of the failure. Often the log will say exactly which adapter still holds the IP. Look for lines containing "0x13c1" or "IP address already in use".

Don't bother restarting the cluster service or rebooting the node — that's a sledgehammer approach. The real fix is cleaning the IP from where it's stuck. Option 1 or 2 handles 95% of cases.