A Windows IP address conflict usually means two devices on the same local network are trying to use the same address. The result can be an unreliable connection, trouble reaching the router, or a Windows warning that seems to arrive just as you need the internet most.

On a typical home network, the first fix is to inspect the connection with IPConfig, then ask the router for a fresh DHCP configuration. If the conflict returns, the lasting fix may be on another device or in the router’s address settings.

This guide covers IPv4 addresses on Windows 10 and Windows 11. Allow about 15 minutes, although tracking down a second device can take longer.

A laptop shows an IP address conflict, with a diagram illustrating how to assign one device a new address. Before you begin​

Save any online work. Releasing an address temporarily interrupts the affected connection, so avoid doing this during a remote session that depends on it.

If this is a work, school, or other managed network, contact the administrator before changing a static address or router settings. Those settings may be intentional.

You’ll need to be connected to the affected Wi-Fi or Ethernet network and have permission to run Command Prompt as an administrator.

1. Inspect your network settings​

  1. Open Start, type Command Prompt, and select Run as administrator.
  2. Enter:

ipconfig /all

  1. Find the section for the connection you’re using, such as Wireless LAN adapter Wi-Fi or Ethernet adapter Ethernet. Ignore disconnected or virtual adapters for now.
  2. Note these fields:
  • IPv4 Address: The address currently shown for that adapter.
  • DHCP Enabled: Yes means the adapter is configured for automatic IPv4 addressing; No indicates a static configuration.
  • Default Gateway: Usually the router’s local address on a home network.
  • DHCP Server: The server that supplied the address, when applicable.
  • Physical Address: The adapter’s hardware address, useful when identifying it in a router’s device list.

Microsoft documents ipconfig /all as a way to distinguish dynamic from static addressing. IPConfig shows this PC’s configuration; it does not, by itself, identify every other device using an address on the network.

Quick check: If DHCP is enabled, try the renewal below. If it is not, skip to the static-address section before changing anything.

2. Release and renew the DHCP address​

For an adapter with DHCP Enabled: Yes, enter the following commands one at a time, pressing Enter after each:

ipconfig /release

ipconfig /renew

Then inspect the result:

ipconfig /all

Without an adapter name, release and renew apply to all applicable adapters. To target only one, use the exact adapter name shown by ipconfig. For example, if its name is Wi-Fi:

ipconfig /release "Wi-Fi"

ipconfig /renew "Wi-Fi"

Replace Wi-Fi with your actual adapter name if necessary. Microsoft’s command documentation confirms that release and renew can be scoped to an adapter and that renewal applies to automatically configured connections.

A successful renewal should give the active adapter a usable IPv4 configuration, and the conflict warning should stop. The address does not have to change: the DHCP server may offer the same one again. Test the connection by opening a site or accessing a local resource you normally use.

If the warning returns, renewal may have treated the symptom rather than the cause. Check for a device with a manually assigned duplicate address.

3. Check for conflicting static addresses​

A static address is entered manually rather than leased automatically. It can cause a conflict if another device uses the same address—or if the router’s DHCP server is allowed to hand that address to someone else.

On your own network:

  1. Note the IPv4 address involved in the warning or shown in the affected adapter’s settings.
  2. Check the router’s connected-device and DHCP lease lists for that address. The labels vary by router.
  3. Check devices that may have manual settings, such as printers, network storage, cameras, and other PCs. A manually configured device may not appear in the DHCP lease list.
  4. If two devices are configured with the same address, change one using its documented settings. Record existing settings first.

If your Windows PC has a static address but does not need one, you can switch it to DHCP provided the network has a working DHCP server:

  1. Open Settings > Network & internet.
  2. For Wi-Fi, select Wi-Fi > Manage known networks, then choose the relevant network. For Ethernet, select Ethernet and the connected network.
  3. Next to IP assignment, select Edit.
  4. Choose Automatic (DHCP) and save.

The wording and layout can vary between Windows 10 and Windows 11. Microsoft notes that choosing automatic IP settings also sets the DNS server address automatically, so record any custom DNS settings before changing them.

If the device needs a static address, don’t simply guess at a replacement. It needs an unused address appropriate to that network, along with the correct subnet, gateway, and DNS settings.

4. Prevent the conflict from returning​

The router’s DHCP settings determine which addresses it can offer automatically. Microsoft warns that manually assigning an address from that same pool can create a conflict; excluding static addresses from DHCP allocation helps prevent it.

Two common approaches are:

  • DHCP reservation: Configure the DHCP server to give a particular device a consistent address. The device still uses automatic addressing. Router interfaces and reservation rules vary, so follow the router’s instructions.
  • Static address outside the dynamic pool or in an exclusion: Assign the device an appropriate unused address that the DHCP server will not lease to other devices. Keep a record so it is not manually assigned twice.

For example, if a router leases addresses from 192.168.1.100 through 192.168.1.200, a suitable unused address outside that pool could be used for a manually configured device—but only after confirming it is valid for the subnet and not already in use. The example is not a universal setting.

Also check whether an additional router or access point is unintentionally running its own DHCP server on the same network. On managed networks, leave DHCP configuration to the administrator.

If renewal fails or the warning persists​

  • “Media disconnected”: Make sure the correct Wi-Fi network is connected or the Ethernet cable is plugged in. Target the active adapter rather than a disconnected one.
  • An address beginning with 169.254: Windows may have been unable to obtain an address through DHCP. Check the connection and, on a home network, whether the router’s DHCP service is enabled.
  • The same conflict keeps coming back: Check static devices and router leases again. A reservation or corrected DHCP pool may be needed.
  • Other devices are affected too: The router or DHCP service may be involved. Restarting the router can help troubleshoot connectivity, but it temporarily disconnects everyone and won’t correct a persistent duplicate static configuration.
  • A work network still reports conflicts: Give the administrator the adapter name, IPv4 address, DHCP server, and the approximate time of the warning. Avoid posting your network details publicly.

You do not need to flush DNS to fix a duplicate IP address: DNS troubleshooting addresses name resolution, not two devices claiming the same local IPv4 address.

Bottom line: Use IPConfig to confirm whether Windows is using DHCP, renew the affected lease, and then investigate static assignments or DHCP settings if the conflict returns. A clean address plan is less exciting than a mystery outage—and that is precisely the point.