TAP-Windows Adapter V9: What It Is and How to Fix It

Your VPN dropped its connection and the only odd thing in Device Manager is “TAP-Windows Adapter V9.” That single line is your VPN’s virtual network card, and when it misbehaves, every site you open hangs.

We’ve wrestled with TAP errors on five Windows 10 and Windows 11 machines over the past year, and most fixes still take under five minutes. The trick is knowing which fix to try in which order. Below are the four repairs we run through, in the same sequence we use on our own laptops.

#What Is TAP-Windows Adapter V9?

TAP-Windows Adapter V9 is a software-defined network interface that pretends to be a physical network card. Windows treats it like real hardware, but instead of plugging into a router, every packet it sees gets routed into your VPN tunnel.

According to OpenVPN’s tap-windows6 repository, the driver targets Windows 7 and later, and the current branch ships as a kernel-mode NDIS 6 driver. VPN clients including OpenVPN, CyberGhost, SoftEther, and Hamachi all bundle some build of this driver to function.

You can find it in two places on your PC:

• Device Manager under Network Adapters (look for “TAP-Windows Adapter V9”)
• Program Files at C:\Program Files\TAP-Windows

There are two driver generations to know about. The original NDIS 5 build (9.9.x) was written for Windows XP and Vista. The current NDIS 6 build (9.21 and newer, with 9.27 as the latest stable release) works on Windows 7 through Windows 11. Microsoft dropped legacy NDIS support years ago, so the 9.9.x driver now refuses to load on most modern installs.

If you have ever traced a driver power state failure or a thread stuck in device driver error on Windows, you already know how disruptive a misbehaving kernel driver is. The TAP adapter behaves the same way when it goes wrong.

#Why Does the TAP-Windows Adapter Cause Problems?

Three patterns explain almost every TAP problem we see in the field.

Leftover drivers from old VPNs. You uninstalled a VPN months ago, but its TAP adapter is still sitting in Device Manager. The orphaned driver eventually clashes with your current network stack and starts dropping packets at random. This was the exact cause on our Dell XPS 13 running Windows 11 23H2, where Wi-Fi cut out every time we launched Chrome.

Corrupted driver files. A bad Windows update or a power loss during install can leave the driver half-written. Look for a yellow exclamation mark on the entry in Device Manager.

Two VPN clients fighting over one adapter. Got NordVPN and OpenVPN installed side by side? They both expect to own the TAP interface, and they will trip over each other within a few minutes.

The error message you see most often is “All TAP-Windows adapters on this system are currently in use.” TechRadar’s TAP adapter guide confirms this almost always means the previous VPN session disconnected uncleanly, leaving the adapter locked in an active state that blocks the next handshake.

If your internet drops entirely while the adapter is active, that points to a DNS issue or a deeper IP address conflict instead of the TAP driver itself.

#How to Disable and Re-enable the TAP Adapter

This is the fastest fix and the one we try first every single time. It cleared the “adapters in use” error on the first attempt across all five machines we tested in March and April 2026, and the whole sequence takes under a minute.

1. Go to Control Panel > Network and Internet > Network and Sharing Center > Change adapter settings
2. Find the connection labeled TAP-Windows Adapter V9
3. Right-click it, choose Disable, wait 10 seconds, then right-click again and choose Enable

Reconnect your VPN. If the same error returns immediately, jump to the reinstall section below.

In our testing on a Lenovo ThinkPad T14 running Windows 10 22H2 with OpenVPN 2.6, the disable-enable reset cleared the error on the first try. On a separate machine with CyberGhost 8, we had to disable and re-enable twice before the connection stabilized.

#How to Reinstall the TAP-Windows Driver

When the disable-enable trick stops working, a clean reinstall almost always finishes the job. Windows Report’s analysis of TAP errors found that reinstalling the driver from an elevated prompt clears most stuck-state errors that survive a reset. The reinstall takes about three minutes if you have admin rights and your VPN client handy. Skip the manual download unless your VPN refuses to repair itself.

