Windows Server 2016 – Failover cluster loses quorum after witness outage – 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

Cluster roles stop after witness outage combined with node loss, creating immediate service downtime.

Environment & Reproduction

Common in two-node clusters where witness availability is critical for majority.

Get-Cluster
Get-ClusterQuorum
Get-ClusterNode

Root Cause Analysis

Vote distribution cannot maintain quorum when witness is unavailable and dynamic witness is not helping.

Quick Triage

Validate witness path reachability and current node votes.

Test-NetConnection  -Port 445
Get-ClusterNode | Select Name,State,NodeWeight

Step-by-Step Diagnosis

Gather cluster logs around quorum transition and node eviction events.

Get-ClusterLog -UseLocalTime -Destination C:Temp
Get-WinEvent -LogName System -MaxEvents 200 | ? {$_.ProviderName -match 'FailoverClustering'}

Solution – Primary Fix

Restore witness and apply a quorum model that tolerates one-node failure.

Set-ClusterQuorum -NodeAndFileShareMajority \fsw01clusterwitness
(Get-Cluster).DynamicWitness = 1

Solution – Alternative Approaches

Use cloud witness when file share witness is unavailable.

Set-ClusterQuorum -CloudWitness -AccountName  -AccessKey 

Verification & Acceptance Criteria

Cluster stays online through a controlled single-node drain test.

Suspend-ClusterNode -Name  -Drain
Get-ClusterGroup

Rollback Plan

Revert to pre-change quorum mode from approved change record if instability appears.

Prevention & Hardening

Continuously monitor witness availability and rehearse quorum failure scenarios quarterly.

Related Errors & Cross-Refs

Typically linked with Event IDs 1135 and 1177 during split network conditions.

Related tutorial: View the step-by-step tutorial for Windows Server 2016.

View all Windows Server 2016 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

Microsoft Learn: quorum models and witness best practices for Failover Clustering.