Fix STATUS_NDIS_CLOSING 0xC0230002 on Windows

When does this error show up?

You'll typically see STATUS_NDIS_CLOSING (0xC0230002) in a system log or a program's debug output right after you've disconnected a VPN, unplugged an Ethernet cable, or disabled a network adapter. Let's say you're running a network monitoring tool like Wireshark or a custom service that hooks into NDIS—the Network Driver Interface Specification. The program tries to bind to a network interface that's already in the middle of closing down. Maybe you switched from a wired connection to Wi-Fi, or your VPN client just dropped. That's when this error lands.

What's actually causing it?

Under the hood, the NDIS layer in Windows manages all network bindings between protocols (like TCP/IP) and adapters (physical or virtual). When an interface starts closing—because the adapter is disabled, removed, or reset—it sets a flag internally to tell new bindings to back off. The error code 0xC0230002 literally means "the binding attempt was refused because the interface is closing." That's it. The real trigger is almost always a timing issue: something tries to bind at the exact wrong moment.

Now, the common culprits are third-party NDIS drivers—especially from VPN software like NordVPN, ExpressVPN, or Cisco AnyConnect. They install virtual adapters that can be flaky during transitions. Also, outdated or corrupted physical NIC drivers from Realtek, Intel, or Broadcom can cause the interface to toggle on and off without your knowledge.

The fix: step by step

Step 1: Identify the offender

Open Event Viewer (press Win + R, type eventvwr.msc, hit Enter). Go to Windows Logs > System. Filter for the source NDIS or netvsc. Look for an event with ID 0xC0230002 or any related error right before your program failed. That event should list the adapter name. Write it down.

Step 2: Reset the NDIS bindings stack

Open Command Prompt as Administrator. Run this command:

netsh int ip reset

You'll see a message that it's resetting the TCP/IP stack. This clears out corrupted binding states. Wait for it to finish—takes about 10 seconds. Then run:

netsh winsock reset

After running both, you should see "You must restart the computer in order to complete the reset." Do that restart now.

Step 3: Disable and re-enable the problematic adapter

After reboot, go to Control Panel > Network and Sharing Center > Change adapter settings. Find the adapter from Step 1 (or the one giving you trouble—likely your VPN virtual adapter). Right-click it and select Disable. Wait 10 seconds. Right-click again and select Enable. This forces the interface to go through a clean open-close cycle, resetting its internal state.

Step 4: Update the NDIS driver

Open Device Manager (right-click Start > Device Manager). Expand Network adapters. Find the adapter that caused the error (again, check its name). Right-click it and choose Update driver > Search automatically for drivers. If Windows doesn't find anything, go to the manufacturer's website—for Realtek, Intel, or your VPN vendor—and grab the latest driver manually. Install it.

If the adapter is virtual (VPN), uninstall it from Device Manager (right-click > Uninstall device), then reinstall the VPN software fresh. That clears any leftover NDIS binding artifacts.

Step 5: Check for adapter power management issues

Windows sometimes turns off network adapters to save power, which triggers that closing state. In Device Manager, right-click the adapter, go to Properties > Power Management. Uncheck "Allow the computer to turn off this device to save power." Click OK. This alone fixed it for a user on a Dell Latitude with a Realtek NIC who saw the error every time the laptop went to sleep.

Still failing? Here's the deeper check

If the error keeps coming back, you've got a driver incompatibility or a broken NDIS filter driver. Third-party software like antivirus suites (think McAfee, Norton, or even some firewalls) install NDIS light-weight filters. They can cause the interface to close mid-bind. Temporarily disable or uninstall any non-Microsoft filtering drivers by going to Control Panel > Network and Sharing Center > Change adapter settings, right-click your active adapter, select Properties, and uncheck any entries you don't recognize (like "AVG Network Filter" or "McAfee NDIS Filter"). Reboot and test.

If that doesn't do it, run a network stack reset from PowerShell (as admin):

Get-NetAdapter | Restart-NetAdapter

This command restarts all adapters cleanly, which can force any stuck closing state to complete and free up the binding slot.

One last thing: if you're using older VPN software that hasn't been updated in a year, that's your problem. Uninstall it completely, run the vendor's cleanup tool if they have one, and reinstall the latest version. Those old NDIS drivers were written for Windows 7 and don't handle modern power state transitions right.