You rebooted after a Windows update, the Ethernet light is on, the cable's seated, and yet Windows says Unidentified Network and you've got no internet. I know how infuriating that is — especially when you did absolutely nothing wrong. The update did this, not you.
This hits Windows 10 22H2 and Windows 11 23H2/24H2 most often on machines with a Realtek PCIe GbE Family Controller. The pattern is always the same: a driver or network stack change ships in a cumulative update, and the Realtek NIC ends up with an APIPA address (169.254.x.x) because DHCP never completes. Your router is fine. Your cable is fine. Windows is being Windows.
Work through these in order. Stop as soon as you're back online.
Fix 1 — The 30-second fix: disable and re-enable the adapter
Yeah, it sounds dumb. Do it anyway. The update often leaves the adapter in a half-initialized state, and a full down/up cycle clears it.
- Press
Win + R, typencpa.cpl, hit Enter. - Find your Ethernet adapter.
- Right-click → Disable. Wait 5 seconds.
- Right-click → Enable.
Give it 15 seconds. If you see the network name change from "Unidentified Network" to your actual SSID/router name, you're done. If it flips back, move on.
Fix 2 — The 5-minute fix: roll back the Realtek driver
Nine times out of ten this is the real fix. The Windows update pushed a Realtek driver that doesn't play nice with your specific chip revision — usually 10.0.1.xx builds pushed through Windows Update instead of Realtek's own 11.x line.
Win + X→ Device Manager.- Expand Network adapters.
- Right-click Realtek PCIe GbE Family Controller → Properties.
- Go to the Driver tab.
- If Roll Back Driver is clickable, click it. Pick a reason, confirm, and reboot.
If rollback is greyed out (common if this was a clean install or the update wiped the previous driver), grab the driver straight from Realtek's site or your motherboard vendor — ASUS, MSI, Gigabyte, and Dell all host their own Realtek GbE packages. Install that, reboot, and check again.
Skip the "Update driver" button in Device Manager. It'll just re-download the same broken one from Windows Update. Waste of time.
Fix 3 — The 15-minute fix: full network stack reset
If the adapter is fine but Windows still won't hand out an IP, the TCP/IP stack itself got corrupted by the update. This happens a lot on machines that went from 22H2 to 23H2 in one shot. Open Command Prompt as Administrator and run these one at a time:
netsh winsock reset
netsh int ip reset
ipconfig /release
ipconfig /renew
ipconfig /flushdns
netsh int ipv4 reset
netsh int ipv6 resetReboot when you're done. Don't skip the reboot — the winsock reset only applies at startup.
Still nothing? Check whether the adapter is getting an address at all:
ipconfig /allLook at the Ethernet adapter section. If Autoconfiguration IPv4 Address shows something like 169.254.x.x, DHCP is failing. That's a different problem — jump to Fix 4.
Fix 4 — Advanced: DHCP and DNS are being ignored
This one's for the stubborn cases. Windows update sometimes flips the adapter to a static IP or breaks the DHCP client service. Two things to check:
Check the adapter IP settings
- In
ncpa.cpl, right-click the Ethernet adapter → Properties. - Select Internet Protocol Version 4 (TCP/IPv4) → Properties.
- Make sure Obtain an IP address automatically and Obtain DNS server address automatically are both selected.
If they were set to static, that's your culprit. Switch to automatic, click OK, then reboot.
Restart the DHCP and DNS services
Open services.msc and check these three are running and set to Automatic:
- DHCP Client
- DNS Client
- Network Store Interface Service
If any is stopped, start it. If it won't start, right-click → Properties → Dependencies tab and check what it needs.
Nuke it from orbit: uninstall and reinstall the adapter
Last resort before reinstalling Windows. In Device Manager, right-click the Realtek adapter → Uninstall device, and tick Delete the driver software for this device if it's offered. Reboot. Windows will re-detect the NIC and install a fresh driver. If it re-installs the broken one, install the Realtek package from your motherboard vendor before rebooting so Windows picks up the right .inf.
Things that won't help, so don't bother
- Network Reset in Settings — it does a subset of Fix 3 and reboots you. Fine as a shortcut, not a solution.
- Reinstalling Windows before trying Fix 2. The driver rollback solves this ~90% of the time.
- Swapping the cable. If the light's on and Device Manager sees the adapter, the cable is doing its job.
- Disabling IPv6. Old forum advice from 2012. Doesn't apply here.
Real-world triggers to watch for
This specific failure shows up most after Patch Tuesday cumulative updates on 23H2, and after the 22H2 → 23H2 feature update. I've also seen it on Dell OptiPlex 7090s and custom builds with the Realtek RTL8168/8111 chip after KB503xxx updates in early 2024. If your machine matches, go straight to Fix 2 — roll back the driver.
One more thing: if rollback is greyed out and the vendor driver won't stick, set a driver update exclusion via Group Policy (gpedit.msc → Computer Configuration → Administrative Templates → Windows Components → Windows Update → Manage updates offered from Windows Update → Do not include drivers with Windows Updates). That stops Windows from quietly reinstalling the broken one on the next Patch Tuesday.