How to fix Error 52 on Windows 11

by

Why This Error Happens

Error 52 occurs when Windows detects that another device on the network is already using the same computer name or NetBIOS identifier. This commonly happens after cloning a Windows 11 image/VM without changing the default hostname, or when DHCP/DNS caches retain stale records pointing to a duplicate name. It can also surface when a previously joined machine was removed improperly, leaving orphaned name registrations in the domain controller or network switch’s ARP/NetBIOS tables.

Step-by-Step Resolution Guide

  1. Check and change the computer name:
  • Go to Settings > System > About > Rename this PC (or Control Panel > System > Advanced system settings > Computer Name tab).
  • Click Change, enter a unique name, and restart the PC.
  1. Verify no duplicate exists on the network:
  • Open Command Prompt as Administrator and run:

    nbtstat -A <IP_address_of_conflicting_device>
  • Check if another live device is broadcasting the same name; if so, rename one of them.
  1. Flush DNS and NetBIOS cache:
  • In an elevated Command Prompt, run:

    ipconfig /flushdns
    ipconfig /release
    ipconfig /renew
    nbtstat -R
    nbtstat -RR
  • This clears stale name resolution entries that may be causing the false duplicate detection.
  1. Remove stale computer object from Active Directory (if domain-joined):
  • Open Active Directory Users and Computers on the domain controller.
  • Locate the old/duplicate computer object under the relevant OU and delete it.
  • Rejoin the PC to the domain afterward.
  1. Restart the network switch/router DHCP lease table (if applicable):
  • Reboot the router/switch or manually clear the DHCP lease for the conflicting IP/hostname to force fresh registration.

Alternative or Verification Steps

  • After renaming and rebooting, attempt to join the domain or workgroup again — if successful without the Error 52 prompt, the issue is resolved.
  • If the problem persists, temporarily disconnect the PC from the network, rename it locally, then reconnect and rejoin the domain/workgroup to avoid transient name broadcast conflicts.