Windows Server / Hyper-V & Failover Clustering
Find the failed cluster resource rather than cycling an entire role
A clustered service can be offline because one dependent resource failed. Inspect the resource and dependency context.
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-ClusterResource | Select-Object Name, ResourceType, State, OwnerGroup, OwnerNodeRead the result
The listing identifies resource state and ownership. A failed dependency can explain several secondary offline resources.
Resolve and verify
Inspect the first failure and its specific application or storage events. Repair that dependency and bring the role back through the cluster's supported workflow.
Before changing production
Do not repeatedly move the whole role or change restart thresholds to hide an unresolved fault.