Windows Server / Hyper-V & Failover Clustering
Inspect cluster quorum configuration before a recovery decision
A cluster connectivity incident can threaten quorum even when some nodes still run workloads. Establish the actual quorum configuration.
Environment and inputs: Windows Server 2022 / 2025 baseline · Windows PowerShell with the specified role or RSAT modules; native utilities are identified in the text. Use delegated administration and elevation only where required.
Start with this check
Confirm the host, shell and access role. Replace sample names, paths, domains and interfaces with approved targets. These are diagnostic commands; assess policy and workload impact before making changes.
Get-ClusterQuorumRead the result
The query reports quorum type and witness resource where configured. Effective voting and current membership require additional context.
Resolve and verify
Compare witness reachability and node membership with the approved design, then repair the failed network or witness dependency through the cluster owner.
Before changing production
Do not force quorum or start competing cluster partitions without a coordinated disaster-recovery procedure.