You're getting a duplicate name error. Let's fix it.
You boot up your Windows PC, check the network, and there it is: STATUS_DUPLICATE_NAME (0XC00000BD). Your machine can't talk to other computers, or maybe file shares just stopped working. The fix is stupidly simple once you know it: your computer name collides with another machine on the network. I've seen this happen when someone clones a hard drive, copies a VM, or just buys a pre-built PC with a generic name like DESKTOP-ABC123 that matches someone else's.
The real fix: change your computer name
- Press Windows key + R, type
sysdm.cpl, and hit Enter. You'll see the System Properties window pop up. - Click the Computer Name tab (it's the first one). You'll see your current computer name listed under Full computer name.
- Click the Change... button. A new window opens called Computer Name/Domain Changes.
- In the Computer name field, type a new name. Make it unique. I use a naming scheme like DESKTOP-JOHN-01 or WORK-LAPTOP-SALES. Don't use spaces or special characters – just letters, numbers, and hyphens. Keep it under 15 characters if you can.
- Click OK. Windows will tell you "Welcome to the new computer name" or something similar. Then it asks if you want to restart now. Choose Restart Now.
- After the reboot, your network should work again. Try accessing a shared folder or pinging another PC – the duplicate name error is gone.
What you should see after each step
- After step 2: The current name is displayed. Write it down if you think you might need it later.
- After step 4: The field updates with your new name. No error messages appear here.
- After step 5: A pop-up says "You must restart your computer to apply these changes." Click OK first, then the restart prompt appears.
Why this works
Every Windows machine on a network broadcasts its name using something called NetBIOS (or sometimes mDNS for newer setups). When two machines have the same name, the network gets confused – it doesn't know which one to talk to. Windows then throws the 0XC00000BD error and blocks that machine from communicating to avoid chaos. By giving your PC a unique name, you're removing the collision. The network can now route traffic correctly.
I've seen this happen most often in these scenarios:
- You cloned a hard drive from one PC to another and both booted at the same time.
- You set up a VM from a template that had the same name as the host.
- A friend gave you their old laptop and you plugged it into your network without renaming it.
- Some cheap pre-built PCs ship with names like DESKTOP-ABC that other people's machines also have.
Less common variations of the same issue
Workgroup name conflict
Sometimes the error isn't about the computer name itself but the workgroup name. If two PCs have the same computer name but different workgroups, you can still get a duplicate name error. To check this, go back to sysdm.cpl, click Change..., and look at the Workgroup field. Make sure all machines you want to share with are in the same workgroup (default is WORKGROUP). If you change the workgroup, you need to reboot again.
Hidden duplicate from a disconnected network drive
I've seen a weirder one: a mapped network drive that's disconnected but still cached. Windows might think a duplicate name exists if the drive's target was a machine that's now offline. The fix here is to open File Explorer, right-click any mapped drives, and choose Disconnect. Then restart your PC. This clears the cached name.
NetBIOS over TCP/IP disabled
If renaming doesn't work, check if NetBIOS is enabled. Open Control Panel > Network and Sharing Center > Change adapter settings. Right-click your active network adapter (like Ethernet or Wi-Fi), choose Properties, then double-click Internet Protocol Version 4 (TCP/IPv4). Click the Advanced button, go to the WINS tab, and make sure Enable NetBIOS over TCP/IP is selected. Click OK all the way out and reboot. Some network configurations disable this, and it can cause duplicate name detection to fail – or falsely trigger – depending on your router.
How to prevent this from happening again
You can stop this before it starts. Here's what I tell the technicians I train:
- Name your PC right away. When you set up a new PC, change the name from the generic one Windows gives you. You'll avoid collisions later.
- Keep a list of names in your network. If you manage more than 3 PCs, write down each name. Use a spreadsheet or a note on your phone. When you add a new machine, check the list first.
- Don't clone drives without renaming. If you clone a hard drive or create a VM from a template, always change the computer name before connecting it to the network. I've seen IT departments brick entire office networks by forgetting this.
- Use a naming convention. Something like LOCATION-PERSON-DEVICETYPE (e.g., NYC-JOHN-LAPTOP). This makes it obvious if a duplicate might sneak in.
That's it. Five minutes of work, and the error is dead. You won't see 0XC00000BD again unless you plug in another machine with the same name – so name everything once and move on.