Fix STATUS_NDIS_INVALID_DATA Error 0xC0230015

This error means Windows can't talk to your network adapter properly. You'll see it after a driver update or when plugging in a USB Wi-Fi or Ethernet dongle. I'll walk you through three fixes, from quickest to most thorough.

What causes this error, and when does it show up?

You'll usually see STATUS_NDIS_INVALID_DATA (0xC0230015) right after a Windows update or a driver update. It can also pop up when you plug in a new USB network adapter — like a TP-Link or ASUS dongle — and Windows tries to install its driver automatically. The error means the Network Driver Interface Specification (NDIS) layer can't process the data the adapter is sending. It's not a hardware failure 90% of the time. It's a driver mismatch or corruption. Let's fix it.

Fix 1 (30 seconds): Restart and check the adapter

Don't skip this step. I've seen a simple restart clear the error because it resets the NDIS state machine. Here's what to do:

Save your work.
Click the Start button, then the Power icon, and select Restart.
When Windows comes back, check if the error is gone. Open the Device Manager (right-click Start, choose Device Manager). Expand Network adapters. If you see a yellow triangle on your adapter, that's the error. Right-click it and select Properties. Under the General tab, look at Device status. If it says This device is working properly, you're done. If it still shows the error, move to Fix 2.

Fix 2 (5 minutes): Roll back the driver

If the error started after a driver update, rolling back is your best bet. Windows keeps the previous driver version for 10 days after an update. Here's how to use it:

Open Device Manager (right-click Start, choose it).
Expand Network adapters, find your adapter (it might say Realtek, Intel, Qualcomm, or Broadcom). Right-click it, choose Properties.
Go to the Driver tab. If the Roll Back Driver button is grayed out, skip this fix. If it's clickable, click it, then select Yes to confirm. Windows will walk you through the rollback.
After it finishes, restart your computer (don't skip the restart). Check Device Manager again. The error should be gone. If the button was grayed or the error persists, move to Fix 3.

Fix 3 (15+ minutes): Netsh, Winsock, and driver reinstall

This is the thorough fix. It resets the network stack and re-installs the driver from scratch. I recommend using a backup of your driver from the manufacturer's site, because Windows Update sometimes pushes broken versions.

Step 1: Reset Winsock and the network stack

Press Windows Key + X and select Windows Terminal (Admin) or Command Prompt (Admin).
A User Account Control window will pop up. Click Yes.
In the terminal, type this command and press Enter:
```
netsh winsock reset catalog
```
You should see Successfully reset the Winsock Catalog.
Type this next command and press Enter:
```
netsh int ip reset
```
You should see Resetting Compartment Forwarding, OK! and similar lines.
Close the terminal and restart your computer.

Step 2: Uninstall the driver completely

Open Device Manager again, expand Network adapters.
Right-click your adapter and select Uninstall device.
In the confirmation dialog, do check the box that says Attempt to remove the driver for this device. Then click Uninstall.
After it finishes, restart your computer. Windows will try to reinstall the driver automatically.

Step 3: Install the correct driver

Go to your computer manufacturer's support site (Dell, HP, Lenovo, etc.) or the adapter manufacturer's site.
Download the latest driver for your exact model and Windows version (Windows 10 or 11, 64-bit).
Run the installer. If it asks, choose Clean installation or Remove previous drivers.
Restart one more time.

When to call it quits

If the error still shows up after Fix 3, the adapter itself might be dying. Try it in a different computer if you can. If it works there, the issue is your motherboard's network port or a corrupt Windows install. If it doesn't work elsewhere, replace the adapter. They're cheap — a USB Ethernet dongle runs $15 these days.

Pro tip: If you're in a hurry and this is a work machine, you can also try a System Restore point from before the error started. Open System Restore by typing rstrui in the Run box (Windows Key + R). Pick a restore point before the error, follow the wizard, and it'll undo any driver changes.