2
0
When I try to connect to my work VPN using OpenVPN, the connection fails with the message:
All TAP-Win32 adapters on this system are currently in use.
Many sources suggest to look in Control Panel\Network and Internet\Network Connections an enable the TAP adapter, but when I look there, there is none. Now I've run addtap.bat
which is provided with OpenVPN, but I still don't get to see any TAP adapter, and logging in in VPN still fails. The output of addtap.bat is
C:\Windows\system32>"C:\Program Files (x86)\OpenVPN\bin\tapinstall.exe" install
"C:\Program Files (x86)\OpenVPN\driver\OemWin2k.inf" tap0801
Device node created. Install is complete when drivers are updated...
Updating drivers for tap0801 from C:\Program Files (x86)\OpenVPN\driver\OemWin2k
.inf.
Drivers updated successfully.
I've Run As Administrator both the setup of OpenVPN and addtap.bat
.
I've run deltapall.bat
to remove any (maybe hidden) adapters. It said it removed three of them, after which I ran addtap.bat
again to try to create another one.
I also run OpenVPN itself as administrator. What's wrong?
Running Windows 7 Home Premium on a HP Pavilion dv7 4050ed. It has worked before, but I recently had to reinstall my laptop, for which I used the restore disks I created when I just got it. Everything else seems to work fine.
== UPDATE ==
The TAP adapter is found in Device Manager, but apparently it is disabled because it is incompatible with Windows 7 64bit. I've deïnstalled OpenVPNGui, downloaded a version that should be 64bit compatible, and installed that. Still no cigar. Then I found a tip to install OpenVPN (version 9) after installing OpenVPNGui, because that installs OpenVPN version 8. Now I got a v9 TAP driver in Device Manager, but it still doesn't work and shows up in device manager with an exclamation mark, and not at all in my network devices.
Not an answer to this issue perhaps, but on Windows 7 with OpenVPN 2.3.10 x86_64-w64-mingw32, running that addtap.bat script resulted in adapters that didn't connect properly, for me. After troubleshooting for a while, I tried manually executing the "devcon" command from the script, but specifying the OemVista.inf instead of the OemWin2k.inf file, and the resulting adapter worked immediately. – Peter Hansen – 2017-06-08T03:52:39.570
Apparently, TAP-adapter is not a tag? – GolezTrol – 2012-06-03T11:47:53.707