Fix STATUS_CLUSTER_NODE_NOT_FOUND 0XC0130004

That error is a membership problem, not a hardware one

Getting 0XC0130004 means Windows Failover Clustering can't find the node's record in the cluster database. The node is physically alive, but its identity inside the cluster is gone or was never fully created. You'll usually see this when trying to bring a node online, run Get-ClusterNode, or validate a cluster after a failed node removal.

Here's the fix that works most of the time.

The fix: evict and re-add the node

Run this from a healthy node that's still part of the cluster. Open PowerShell as Administrator.

# Check which nodes the cluster still knows about
Get-ClusterNode

# Force the problematic node out
Get-ClusterNode "NODE_NAME" | Remove-ClusterNode -Force

# If the node is stuck in 'Down' state, also clear its cluster state on the node itself
# (run this ON the problem node, not on the healthy one)
Clear-ClusterNode -Force

# Now add it back from the healthy node
Add-ClusterNode -Name "NODE_NAME"

Replace NODE_NAME with the actual name. After the Add-ClusterNode, the node should show Up in Get-ClusterNode.

Why this works

What's actually happening here is the cluster database on the node you're trying to fix has a stale or incomplete entry for itself. The eviction removes that broken reference from the cluster's shared database. Then Clear-ClusterNode wipes the local cluster hive so the node comes back clean. When you re-add, it creates a fresh node object and re-syncs the configuration. The reason step 3 matters is that without clearing the local state, the node might still hold onto a conflicting GUID, and the join will fail with the same error.

When evict-and-re-add doesn't work

Sometimes the node won't even appear in Get-ClusterNode, or the removal command fails because the cluster thinks the node is required for quorum. In that case, you need to force the configuration update.

# Force the cluster to forget the node (run on a healthy node)
$cluster = Get-Cluster
$cluster | Set-ClusterParameter -Name "ForceEvict" -Value 1

# Then retry the removal
Get-ClusterNode "NODE_NAME" | Remove-ClusterNode -Force

I've also seen this error after a node was restored from a VM snapshot or a physical backup. The node's computer account in Active Directory might have been orphaned. If the above doesn't clear it, reset the machine account:

# On the problem node, run as Domain Admin
Test-ComputerSecureChannel -Repair

Then reboot the node and join the cluster again.

Less common variations of the same root cause

Cluster service starts but node won't join

You might get 0XC0130004 when the Cluster Service starts but the node immediately falls back to Down. This usually means the node's local cluster database is out of sync with the other nodes — often after a forced shutdown or power loss. The fix is the Clear-ClusterNode step. Don't skip it.

Error appears during New-Cluster creation

If you're creating a brand new cluster and one of the nodes throws 0XC0130004, the node probably had a previous cluster configuration that wasn't removed. You need to clear that node before you can add it to a new cluster.

# On the offending node, before creating the cluster
Clear-ClusterNode -Force

Node stuck in 'Not Configured' state

Occasionally a node shows Not Configured in Failover Cluster Manager but still returns 0XC0130004 when you try to add it. That means the cluster service is running but the node's configuration is incomplete. Re-running the Clear-ClusterNode and then Add-ClusterNode from scratch is your best bet.

Prevention

Most of the time, this error is the result of a node being removed improperly — someone ran Remove-ClusterNode without the -Force flag, or the node lost power during a cluster operation. Here's what I do to avoid it:

• Always use -Force when evicting a node that's down. It's the only reliable way to get rid of a broken node.
• Before you patch or reboot a node, make sure it's in Up state. If it's flapping, fix that first.
• Don't restore cluster nodes from snapshots. The cluster service hates it when the node's state is rolled back to before the node joined. You'll get exactly this error.
• Keep your cluster validation reports. If you run Test-Cluster regularly, you'll catch configuration drift before it becomes a node-killing issue.

That's the whole deal. Evict, clear, re-add. If that fails, reset the machine account. And for the love of uptime, never snapshot a cluster node.