Skip to content

What Is the TAP-Windows Adapter? (And When You Don't Need It)

If you’ve ever installed OpenVPN on Windows, there’s an extra network adapter sitting in your Device Manager called TAP-Windows Adapter V9. It isn’t malware, it isn’t a leftover you should delete on sight, and it isn’t unique to any one VPN brand. Here’s what it actually is.

The short version

TAP-Windows is a virtual network adapter. Windows can’t just hand a program raw network traffic, so OpenVPN installs a fake network card, your system routes traffic into it as if it were real hardware, and OpenVPN picks the traffic up from there, encrypts it, and sends it through the tunnel. Every OpenVPN-based VPN on Windows installed one for years, which is why the same adapter shows up whether you used any of a dozen VPN brands.

TAP, TUN, and Wintun

NameWhat it is
TAP-Windows (tap-windows6)The classic virtual adapter driver, bridges at the Ethernet level. What most “TAP driver” errors refer to.
TUN modeThe same idea one layer up (IP packets instead of Ethernet frames). On Windows both modes historically ran through the TAP driver.
WintunA newer, faster virtual adapter created for WireGuard, later adopted by OpenVPN 2.6+ as an alternative to TAP. Fewer driver headaches.

If your VPN setup is modern, there’s a fair chance it already uses Wintun and you’ll never see a TAP error again.

When you actually need TAP

  • You use a manual OpenVPN setup (OpenVPN GUI / older OpenVPN Connect) with .ovpn config files
  • You run an older VPN client built on OpenVPN 2.5 or earlier

That’s the whole list. The adapter installs with the OpenVPN client, one per connection as a rule, and gets used only while the tunnel is up.

When you don’t

Modern VPN apps skip TAP entirely

Protocols like IKEv2 (built into Windows), WireGuard (Wintun) and the Xray family (VLESS Reality, Hysteria2) don’t use the TAP driver at all. The VPNBaron app runs on these, which is why it has no TAP driver to install, corrupt, or troubleshoot.

If your only reason for keeping OpenVPN around is habit, switching to a modern app removes this entire class of problems: no yellow exclamation marks in Device Manager, no “All TAP-Windows adapters are in use”, no driver reinstalls after Windows updates.

Common TAP errors (and where to fix them)

The classics, usually after a Windows feature update or an unclean VPN uninstall:

  • “All TAP-Windows adapters on this system are currently in use”
  • A TAP adapter with a yellow warning icon in Device Manager
  • OpenVPN connecting but no traffic flowing

Step-by-step fixes for all of these live in our dedicated guide: Fix TAP Adapter Issues on Windows.

Is it safe to remove?

If you no longer use any OpenVPN-based client: yes. Uninstall the OpenVPN software and the adapter goes with it (or remove it from Device Manager). If it reappears, some installed program still ships the driver. Removing TAP while an OpenVPN client is still installed will just break that client until it reinstalls the driver.