TAP-Win32 Adapter V9 Drivers Download

'an error ocurred installing the TAP device driver' while installing OpenVPN
To download TAP-Windows driver file, visit openvpn. This process will take some time. Registered driver package 'oemvista. PC Mag quote reprinted from www. Editing help is available. Some of them may have several versions available, e. Additionally, if you have any software that utilizes a virtual nic, you may want to make sure it's not running as well.

Navigation menu


I have the same question Amrita M Replied on September 15, Hope this information is helpful. Thanks for marking this as the answer. How satisfied are you with this reply? Thanks for your feedback, it helps us improve the site. How satisfied are you with this response? This site in other languages x.

Microsoft Teams - Office Team communication service subreddit. Xbox One - dedicated to Xbox One console and its peripherals, news and discussions.

Excel - dedicated to Excel, powerful program of Office suite. This subreddit is suitable for both Office warriors and newbies. Bing - dedicated to Microsoft's Bing web search and its news and discussions.

Tech Support - dedicated to solving problems and helping others out. I had the TAP virtual driver installed and even after the upgrade everything worked fine. But suddenly not sure if a Windows update was involved , the adapter stopped working.

I realised this as I tried to connect to an IPVanish server; the software just wouldn't connect. I decided to reinstall the TAP driver and downloaded the latest version 9. Unfortunately, the installer gets stuck at the following line: After a couple of minutes a message box shows "An error occurred installing the TAP device driver.

Existing files modified, may need to restart related services. Restart required for any devices using this driver. In Windows 10 version Build I have two machine with build , one upgraded from Windows 8, and another is a fresh install from MSDN. So upgrading is not correlated in my case.

I tested NDIS 6 tap-windows If i install the tap-windows on a fresh install, it works perfectly, without need a reboot. But if after i uninstall and reinstall directly, without reboot, uninstall don't ask a reboot , it hangs for FIVE minute and after throw this error: Device Manager show a 'Unknown device'. It's always reproducible on two machine, please tell me if you need any other informations.

I can confirm that what Clodo has reported is being experienced by us with the latest Windows 10 patch. However, we have one laptop which was updated to this latest version of Windows 10 on which now the OpenVPN installation times out during the TAP driver installation.

I will attempt to reboot and see if the adapter shows up properly. However, our usecase is slightly different in that we start openvpn as a Delayed Start service so that the user in the field doesn't require Administrator privileges. However, I am enclosing a screenshot of the error displayed when attempting a manual installation of tap-windows.

Responding to my own post from a couple of hours ago, I think I may have found at least part of the issue. I found that there were two TAP drivers installed. We have the same problem, as we ship openvpn as part or our product.

For us it is a showstopper, so I did some investigation what's going on here and would like to share my findings. First of all, this is not a problem of antivirus or vmware, these are all red herrings.

I have tested on Win10 both on clean installed hardware and in VMs, all without any antivirus except for the oob stuff and the problem exists on both. Our software exhibits this behaviour when updating, where we do a "devcon remove tap" and a "devcon install OemVista? If we do so, we get the 4 minute timeout and the tap adapter is gone. However, everything works if we reboot either inbetween these two devcon calls or afterwards which is a rather strange behaviour I have never seen before for root enumerated devices such as the openvpn tap adapter.

This is why it works for people after some time: They have simply rebooted their boxes in the mean time and the tap adapter either reappears or can be installed successfully. It also works if you start ncpa. So what I currently do in our software: Not really scientific, but it seems to work in our installer. Just for the records, this is the call stack in devcon during the 4 minute hang which is followed by the timeout error of UpdateDriverForPlugAndPlayDevices?

So maybe someone else can jump in and has an idea why launching ncpa. I have debugged devcon for these two calls and I cannot see why a reboot should be required, there is no indication for it in the API calls being made in these two calls UpdateDriverForPlugAndPlayDevices? So I guess that this is either a long standing bug in the ndis6 driver that never raised its head until lately or a bug in win10 Oh yes, another thing: It doesn't make a difference whether Win 10 is running as installed from the ISO or if the latest patches are applied to Somewhere someone purportedly had success when applying the latest patches, but I suppose that this just led to a reboot which heals all problems as described above.

It is going to be another thing for the next version of the driver, this will have to be signed using an EV certificate. I still am not able to install TAP driver. I am having the same issue, I can confirm that the pnputil to remove the driver from the driverstore doesn't actually fix the problem. It seems that rebooting and trying to install the drivers again sometimes works but not in all cases.

