You're in the middle of a video call or a big download, and suddenly the network drops. You check the adapter, and there it is: STATUS_NDIS_MEDIA_DISCONNECTED (0XC023001F). This usually happens right after waking your PC from sleep, or when the ethernet cable gets yanked out of the port—even for a split second. The error means the network interface is physically not connected, according to Windows.
Why Does This Happen?
NDIS (Network Driver Interface Specification) is how Windows talks to your network card. When the card reports "no link," Windows throws this code. But here's the kicker: sometimes the cable is plugged in fine, and the router is blinking. The problem is often a driver or power management setting that makes the adapter go to sleep and never properly wake up.
I've seen this most often on Dell and Lenovo laptops running Windows 10 21H2 or Windows 11 22H2, especially after a BIOS update. The driver gets confused and the link state gets stuck.
The Fix: Step-by-Step
- Check the physical connection. Yes, I know it sounds basic, but unplug the ethernet cable and plug it back in. If you're on Wi-Fi, toggle the Wi-Fi switch off and on (some laptops have a physical switch or Fn key combo). Also, try a different cable if you have one—I've seen dying cables cause this exact error.
- Restart the adapter. Press
Win + Xand select Device Manager. Expand Network adapters, right-click your adapter (e.g., Intel I219-V or Realtek PCIe GbE), and choose Disable device. Wait 10 seconds, then right-click and Enable device. This forces the NDIS stack to reinitialize. - Reset the network stack. Open Command Prompt as Administrator (search "cmd", right-click, "Run as administrator") and run these commands in order:
netsh winsock reset
netsh int ip reset
ipconfig /release
ipconfig /renewThen reboot. This clears any corrupted Winsock entries that might be interfering with the link detection.
Kill the Power Saving Settings
This is the real culprit more often than not. In Device Manager, right-click your adapter, go to Power Management, and uncheck the box that says "Allow the computer to turn off this device to save power." Do the same under the Advanced tab—look for "Energy Efficient Ethernet" and set it to Disabled. This stops the adapter from dropping the link when your CPU idles.
Update or Roll Back the Driver
If the steps above didn't stick, the driver is likely buggy. Go to your adapter's manufacturer website (Intel, Realtek, etc.) and grab the latest driver. If you recently updated and this started happening, roll back: Device Manager → adapter → Driver tab → Roll Back Driver. On my own machine, rolling back the Realtek driver from 2024 to the 2022 version fixed a recurring 0XC023001F.
Still Broken? Check These
- BIOS settings. Some systems have a "Wake on LAN" or "Deep Sleep" option that kills the NIC entirely. Boot into BIOS (F2/Del during startup) and disable any power-saving options for the network card.
- Router ports. Try a different port on your router. I've had a router where one specific port stopped negotiating the link after a power surge—the cable was fine, but the port was dead.
- Static IP vs DHCP. If you're on a static IP, make sure the subnet mask and gateway are correct. A misconfigured static IP can cause the OS to report a media disconnect even though the link is up.
If none of that works, you might be looking at a hardware issue. Run a live Linux USB to see if the adapter works there. If it does, it's a Windows-side problem you can nuke with a clean OS reinstall. If it doesn't, it's time for a USB ethernet adapter—they're cheap and they work.
I know this error is infuriating because it makes your machine look like the problem when it's often just a dumb power setting. But start with the adapter restart and the power management tweak—that fixes the majority of cases. Good luck.