How to fix Error 60 on Windows 11

by

Why This Error Happens

Error 60 (“The remote adapter is not compatible”) typically occurs when the Remote Desktop Protocol (RDP) client attempts to negotiate a connection using a network adapter driver or Winsock configuration that is outdated, corrupted, or mismatched with the security protocols required by the host. This is often triggered by a corrupted network stack, an outdated NIC driver, or conflicting virtual adapters created by VPN software, Hyper-V, or third-party antivirus tools. It can also result from a broken Winsock catalog after a Windows Update or driver rollback.

Step-by-Step Resolution Guide

  1. Reset the Winsock catalog and TCP/IP stack
    Open Command Prompt as Administrator and run:
   netsh winsock reset
   netsh int ip reset

Restart your PC after running these commands.

  1. Update or reinstall the network adapter driver
  • Go to Device Manager > Network Adapters.
  • Right-click your primary adapter (Ethernet or Wi-Fi) → Update driver → “Search automatically for drivers.”
  • If that fails, right-click → Uninstall device, check “Delete the driver software,” then reboot to let Windows reinstall a clean driver.
  1. Disable conflicting virtual adapters
  • Open ncpa.cpl (Network Connections).
  • Temporarily disable any VPN adapters, Hyper-V Virtual Switches, or VMware/VirtualBox virtual NICs that aren’t in active use.
  • Retry the Remote Desktop connection.
  1. Check and repair system files
    Run the following in an elevated Command Prompt to fix underlying corruption:
   sfc /scannow
   DISM /Online /Cleanup-Image /RestoreHealth
  1. Update Remote Desktop Client settings
  • Open Registry Editor (regedit) and navigate to:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp
  • Ensure SecurityLayer is set to 1 (Negotiate) rather than 0 or 2, which can cause adapter compatibility mismatches during handshake.

Alternative or Verification Steps

  • After applying the fixes, test connectivity by launching mstsc and connecting to the same remote host — the session should establish without triggering Error 60.
  • If the issue persists, try connecting from a different network adapter (e.g., switch from Wi-Fi to Ethernet) or a different device entirely to isolate whether the problem is adapter-specific or host-side.