ERROR_CLUSTER_NODE_SHUTTING_DOWN - 5073 (0x13D1)
The cluster node is shutting down.
Updated: Feb 21, 2026
Technical Meaning
The error code ERROR_CLUSTER_NODE_SHUTTING_DOWN (5073, 0x13D1) indicates that a cluster node is in the process of shutting down. This typically occurs during planned maintenance or when a node needs to be decommissioned.
Error Details
This error is returned by Windows Cluster Services APIs and tools when an operation cannot proceed because the specified node is being shut down. The node might be part of a failover cluster, where nodes can take over each other's responsibilities in case of failure.
Usage Context
The context for this error includes scenarios such as:
- Planned maintenance: A node is scheduled to go offline for updates or repairs.
- Decommissioning: A node is being removed from the cluster infrastructure.
- Node failure: The system detects that a node has failed and initiates a shutdown sequence.
Developer Interpretation
When this error occurs, developers should understand that the operation they are attempting to perform cannot be completed because the target node is in the process of shutting down. Developers should handle such errors by retrying the operation on another available node or waiting for the node to fully shut down before proceeding with other operations.
Related Errors
ERROR_CLUSTER_NODE_NOT_FOUND(5074, 0x13D2): The specified cluster node does not exist.ERROR_CLUSTER_NODE_EXISTS(5068, 0x13B4): A node with the same name already exists in the cluster.
FAQ
Q: What causes this error?
A: This error is typically caused by a planned shutdown or decommissioning of a cluster node. It can also occur if the node has failed and the system is initiating a shutdown sequence.
Q: How should I handle this error in my code?
A: You should retry the operation on another available node or wait for the node to fully shut down before proceeding with other operations.
Summary
The ERROR_CLUSTER_NODE_SHUTTING_DOWN (5073, 0x13D1) is a generic error indicating that a cluster node is in the process of shutting down. Developers should handle this by retrying operations on another available node or waiting for the node to fully shut down before proceeding.