Windows Server 2022 – Failover cluster loses quorum after single node failure – Fix & Prevention

📖 ~1 min read

Table of contents

1. Symptom & Impact
2. Environment & Reproduction
3. Root Cause Analysis
4. Quick Triage
5. Step-by-Step Diagnosis
6. Solution – Primary Fix
7. Solution – Alternative Approaches
8. Verification & Acceptance Criteria
9. Rollback Plan
10. Prevention & Hardening
11. Related Errors & Cross-Refs
12. References & Further Reading

Symptom & Impact

After one cluster node fails, the remaining nodes lose quorum and clustered roles stop. This creates immediate service disruption for workloads hosted on Failover Clustering.

Environment & Reproduction

Occurs in two-node or uneven-vote clusters with misconfigured witness. Reproduce by isolating one node or network path during business hours simulation.

Get-Cluster
Get-ClusterNode
Get-ClusterQuorum

Root Cause Analysis

Node and witness vote math no longer satisfies dynamic quorum after node failure. Common causes include witness offline state, stale cloud witness key, or disabled dynamic witness.

Quick Triage

Confirm cluster service state, quorum mode, and witness reachability first.

Get-Service ClusSvc
Get-ClusterLog -UseLocalTime -Destination C:Temp
Test-NetConnection -ComputerName  -Port 443

Step-by-Step Diagnosis

Collect cluster logs, validate votes, and verify witness health before changing configuration.

(Get-Cluster).QuorumType
Get-ClusterNode | Select Name,State,NodeWeight
Get-WinEvent -LogName System -MaxEvents 200 | ? {$_.ProviderName -match 'FailoverClustering'}

Solution – Primary Fix

Restore a healthy witness and set a quorum model that preserves majority during one-node loss.

Set-ClusterQuorum -NodeAndFileShareMajority \fsw01clusterwitness
(Get-Cluster).DynamicQuorum = 1
(Get-Cluster).DynamicWitness = 1
Start-ClusterNode -Name 

Solution – Alternative Approaches

Use cloud witness or disk witness if file share witness is unavailable.

Set-ClusterQuorum -CloudWitness -AccountName  -AccessKey 
# or
Set-ClusterQuorum -DiskWitness 

Verification & Acceptance Criteria

Cluster remains online after simulated single-node outage; all critical clustered roles fail over successfully.

Get-ClusterGroup | Select Name,State,OwnerNode
Suspend-ClusterNode -Name  -Drain
Get-ClusterNode

Rollback Plan

If instability appears, revert to previous quorum mode and witness settings from pre-change notes.

Set-ClusterQuorum -NodeMajority
Import-Clixml C:Tempcluster-prechange.xml

Prevention & Hardening

Monitor witness connectivity, enforce cluster baseline checks, and test quorum quarterly with controlled failover drills.

Related Errors & Cross-Refs

Common linked events include 1177, 1135, and role flapping during network partitions. Also review heartbeat and CSV path stability.

View all Windows Server 2022 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

Microsoft Learn: Failover Clustering quorum models, dynamic quorum guidance, and cloud witness configuration for Windows Server 2022.