Fix IP Address Conflict 0xC0000254 on Windows 10/11

That IP conflict error is a pain—let's kill it

I know seeing 0xC0000254 pop up right when you're trying to get online is maddening. But it's almost always a quick fix. Nine times out of ten, your PC grabbed the same IP as another device (maybe a phone, a printer, or a roommate's laptop). Here's the step-by-step to squash it.

First, release and renew your IP lease

This is the fastest fix for 99% of users. Open Command Prompt as admin—hit Win+R, type cmd, then right-click and pick Run as administrator. Then run these two commands in order:

ipconfig /release
ipconfig /renew

The /release drops your current IP. The /renew asks your router to hand out a fresh one. It usually works within seconds. If you get an error on /renew (like "An error occurred while renewing"), your DHCP server might be down—skip to the static IP method below.

Why it works: Your router's DHCP service assigns unique IPs, but sometimes two devices end up with the same one because of stale lease data or a misconfiguration. Releasing and renewing forces your PC to get a new address from the pool, avoiding the conflict.

If that doesn't work, set a static IP

Sometimes your router is just stubborn and keeps giving you the same conflicting address. This happens a lot on older routers (like Netgear WNR2000 or Linksys WRT54G models) or in dorm networks. Here's how to override it.

1. Open Control Panel → Network and Sharing Center → Change adapter settings.
2. Right-click your active connection (Wi-Fi or Ethernet) → Properties.
3. Double-click Internet Protocol Version 4 (TCP/IPv4).
4. Select Use the following IP address and fill in:
   — IP address: pick something like 192.168.1.50 (make sure it's not already in use—try pinging it first)
   — Subnet mask: usually 255.255.255.0
   — Default gateway: your router's address, typically 192.168.1.1 or 192.168.0.1
5. For DNS, use 8.8.8.8 and 8.8.4.4 (Google's—they're fast and reliable).
6. Click OK, then OK again, and restart your connection (disable and re-enable the adapter).

I've seen this fix work on everything from a Dell Latitude 7480 to a Surface Pro 9. Just be sure your static IP isn't in the router's DHCP range—otherwise you'll still get conflicts.

Why it works: By setting a static IP, you bypass DHCP entirely. Your PC keeps that address forever, so no other device can grab it unless there's a duplicate static assignment somewhere else.

Less common cause: duplicate MAC address conflicts

Rare but real—especially on networks with cheap switches or managed Wi-Fi setups. Some NICs from Realtek (like the RTL8168) have buggy firmware that reports the same MAC address as another device. This triggers the same 0xC0000254 error even though the IPs are different. If you've tried everything above and still see the error, check your MAC address:

ipconfig /all

Look for Physical Address. If it looks identical to another device on your network (ask your IT guy or check your router's client list), you'll need to update your NIC driver or, worst case, swap the network card. I've also seen this on virtual machines—if you're running Hyper-V or VMware, the virtual switch can clone MACs. Disable any virtual adapters you don't need in Network Connections.

Prevention: keep it from coming back

Once you've fixed it, you don't want to see 0xC0000254 again. Here's how:

• Limit DHCP lease time on your router to 24 hours or less. That way, stale leases clear out faster—most routers let you set this under LAN settings.
• Reserve IPs for static devices like printers or NAS. On your router, use DHCP reservation (bind MAC address to a specific IP). This keeps them from grabbing random addresses.
• Update your router firmware—I've seen TP-Link Archer C7 and Asus RT-AC68U units fix IP conflict bugs after a firmware update.
• Skip using multiple DHCP servers on the same network. If you have a second router acting as a switch, make sure its DHCP server is turned OFF.

One last thing: if you're on a corporate network or a college dorm, you might not be able to change DHCP settings. In that case, just use the static IP workaround above and hope the network admin doesn't mind.

That's it—get your IP sorted and get back to work. If you're still stuck, try restarting your router (unplug power for 30 seconds), which often clears out the lease table entirely.