Fix ERROR_CLUSTER_INVALID_NETWORK_PROVIDER (0X000013B9)

Quick Answer

Run netsh int ip reset and winsock reset on the node, then uncheck IPv6 on the cluster network adapter. If that fails, remove and re-add the network adapter from within Failover Cluster Manager.

Why This Happens

You'll see error 0X000013B9 when a node tries to join a cluster and the cluster service can't initialize the network provider. The culprit here is almost always a corrupted TCP/IP stack or a binding that got out of sync — maybe after a Windows Update, a driver rollback, or someone fiddling with network bindings. I've seen it most often on Windows Server 2019 after a cumulative update that broke IPv6 bindings. The cluster service expects the adapter to have a valid network provider (usually TCP/IPv4), but something in the LSU (Lower Stack Upper) is hosed.

Don't bother reinstalling the whole cluster role — that rarely helps and wastes time. The fix is simpler.

Fix Steps

1. Reset Winsock and TCP/IP
   On the affected node, run these commands as Administrator:

   netsh winsock reset
   netsh int ip reset

   Reboot the node after. This clears any corrupted LSP (Layered Service Provider) entries that might block the cluster provider.
2. Disable IPv6 on the cluster adapter
   Open Network Connections (ncpa.cpl), right-click the cluster network adapter, go to Properties, and uncheck Internet Protocol Version 6 (TCP/IPv6). Click OK. The cluster service prefers IPv4 anyway, and IPv6 bindings are a common source of this error.
3. Re-register the cluster network provider
   Open PowerShell as Admin and run:

   Get-ClusterNetwork -Cluster (Get-Cluster).Name | Set-ClusterNetwork -Enable

   This re-enables all cluster networks. Then restart the Cluster service:

   Restart-Service -Name ClusSvc

4. Remove and re-add the network adapter in Failover Cluster Manager
   If the error persists, open Failover Cluster Manager, go to Networks, find the problematic adapter, and select Remove. Then Add Network and select the adapter. This forces the cluster to rediscover the network provider.

Alternative Fixes

• Roll back or update the network driver — Open Device Manager, find the adapter, go to Properties > Driver. Try Roll Back Driver first (if an update just ran). If that doesn't work, download the latest driver from the manufacturer (Intel, Broadcom, Mellanox) and install. Windows Update drivers are often too generic for cluster adapters.
• Check for third-party firewall interference — Temporarily disable any non-Microsoft firewall (like McAfee or Symantec) and see if the error clears. They sometimes block cluster network traffic at the provider level. If so, add the Cluster.exe and ClusSvc.exe to the firewall exceptions.
• Reset the cluster node itself — Last resort:

  Remove-ClusterNode -Name <NodeName>
  Add-ClusterNode -Name <NodeName>

  This rebuilds the node's cluster database. It's a bit nuclear but works when nothing else does.

Prevention Tip

Always test Windows Updates in a staging cluster before deploying to production. The biggest trigger for 0X000013B9 is a patch that updates the network stack. Also, set your cluster adapters to use static IPs and disable DHCP — that reduces binding corruption. And never, ever install any third-party network drivers through Windows Update. Grab them from the OEM's site directly.