How to fix Error 1204 on Windows 11

by

Why This Error Happens

Error 1204 typically occurs when Windows attempts to map or authenticate a network drive using a provider name that no longer matches an entry in the registry’s NetworkProvider\Order key. This is often caused by corrupted or leftover registry entries from previously installed VPN clients, antivirus software, or third-party network redirectors that were improperly uninstalled. It can also happen if the ProviderOrder string contains a reference to a provider (like “LanmanWorkstation” or a custom VPN provider) that is missing, disabled, or has a corrupted DLL path.

Step-by-Step Resolution Guide

  1. Check the Network Provider Order in the Registry
    Press Win + R, type regedit, and navigate to:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\Order
    Look at the ProviderOrder value. Note any provider names listed that seem unfamiliar or belong to uninstalled software (e.g., a VPN client no longer installed).

  2. Remove Invalid or Orphaned Provider Entries
    Cross-reference each provider listed in ProviderOrder with its corresponding subkey under:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services
    If a provider name in the list doesn’t have a matching service key (or the key exists but the NetworkProvider\ProviderPath DLL is missing), remove that name from the ProviderOrder string (edit as a comma-separated list, don’t delete the whole value).

  3. Restore Default Provider Order (If Corruption Is Extensive)
    If multiple entries are broken, reset ProviderOrder to the Windows default:
    LanmanWorkstation,RDPNP,webclient
    Restart the machine after making this change for it to take effect.

  4. Uninstall Problematic Third-Party Software
    Go to Settings > Apps > Installed Apps and remove any VPN clients, network shaping tools, or antivirus suites installed/updated recently. Reboot, then reinstall the latest version from the vendor if needed — this often re-registers the provider correctly.

  5. Run System File Checker and DISM
    Open Command Prompt as Administrator and run:

   sfc /scannow
   DISM /Online /Cleanup-Image /RestoreHealth

This repairs corrupted system files that manage network provider DLLs (like ntlanman.dll or rdpnp.dll).

Alternative or Verification Steps

  • After making changes, try remapping the network drive again via File Explorer > This PC > Map Network Drive to confirm the error no longer appears.
  • If the issue persists, boot into Safe Mode with Networking and check if the error still occurs — this helps isolate whether a startup service/driver is reintroducing a bad provider entry.