Yeah, that error's annoying. Your machine boots up, joins the network, and then boom — Windows tells you someone else already claimed that name. Let's kill it fast.
The real fix: rename your PC
- Open Settings → System → About (on Windows 10/11).
- Click Rename this PC (or Rename PC — Microsoft moves it sometimes).
- Type a new name. Don't get cute — use something unique like
DESKTOP-7X3KorOFFICE-PC2. Keep it under 15 characters, no spaces, no hyphens. Old NetBIOS can't handle long names. - Click Next → Restart now. Done.
If you're on a domain, you'll need domain admin creds to rename. Workgroup? No problem — rename freely.
Why this works
What's actually happening here is that Windows uses NetBIOS over TCP/IP to broadcast its machine name on the network. When another device — could be another PC, a printer, or even a Raspberry Pi — has the same name, the NetBIOS name service throws error 0X000008F9 (NERR_DuplicateName). Windows is basically saying, "I can't resolve a unique name for myself, so I'm not going to work properly." Renaming gives you a fresh, collision-free identity.
The reason step 2 works is that the rename triggers a full restart of the NetBIOS name table. No cached garbage left behind.
Less common variations
1. NetBIOS over TCP/IP disabled
If you renamed and still see the error, check whether NetBIOS is on. Go to Control Panel → Network and Sharing Center → Change adapter settings → right-click your adapter → Properties → Internet Protocol Version 4 (TCP/IPv4) → Properties → Advanced → WINS tab. Make sure Enable NetBIOS over TCP/IP is selected. If it's disabled, Windows can't even register the name — but the error can still pop up from other services.
2. Two adapters with the same name
Rare, but I've seen it: a laptop with both Wi-Fi and Ethernet trying to register the same machine name twice. Disable one adapter in Network Connections (right-click → Disable) and see if the error vanishes. If it does, your network stack is confused. Reboot with only one enabled, then re-enable the other after a clean boot.
3. Static IP with duplicate hostname in DNS
If you're in a corporate environment with DNS, the error can actually come from a stale A record. Your PC's name is in DNS, but someone else grabbed it first. Ask IT to delete the old record, or use a different name. You can check with nslookup yourpcname in a command prompt — if it returns a different IP than yours, you've got a DNS collision.
4. Third-party software that registers NetBIOS names
Old versions of VMware or VirtualBox sometimes register a virtual machine name on the host's network. If you renamed the host and still see the error, Disable the virtual network adapters in Device Manager (View → Show hidden devices → Network adapters → right-click the VM ones → Disable device). No need to uninstall the whole hypervisor.
Prevention
Don't name two PCs the same thing. Sounds obvious, but I've walked into offices where every Dell Latitude was called Dell-Latitude because IT cloned images without renaming. If you manage a fleet, use a naming convention with a serial number suffix — OFFICE-1A3B, OFFICE-4C2D. For home users, just pick something random. My home server is called FRIDGE — nobody else is naming theirs that.
Also, if you use DHCP reservations, assign a unique hostname per MAC address. Some routers let you override the device name — don't. Let Windows tell the router what it's called.
One more thing: if you ever run nbtstat -n from a command prompt and see CONFLICT in the status column, you're about to hit this error. Reboot or rename immediately.