Fix 0x80130004: Cluster Network Already Offline

This error usually pops up when you're trying to bring a cluster network online through Failover Cluster Manager or PowerShell, and the system tells you it's already offline. You'll see it on Windows Server 2012 R2 through 2022, especially after a node restart or a network adapter failure. I've seen it happen most often when a team member ran a BringsClusterNetworkOffline script and forgot about it, or when a network cable was unplugged during a maintenance window. The exact message reads: STATUS_CLUSTER_NETWORK_ALREADY_OFFLINE (0x80130004).

Why This Happens

The cluster service tracks network states through its own database, not just the Windows networking stack. When you see this error, it means the cluster's own record of that network's status is set to offline—it's not just a temporary glitch. The root cause is often a leftover state from a previous command or a failed health check. The cluster thinks the network is offline and won't let you change it until the state is cleared or manually overridden.

Fix: Force the Network Online

Skip the GUI on this one—PowerShell is faster and more reliable. Here's what I've used in production to solve this.

Identify the network name – Open PowerShell as Administrator on any cluster node. Run:
```
Get-ClusterNetwork
```
Look for the network with State : Offline. Note its Name (e.g., "Cluster Network 1").
Bring it online forcefully – Use this command, replacing "Cluster Network 1" with your network's name:
```
Get-ClusterNetwork "Cluster Network 1" | Set-ClusterNetwork -State Online -Force
```
The -Force flag overrides the cluster's cached state. I've never had this fail if the underlying network adapter is functional.
Verify the state – Run Get-ClusterNetwork again. The state should now read Online. Also check the network's role (Client, Cluster, or Both) to ensure it's correct—sometimes the role gets unset.
Test connectivity – From each node, ping the cluster network's IP address. If that fails, your physical or virtual switch configuration is the real problem. The cluster won't keep a network online if it can't communicate.

What to Check If It Still Fails

If the network goes back to offline after a few minutes, or the command throws a different error, look at these three things:

Network adapter health – Run Get-NetAdapter | Where-Object {$_.Status -eq "Disconnected"} on all nodes. A disconnected adapter will force the cluster network offline automatically. Replace the cable or reconfigure the virtual switch.
Cluster log – Generate a cluster log with Get-ClusterLog -Destination C:\ClusterLogs and search for the network name or the error code. You'll often see a ClusSvc warning about a missing NIC.
Stale DNS records – Check that the cluster network's IP address matches the DNS entry. If it doesn't, the cluster may refuse to bring the network online. Clear any old records from the DNS server and restart the Cluster service on all nodes (Restart-Service ClusSvc — expect a brief failover).

I've seen this error on a 2016 cluster after someone accidentally disabled the NIC in Hyper-V. The fix above worked every time. If you're stuck, leave a comment with your cluster setup and I'll help you dig deeper.