Cluster Resource Scheduler Won't Start on Server 2019

Quick answer

Stop the cluster service on all nodes, delete the scheduler resource from the cluster database using PowerShell, then restart the service. The cluster will recreate the resource. This takes 10 minutes.

Why this happens

I've seen this on Server 2019 and 2022 after a Windows Update that changed the network adapter binding order, or after someone moved a cluster disk to another node without draining roles. The scheduler resource gets stuck in a pending state. The cluster tries to start it, fails, logs Event ID 1069, and then nothing works—no failovers, no resource moves. The fix isn't a reboot, it's a reset.

Fix steps

1. Open PowerShell as Admin on any node that can still connect to the cluster. If no node can connect, skip to step 4.
2. Run Get-ClusterResource "Cluster Resource Scheduler". If you see a state like "Pending" or "Failed", that's your problem. If the resource doesn't exist, you've got a different issue—check cluster logs.
3. Run Stop-Cluster to stop the cluster service on all nodes. After this, the cluster will be down. Users will lose access to any clustered services (like file shares or SQL). Plan for that downtime.
4. On each node, open Services.msc, find the Cluster Service, and set it to Manual start. Don't start it yet. Do this on all nodes.
5. Pick one node. Open PowerShell as Admin on that node. Run Clear-ClusterResource "Cluster Resource Scheduler". This deletes the resource from the cluster database. You'll see no output if it works.
6. Now set the Cluster Service back to Automatic on all nodes. Start the service on one node first. Wait 30 seconds. After it starts, check Get-ClusterResource. The Cluster Resource Scheduler should show as Online. If it does, start the service on the other nodes.
7. Run Get-ClusterGroup. You should see all your groups (like SQL Server or File Server). They'll be in Offline state. Start them manually with Start-ClusterGroup "GroupName" for each group.

Alternative fixes

If the steps above don't work:

• Check network dependencies: The scheduler resource depends on network connectivity between nodes. Open Failover Cluster Manager, right-click the Cluster Resource Scheduler, go to Properties, Dependencies tab. If there's a dependency on an IP address or network name that's missing or misconfigured, remove that dependency. I've seen this happen after moving a cluster to a different subnet.
• Reset the cluster quorum: Sometimes the scheduler fails because the cluster can't form quorum. Run Set-ClusterQuorum -NodeWeight 1 on all nodes to force each node to have a vote. Then restart cluster services. If quorum was the issue, the scheduler will start now.
• Force remove and recreate: If nothing works, destroy the cluster and rebuild it. Export the cluster configuration first with Export-ClusterConfiguration -Path C:\cluster.csv. Then remove the cluster. Recreate it with the same nodes and import the config. This is a nuclear option—only do it if you're ready to rebuild.

Prevention tip

Before applying any Windows Update, take a snapshot of each node (if virtual) or back up the cluster registry. Also, after changing network bindings, run Test-Cluster to validate that the cluster still works. If you move cluster disks around, always drain the node first. The scheduler hates sudden disk moves.

What to expect after the fix

Once the scheduler is back online and groups are started, run Get-ClusterResource to confirm all resources are in Online state. Event logs should stop showing Event ID 1069. Test a failover by moving a group to another node with Move-ClusterGroup "GroupName" -Node "OtherNode". If that works, you're good.