Fix "Computer Name Already Exists" Error 0X00000860 on Windows

When You See This Error

You're sitting at a Windows 10 or 11 machine — maybe a laptop that was just reimaged, or a desktop that's been off the domain for a while. You type in the domain credentials, click OK, and then boom: “The computer name already exists on the network.” Error code 0X00000860 (or NERR_DupNameReboot in older speak). The join fails, and you’re stuck.

The most common trigger? You rebuilt or renamed a computer that already had an Active Directory computer account. That old account is still sitting in AD, and Windows sees it as a name collision. This also happens when you try to join a machine with the same name as another computer that's currently online (or just hasn't been cleaned up).

Root Cause (Plain English)

Active Directory keeps a list of every computer that's ever joined the domain — even if that computer is broken, dead, or sitting in a closet. Each computer account has a unique Security Identifier (SID), and the network uses that SID to authenticate. When you try to join a new machine with the exact same name, Windows detects the existing account and says, “Nope, that name is taken.”

It’s not a network conflict in the TCP/IP sense (no IP collision). It’s an AD object conflict. The fix is to either delete the old computer object from AD or rename your machine to something unique.

Fix It in 3 Steps

Step 1: Delete the Old Computer Account from Active Directory

This is usually the cleanest fix. You'll need domain admin rights (or at least delegated permissions to delete computer objects).

1. On a domain controller or a machine with RSAT installed, open Active Directory Users and Computers (dsa.msc).
2. Find the computer object with the same name as your current machine. It's usually under the Computers container, or maybe in an OU where the old machine lived.
3. Right-click the computer object, select Delete. Confirm the deletion.
4. Wait a few minutes for replication to finish (or force replication with repadmin /syncall if you're impatient like me).

Step 2: Rejoin the Domain

Now that the old account is gone, the domain will let you create a new one.

1. On the client machine, open Settings > Accounts > Access work or school.
2. Click Disconnect if it shows any existing connections. Reboot.
3. Go back to Access work or school > Connect.
4. Choose Join this device to a local Active Directory domain.
5. Enter the domain name and credentials. Should work now.

Step 3: If You Can't Delete the Old Account (No Permissions)

Maybe your admin won't delete the old account because it belongs to a different team. Fine. Workaround: rename your current computer to something new.

1. On the client, go to Settings > System > About > Rename this PC.
2. Pick a name that doesn't exist on the domain. Something like DESKTOP-ABC123 is safe — but better to follow your org's naming convention.
3. Reboot. Then try the domain join again.
4. After it joins, you can rename it back to the original name if you want — but only after the old AD account is cleaned up.

What to Check If It Still Fails

If you've done all that and the error still shows up, something else is going on. Check these:

• DNS is stale. Old DNS records can cause a false positive. On the client, run ipconfig /flushdns and ipconfig /registerdns. On the DNS server, delete any A or PTR records for the old name.
• The old computer is still powered on. If the original machine is still on the network with that name, you can't join a second one. Turn it off or disconnect it.
• Replication lag. In a multi-DC environment, the DC you're authenticating against might not have the deletion yet. Wait 15 minutes or use repadmin /syncall to force it.
• Do you see the error after a reboot? That's a different beast — it usually means the computer account got corrupted or the secure channel is broken. In that case, completely disjoin the domain and rejoin fresh.

I know this error is infuriating because it's so easy to trigger and the error message isn't exactly helpful. But once you realize it's just a leftover AD object, the fix is straightforward. Delete the old account, or rename the machine. That's it.