How to fix Error 54 on Windows 11

by

Troubleshooting Guide: Error 54 – “The Network Is Busy” on Windows 11

Why This Error Happens

Error 54 typically occurs when a network resource (such as a shared drive, printer, or remote server) is temporarily overloaded, unreachable, or when the SMB (Server Message Block) protocol encounters a conflict during file or resource sharing. This can result from network congestion, an unstable NIC (Network Interface Card) driver, corrupted network stack components, or a misconfigured firewall blocking retries. In some cases, outdated SMB versions (like SMBv1) or timeout mismatches between client and server also trigger this error.

Step-by-Step Resolution Guide

  1. Reset the TCP/IP Stack and Winsock Catalog
    Open Command Prompt as Administrator and run:
   netsh int ip reset
   netsh winsock 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 active adapter, select Update driver. If the issue persists, choose Uninstall device, then restart Windows to let it reinstall the driver automatically.

  2. Enable SMB 2.0/3.0 and Disable SMBv1 (if legacy compatibility isn’t needed)
    Open Control Panel > Programs > Turn Windows features on or off, uncheck SMB 1.0/CIFS File Sharing Support, and ensure SMB Direct is enabled if using compatible hardware.

  3. Adjust Network Timeout Settings via Registry
    Open regedit, navigate to:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters
    Add/modify a DWORD value named SessTimeout and set it to 60 (decimal) to allow more time before a busy response is triggered.

  4. Check Firewall and Antivirus Rules
    Navigate to Windows Security > Firewall & network protection > Advanced settings, and ensure no rules are blocking outbound/inbound traffic on ports 445 (SMB) or 139 (NetBIOS).

Alternative or Verification Steps

  • Verify the Fix: Try accessing the network resource again (shared folder, printer, or drive). Run ping <server-IP> and net use \\server\share in Command Prompt to confirm stable connectivity without delays.
  • Alternative Fix: If the error persists, try connecting via a different network (e.g., mobile hotspot) to isolate whether the issue is local network congestion or a server-side problem.