Tap-windows Driver (9.24.2) Download [UPD]
Rochell Estrello
If you need to run OpenVPN on Windows Vista/7 64-bit you have to use signed TAP drivers. Unless you sign them yourself, you need to extract drivers from an existing OpenVPN installer. See below for instructions.
Occasionally you may need play with different TAP-driver versions. In this case you can use devcon.exe from the Windows command-prompt. Below are some common commands you can run from an administrator Powershell or cmd.exe console:
Basically what happens when you install the TAP-Windows driver is that you get a new network adapter that shows up in your network control panel. You right click on the TAP adapter and set the TCP/IP properties, i.e. IP address and netmask. Then you rename the TAP adapter icon to something like "my-tap" and reference it using the --dev-node option in OpenVPN.
People occasionally report tap-windows installation issues, assuming they are all caused by a single bug, because devcon.exe gives the same error message/code. This is unfortunately not the case, and the reason for a install failure could be:
If you're still having issues installing the tap-windows driver, you should try installing it on another computer. If installation to another computer works, it's highly likely the problem is in your system, not in the OpenVPN/tap-windows installer itself.
You can further debug tap-windows installation issues by looking at the common log file for all Windows driver installations, which on Windows 7 is normally located in C:\Windows\inf\setupapi.dev.log. If you're filing a bug report, you should attach the logs for the tap-windows installation part to the bug report.
This post talks about TAP-Windows Adapter v9, what they are, why VPNs require them, and where you can download the TAP Drivers. We will also show you how to install, update or uninstall the TAP driver.If you open the Windows Settings, you will see a program called TAP-Windows installed.Windows 11/10/8/7/Vista users will see it in the Control Panel.If your open Devices Manager and expand Adapters, you will also see it there.
Most VPN software install a particular network driver called Tap Windows. The adapter typically appears in Device Manager after the installation of a VPN client and is used by most VPN suites as an alias for connecting to the Internet privately.
Are you unable to establish a connection with your VPN? Then, you must troubleshoot by checking if the Tap Windows Adapter V9 is installed properly. If you identify any signs of a corrupted driver, follow the guide below to reinstall the Windows Tap Adapter:
5. Now, check if you can find out Tap-Windows Adapter V9. If you see one, reinstalling the driver will often remedy the issue. So, right-click the driver and choose Uninstall device.
Why does this happen, you may wonder? Because some VPN programs check for missing drivers and install them automatically. If you want to remove the Tap Windows driver, check out this simple guide below:
If you use a VPN frequently, you may have encountered the Tap Windows Adapter v9.21.2. This adapter serves as a network driver and is required by VPN services to establish connections to servers. It is an essential component for most VPN clients. However, if you use a VPN through a browser extension, you will not need to install this adapter.
Note: If the VPN client you use only gives you a missing driver error, but fails to reinstall TAP-Windows Adapter 9.21.2, reinstall the VPN client itself. This will prompt the installer to also install the missing driver.
Alternatively, visit this website and download the appropriate TAP-Windows installer from OpenVPN Technologies based on your operating system.
Important: you will need to use the correct installer for your operating system. The Windows 10 installer works on Windows 10 and Windows Server 2016/2019. The Windows 7 installer will work on Windows 7/8/8.1/Server 2012r2. This is because of Microsoft's driver signing requirements are different for kernel-mode devices drivers, which in our case affects OpenVPN's tap driver (tap-windows6).
Important: you will need to use the correct installer for your operating system. The Windows 10 installer will not work on Windows 7/8/8.1/Server 2012r2. This is because Microsoft's driver signing requirements and tap-windows6. For the same reason you need to use an older installer with Windows Server 2016. This older installer has a local privilege escalation vulnerability issue which we cannot resolve for Windows Server 2016 until tap-windows6 passes the HLK test suite on that platform. In the meanwhile we recommend Windows Server 2016 users to avoid installing OpenVPN/tap-windows6 driver on hosts where all users can't be trusted. Users of Windows 7-10 and Server 2012r2 are recommended to update to latest installers as soon as possible.
This is primarily a maintenance release with minor bugfixes and improvements, and one security relevant fix for the Windows Interactive Service. Windows installer includes updated OpenVPN GUI and OpenSSL. Installer I601 included tap-windows6 driver 9.22.1 which had one security fix and dropped Windows Vista support. However, in installer I602 we had to revert back to tap-windows 9.21.2 due to driver getting reject on freshly installed Windows 10 rev 1607 and later when Secure Boot was enabled. The failure was due to the new, more strict driver signing requirements. The 9.22.1 version of the driver is in the process of getting approved and signed by Microsoft and will be bundled in an upcoming Windows installer.
This adds a second tap adapter and rename it. This can be done after install. You might need to install both sophos and ecather before running this fix. This script is available in the installation driver folder Talk2mVpnService > driver with the file called install.bat . The script will will add an adapter then rename it for ecathcer. The folder link should look something like C:\Program Files (x86)\eCatcher-Talk2M\Talk2mVpnService\drivers
Once in this directory right click on install.bat and select run as administrator.
I have a user that when they install the SSL client they do not get a Tap Windows Adapter. They get Unknown. I have tried updating and choosing the driver but get "an error encountered". There are numerous threads for OpenVpn client having these issues but no real fix except to reinstall Windows 10. Some have disabled Secure Boot. Haven't tried that yet as they are remote.
Under some rare circumstances, newer versions of the TAP driver for some versions of Windows can cause slowdowns and render the Internet practically un-browsable using any OpenVPN based service. The details of why it acts this way are not known, but there are several reports of people saying that downgrading to the last NDIS 5 version of the driver significantly improved their speed.
You might find that the adapter will re-appear inside Device Manager every time your system boots up. This situation occurs because some VPN programs have a startup service that checks for missing drivers and installs any needed driver automatically that is missing.
Step 4: Next, find Tap-Windows Adapter V9 and see if it has an exclamation mark on the icon associated with it. If it does, you should right-click the driver and select Uninstall device.
Support for Microsoft precision touchpad drivers in Windows is available for Mac computers with the Apple T2 Security Chip. If your Mac supports these drivers, you can set precision touchpad options using Windows; otherwise, you can set trackpad options using Boot Camp Control Panel. See the Apple Support article Mac models with the Apple T2 Security Chip.
This morning, when I turned my computer on, my wireless wouldn't connect to my router. When I looked in the Device Manager it had "Network Controller" in "Other Devices" and it said that there wasn't a driver installed for it.
I tried downloading the driver for the network adapter from the Dell service page, but the latest driver (R246753) says that I need to use the "Intel(R) PROSET/wireless installer" to install it. I downloaded a previous drives for it (1T47J, I believe), and it installed, but as soon as the installation was completed, Windows did a search for the driver and came up with the same problem... the driver wasn't installed. So, back to square one. I located the "Intel PROSet/Wireless Software and Drivers for Windows 7" on the intel site, downloaded and ran it, and it tried to install the driver, but when it was done, it put me back to square one again too.
I tried updating the driver using the Dell Support Center, but whereas it knows that there is something wrong with the driver situation for the Network Controller, it doesn't give any way to fix that. It just gives me the option to have Windows update it, and it ends up with the same result as above.
df19127ead