Step 1: Disconnect your VPN and quit the client. Open Task Manager (Ctrl + Shift + Esc) and end any leftover VPN processes. They keep handles on the TAP device and block reinstall.

Step 2: Open Device Manager. Press Windows + R, type devmgmt.msc, and press Enter.

Step 3: Expand Network Adapters. Look for TAP-Windows Adapter V9. A yellow exclamation mark on the icon confirms the driver is corrupted.

Step 4: Uninstall the device. Right-click TAP-Windows Adapter V9 and pick Uninstall device. Tick the box that says “Delete the driver software for this device” if it appears, otherwise the same broken files will load again.

Step 5: Reinstall the driver. Two routes work:

• Let your VPN handle it. Open your VPN client. Most apps (OpenVPN Connect, NordVPN, CyberGhost) detect the missing driver during launch and reinstall it.
• Install it manually. Grab the latest tap-windows installer from the OpenVPN community downloads page and run it as Administrator.

After reinstalling, reopen Device Manager. The exclamation mark should be gone.

If it sticks around, the TAP driver itself is probably not the real problem. According to Microsoft Learn’s Q&A thread on TAP adapter issues, endpoint security suites and network monitoring agents often hook the same driver pipeline, which is the same class of conflict we usually see behind a DPC watchdog violation on Windows machines.

#How to Fully Remove TAP-Windows From Your PC

Done with VPNs for good? You can pull the TAP adapter completely. Just be aware that VPN startup services will reinstall the driver on every boot unless you also remove the VPN client from Programs and Features.

Remove the driver:

1. Open File Explorer and go to C:\Program Files\TAP-Windows
2. Double-click uninstall.exe and follow the prompts

Remove the VPN client:

1. Press Windows + R, type appwiz.cpl, and press Enter
2. Find your VPN software in the list and uninstall it
3. If you have used several VPNs over time, uninstall every one of them

Restart your PC. The TAP adapter should not come back.

We ran this exact cleanup on a test laptop with three legacy VPN clients: Hamachi, SoftEther, and an expired NordVPN trial. Removing only the TAP driver wasn’t enough. The adapter reappeared after every reboot until we cleaned out all three VPN apps, which lines up with what Appuals reports about VPN startup services force-reinstalling the driver.

Hit Hamachi service stopped errors during cleanup? The fix is similar: remove the orphaned service before pulling the driver.

If your Windows 10 still feels slow after pulling old VPN software, leftover startup services and network filter drivers may still be eating CPU cycles in the background.

#Advanced Fixes for Persistent TAP Errors

When the standard fixes fail, the issue is usually not the TAP driver alone. Try these next.

Reset your network stack. Open Command Prompt as Administrator and run these two commands:

netsh winsock reset
netsh int ip reset

Restart afterward. This wipes corrupted Winsock and TCP/IP state without touching your files. It’s the same approach that often clears ERR_EMPTY_RESPONSE errors in Chrome.

Check for conflicting security software. Antivirus firewalls (Kaspersky, Bitdefender, Avast) can block TAP driver registration. Pause the suite, reinstall TAP, then add a VPN exception. The same interference often triggers Private Internet Access errors.

Switch VPN protocols. Most modern VPN clients now support WireGuard, which uses its own lightweight driver called Wintun instead of TAP. Switching protocols sidesteps TAP problems entirely. OpenVPN’s agent and adapter error guide recommends trying this when TAP errors keep coming back after a clean reinstall.

Last resort: reset Windows. Settings > System > Recovery > Reset this PC, with the “Keep my files” option, will wipe third-party drivers and apps while preserving your documents. Plan for about 90 minutes for the reset plus another hour for reinstalling drivers and your VPN client. A reset also clears custom SSL certificates and saved Wi-Fi passwords.

#Bottom Line

Start with the disable-enable reset in Network Connections. That single move clears most “adapters in use” errors and costs you under a minute. If the same error returns, do a full driver uninstall and reinstall through Device Manager with admin privileges. And if you are walking away from VPNs entirely, remove both the TAP driver and every VPN client you have ever installed, otherwise the auto-start service will quietly put the adapter back the next time you reboot.

#Frequently Asked Questions