⚠️ 2 verified solutions available for Error 5953 — Last updated 2026-03-24
Error 5953 📋

Fix ERROR_CLUSTER_RESOURCE_VETOED_MOVE_INCOMPATIBLE_NODES — Windows Error Code 5953

Error 5953 (ERROR_CLUSTER_RESOURCE_VETOED_MOVE_INCOMPATIBLE_NODES) is a Windows DNS & WINS error that occurs when a resource vetoed a move between two nodes because they are incompatible.. This guide provides step-by-step solutions to resolve this issue.

🏷️ Code: 5953 📛 ERROR_CLUSTER_RESOURCE_VETOED_MOVE_INCOMPATIBLE_NODES 📅 Updated: 2026-03-24 ⏱️ 2 Solutions
⚡ Quick Fix

Flush DNS and Switch Servers: Open Command Prompt as Administrator

👇 See all 2 solutions below
🐞 Auto-Fix Script for Error 5953
⚠️ How to use: Open PowerShell as Administrator, paste the code above, and press Enter.
✓ Safe & Transparent ✓ No Downloads Required ✓ Review Before Running
📑 Table of Contents
What is Error 5953? Common Causes Step-by-Step Solutions Prevention Tips Related Errors

💡 What is Error 5953?

Windows System Error Code 5953, known as ERROR_CLUSTER_RESOURCE_VETOED_MOVE_INCOMPATIBLE_NODES, is a DNS & WINS error that occurs during DNS resolution and WINS name resolution. The error indicates that: A resource vetoed a move between two nodes because they are incompatible. When this error is encountered, the Windows operating system was unable to complete the requested operation within the DNS/WINS services subsystem. The error code 5953 is returned by the GetLastError() function and provides developers with a specific identifier to diagnose the root cause of the failure. The symbolic name ERROR_CLUSTER_RESOURCE_VETOED_MOVE_INCOMPATIBLE_NODES maps directly to this numeric code and is commonly referenced in Microsoft documentation, developer forums, and system logs. Understanding this error and its context within DNS resolution and WINS name resolution is essential for effective troubleshooting.

⚠️ Common Causes

  • System resource conflict: A resource vetoed a move between two nodes because they are incompatible.
  • DNS server misconfigured
  • Stale DNS cache entries
  • Hostname cannot be resolved
📚 Comprehensive Guide

Troubleshooting COM and DCOM Architectural Failures (Event ID 10016)

A comprehensive guide on Component Object Model (COM), Distributed COM (DCOM), and how to safely interpret and resolve Event ID 10016 errors.

Read the full guide →

✅ Step-by-Step Solutions

1 Flush DNS and Switch Servers
  1. Open Command Prompt as Administrator
  2. Run: ipconfig /flushdns
  3. Change DNS to Google (8.8.8.8) or Cloudflare (1.1.1.1)
  4. Run: ipconfig /registerdns
Advertisement
[AdSense In-Article Ad Generator]
Show Advanced Solutions (1 more)
2 Advanced Diagnostic for ERROR_CLUSTER_RESOURCE_VETOED_MOVE_INCOMPATIBLE_NODES
  1. Open Windows Event Viewer (eventvwr.msc)
  2. Navigate to Windows Logs → System to find Event ID 5953
  3. Look for associated warnings that occurred immediately before the system crashed
  4. Right-click the entry and export the log file for further analysis

🎬 Video Tutorials

▶️ Watch Video Tutorials
How to fix Error 5953 (Cluster Resource Vetoed Move Incompatible Nodes)
Open on YouTube →

💻 Diagnostic Command

Run this PowerShell command to find related events in your system log:

Get-EventLog -LogName System -Newest 20 | Where-Object {$_.Message -like "*5953*" -or $_.Message -like "*ERROR_CLUSTER_RESOURCE_VETOED_MOVE_INCOMPATIBLE_NODES*"} | Format-List

💡 Open PowerShell as Administrator, paste the command above, and press Enter.

🛡️ Prevention Tips

  • Use reliable DNS (8.8.8.8 or 1.1.1.1)
  • Flush DNS cache periodically
  • Monitor DNS resolution performance
Was this helpful?
Last updated: 2026-03-24
📖
Based on Official Microsoft Documentation
Solutions Tested on Windows 10 & 11
Error codes sourced from Microsoft Win32 SDK. Updated 2026-03-24.
🔧 Diagnose Your Error