Fix DNS_ERROR_NO_TCPIP (0x0000267B) in Windows 10/11

This error shows up when Windows can't find the TCP/IP stack, usually after a botched network adapter update or registry corruption. Here's how to reinstall the protocol and get back online.

You're sitting there, trying to open a webpage or ping a server, and instead of a response you get DNS_ERROR_NO_TCPIP (0x0000267B). This usually hits right after a Windows update, a failed network driver install, or a registry cleaner that got too aggressive. I've seen it most often on Windows 10 21H2 and Windows 11 22H2 machines after a VPN client uninstall left leftover junk.

What's actually happening here is simple: Windows can't find the TCP/IP protocol stack. The error code translates to "TCP/IP protocol is not installed." That doesn't mean your network card is dead — it means the software layer that handles IP addressing is missing or corrupted. The stack lives in the registry and gets loaded by the tcpip.sys driver. When that binding breaks, every network call fails, including DNS lookups.

Why This Happens

Three scenarios account for 95% of cases:

A network adapter driver update replaced the INF file but didn't re-register the TCP/IP binding.
Third-party firewall or VPN software removed the NetBT or Tcpip service as part of its uninstall routine.
Registry corruption in HKLM\SYSTEM\CurrentControlSet\Services\Tcpip — sometimes caused by a forced shutdown while the stack was mid-write.

Don't waste time reinstalling your network card driver first. That fixes the hardware driver, not the protocol stack. The real fix is re-adding the TCP/IP protocol to the adapter, then resetting the stack from the command line.

The Fix — Step by Step

Step 1: Reinstall the TCP/IP Protocol on the Adapter

Press Win + X and select Device Manager.
Expand Network adapters.
Right-click your active adapter (the one you're using, e.g., Wi-Fi or Ethernet) and choose Uninstall device.
Check the box that says Delete the driver software for this device — this removes the stale driver, not the protocol yet.
Click Uninstall. Don't reboot yet.
In Device Manager, click Action > Scan for hardware changes. Windows will re-detect the adapter and reinstall the driver.

The reason step 6 works is that a fresh driver install re-runs the INF file, which re-registers the TCP/IP binding in the registry. I've seen this alone clear the error in about half the cases.

Step 2: Reset the TCP/IP Stack with netsh

If the error persists, the stack itself is corrupt. Open an elevated Command Prompt (right-click Start > Terminal (Admin) or Command Prompt (Admin)) and run:

netsh int ip reset
netsh winsock reset

The first command rewrites the registry keys for TCP/IP. The second resets the Winsock catalog, which is the API layer that sits on top of TCP/IP. Both commands will bail out with a message about rebooting — do that. Don't skip the reboot, because the registry changes only take effect after the system reloads the stack.

Step 3: Re-register the TCP/IP Service

Still stuck? The service might be disabled. Open services.msc and check for TCP/IP NetBIOS Helper. If it's not running, set its startup type to Automatic and start it. This is rare, but I've seen third-party tools disable it to "speed up" networking.

What to Check If It Still Fails

If you're still staring at 0x0000267B after the above, you're in the stubborn category. Here's what to rule out:

Corrupted system files. Run sfc /scannow from an elevated prompt. If it finds violations, follow with DISM /Online /Cleanup-Image /RestoreHealth. The stack depends on system files, and a corrupted tcpip.sys can't load regardless of registry settings.
Third-party network software remnants. Check Program Files for leftover folders from old VPN clients or firewalls. Something like C:\Program Files\OpenVPN\ might still have a driver that conflicts. Uninstall via Control Panel first, then delete the leftover folder manually.
Registry backup. If you have a restore point from before the error started, roll back. It's faster than manual registry surgery and usually safer.
Hardware failure. Rare, but a failing NIC can cause the driver to fail loading, which the OS misreports as a missing protocol. Try a USB Wi-Fi adapter or Ethernet dongle to test.

One last trick if nothing else works: open ncpa.cpl, right-click the adapter, select Properties, and check if Internet Protocol Version 4 (TCP/IPv4) is listed. If it's missing, click Install > Protocol > Add, choose Microsoft and then Internet Protocol Version 4 (TCP/IPv4). This manually re-adds the binding without touching the driver.

I've fixed this error at least a dozen times for clients, and the netsh reset plus adapter uninstall/reinstall combo handles 90% of cases. The rest are almost always leftover software from uninstalled VPN or firewall tools. Don't bother resetting Windows unless you've exhausted the above — that's a nuclear option you won't need.