Any update from the developers? Ok i have a workaround that seems to work on all Windows 10 systems ive tried this so far on. Reboot and try again. We use the TAP driver in our software product and run the tapinstall command directly in the install process which just simply timesout after 5 minutes with an error. Performing the above workaround has worked on all machines experiencing this problem so far. I cannot seem to reproduce it anymore with Win 10 build Im wondering what kind of luck you guys have with this build.

This is the insider preview Fast Ring build I have a simple work around that I have confirmed works on 3 different WIN 10 x64 machines so far that wouldn't install TAP previously. I'm running Kaspersky Small Office Security 4. It will finish installing and will not hang. If you want to live dangerously, you can start the installer first, let it hang, then complete the steps.

It will become unstuck as soon as you hit "Apply" button after making the changes. I am also experiencing the problem on a Windows 8 machine.

I have no antivirus software installed. I tried all the methods above. Removed the driver from the driver store using pnputil, it does not help. The TAP driver just does not install.

I am putting my setupapi. Can this be reproduced with tap-windows That version is included in latest openvpn Windows installer releases, such as 2. Hello, I've been having the same problem since yesterday, while trying to update the TAP driver. This is Windows 10, 64 bit, and occurred while trying to install with tap-windows Since a week ago, I try to install the TAP driver, oem Win10 has been upgraded from Win7 in July this year.

Set selected driver complete. Searching single INF 'C: Processing a single INF: Looking for class installer for 'Netzwerkadapter' No class installer for 'Netzwerkadapter' dvi: Looking for co-installer modules for 'Netzwerkadapter'.

Selected driver installs from section [tap Rank - [0x00ff] dvi: Flags - 0x flq: Copying driver package files: Validating driver package files against catalog 'tap Driver package is valid. System restore not required for signed driver package. Importing driver package files: Opened driver package object 'oemvista.

Opened driver INF file object 'oem Setting catalog hint 'oem Catalog hint set on file 'C: Flushed all driver package files to disk. No system restore point was set earlier. Doing device matching lookup sto: Enumerating INFs from path list 'C: Searched 1 potential matches in published INF directory dvi: Installation deferred too early ump: Installation will be processed asynchronously. Installation will be processed asynchronously ndv: What happens if you try to install the tap driver indirectly, by installing openvpn 2.

The same thing happens; that's what I initially did, and it always fails installing tap driver. So, it seems to install when I go into Safe mode without networking; it didn't work with networking enabled , and shows up in the Device Manager. Just in case this helps. I don't know that much to give an useful insight to this problem. Is there anything special about your Win10 installations? Like, a rarely-seen security suite installed, special corporate VPN client, etc.? It works for most Win10 users, so I find it very surprising it stubbornly refuses to work for you.

That is all, as far as I can remember. Speaking of which, it used to work with all of those, but failed to install when I was trying to update i. I've tried installing the tap driver by itself without that, which unfortunately didn't work. I have a 2nd win10 system, same hardware, almost parallel installations and use.

There, openvnp and TAP had been installed some weeks earlier and work perfectly. I suggest that a recent win10 update might be the source of the trouble, there have been many of them in the last weeks I have heard anecdotal evidence that in some cases Windows Update can block devcon. If this the case, then stopping the Windows Update service should logically solve the problem.

To test this launch Windows Powershell as an administrator. If installation now works, then Windows update was the culprit. So, I did check the wuauserv, and it was already stopped. I guess this is the reason that it's not installing - upon trying to install the SoftEther? VPN again, it also failed to install its adapter.

Based on the fact that everything was running fine before this arised, I'm guessing that recent windows update broke something on my computer. Maybe I'll have to do a clean install of windows. Thank you all for looking into it though. Get-Service is not a recognized command on my system. Instead, I used "sc query wuauserv", indicating that the service is stopped. If Powershell is truly missing, then the Windows installation has been customized to some degree, as Powershell should be installed by default on Windows 7 and later, and possibly Vista.

I found a command for reinstalling the win10 apps, no success when installing Openvpn. Just found this ticket and sadly I've run into this issue numerous times. In my particular case at least, it's always been windows fault. The problem is with permissions of windows driver folders. It seems to trigger during windows update flights and appears to be random so I'm guessing the windows update fails at some point when restoring drivers as part of upgrade process.

Using the "Take Ownership" shell extension and adding myself to drivers folder and force propagating the permission fixes the problem. Take Ownership Shell Extension for Windows