Cluster quorum resource can't have dependencies (0X000013CD)

When you'll see this error

You're setting up a Windows Server Failover Cluster—maybe Server 2019 or 2022. You add a clustered disk as the quorum witness in the cluster configuration. Then you try to set a dependency between that quorum disk and another resource, like a file share or a generic application. Right when you click Apply or OK, the cluster manager spits back:

ERROR_DEPENDENCY_NOT_ALLOWED (0X000013CD)

The exact message reads: "The cluster quorum resource is not allowed to have any dependencies." You'll also see this if you run a PowerShell command like:

Add-ClusterResourceDependency -Resource "Quorum Disk" -Provider "Some Other Resource"

It's a hard block. No workaround through the GUI or PowerShell. The cluster engine just refuses.

What's happening under the hood

The quorum resource is special. It's the vote that decides if your cluster stays alive or goes down during a network split or node failure. Making it dependent on another resource means if that other resource fails, the quorum resource could go offline too. That would break the cluster's ability to establish quorum—exactly what the cluster is designed to prevent.

Think of it like a referee. You wouldn't tie the referee's decision to a player's performance. The referee has to stay independent. Same idea here: the quorum disk or file share witness can't rely on anything else.

The real root cause is almost always a misunderstanding of what the quorum resource does. People see a disk they've dedicated to quorum and think, "This disk should be available before the cluster services start," so they add a dependency. But the cluster already handles that ordering internally. You don't need to override it.

In some cases, this error pops up because you're trying to use the quorum resource as a regular application disk—hosting a database or a file share on it. That's a bad idea anyway. Quorum disks should be small (512 MB to 2 GB), simple, and used only for the quorum log.

The fix (step by step)

1. Open Failover Cluster Manager on any node in the cluster. You'll see the cluster name on the left pane.
2. Expand the cluster name, then expand Storage. Right-click the disk that's assigned as the quorum witness and select Properties.
3. Go to the Dependencies tab. You'll see the dependency you tried to add listed there. Select it and click Remove. If the tab is empty, skip to step 5.
4. Click Apply and then OK. You should see the error disappear. After you click Apply, the dependency list should go empty.
5. Don't try to add a dependency back. Instead, ask yourself: what did you need that dependency for? If you wanted the quorum disk to be online before another service starts, stop. The cluster already brings quorum online first during startup. You can verify this by looking at the cluster log: Get-ClusterLog shows the order.
6. If you need that disk for application data (like SQL Server logs), remove it as the quorum witness. Right-click the cluster name, go to More Actions > Configure Cluster Quorum Settings. Choose Select the quorum witness and pick a different disk or a file share witness. Then you can add the original disk back as a regular cluster disk and set dependencies on it freely.
7. Run validation to make sure everything's clean. Open PowerShell as admin and run:

Test-Cluster

Check the output for any warnings about dependencies or quorum.

If it still fails

Sometimes the error persists even after removing dependencies because the cluster is in a weird state. Try these in order:

• Restart the Cluster service on all nodes: Stop-Service ClusSvc; Start-Service ClusSvc on each node, one at a time.
• Check for duplicate quorum resources. Open Failover Cluster Manager, go to Roles, and look for any role that has a quorum resource listed twice. If you see two quorum disks, you've got a misconfiguration. Remove one via PowerShell: Remove-ClusterResource -Name "Quorum Disk 2".
• Review the cluster log for more clues. Run Get-ClusterLog -Destination C:\Logs -TimeSpanMinutes 10. Open the generated .log file and search for "ERROR_DEPENDENCY_NOT_ALLOWED" or "0x13CD". The log will show you exactly which resource triggered the block.
• If nothing else works, destroy and recreate the quorum from scratch. Run Set-ClusterQuorum -NoWitness to remove the witness, then Set-ClusterQuorum -Disk Witness and pick a fresh disk. You'll need downtime for this.

In my 12 years of managing clusters, I've seen this error about a dozen times. Every single case was someone trying to make the quorum disk do double duty. Don't do it. Keep it simple, keep it separate, and you won't see 0X000013CD again.