MTK 2.6.2 Fails to install TAP Adapter (self.Piracy) submitted 1 year ago by AnalBumCover1000 I'm on a Licensed Win10 Pro desktop and I'm unable to activate Office 2013 using MTK.
During CIS4 installation, a prompt by Windows said that new hardware was being installed called 'TAP-Win32 Adapter V9'. Apparently it is a software driver to emulate hardware.
The user is given no information during the install of CIS4 as to what is this new 'device' that will be discovered by Windows. The user can opt to allow installation of the device or abort it. So which action should the user select?
![Adapter Adapter](/uploads/1/2/4/1/124145860/924077465.jpg)
They obviously have not been given info about it beforehand to make an educated decision. If I abort the 'device' install, the installation completes and, so far, CIS4 seems to work okay.
If I allow the 'device' installation, the install completes but I notice a 2nd tray icon for a network connection (which is disabled by default). Since CIS4 seems to be functioning without this pseudo-hardware device, why bother installing it at all and consternate the user who has to decide whether they need it or not or whether they want it or not? What is the TAP-Win32 Adapter V9 device? It appears to be some software-emulated network adapter. Why would I need another one besides the actual NIC in my host? Why isn't the user informed as to what is this 'device' so they can make an informed decision when the prompt appears?
I'm having trouble installing OpenVPN - the TAP driver simply refuses to install. I've tried 5 different versions of the installer - including v2.1 RC19 which, according to a Google search, seems to be everyones solution. I've tried v2.1.3, which supposedly should have the driver signing solved, v2.1.1, v2.1.4 and even v2.2 beta5 - all run as administrator. I've tried running the installers in compability mode set to Vista, aswell. I've tried downloading the x64 driver (tap0801), from openvpn.se, and installing it manually (from a dos prompt, run as administrator, from a destination folder that isn't named with troublesome characters like space), and between the installs, i've even made sure to uninstall the 'unknown' TAP network adaptor, the installations leaves behind. I've tried extracting the driver (tap0901) from the installer and manually install it, using same procedure as above.
I'm fresh out of ideas on how to get OpenVPN running on Windows 7 Ultimate x64, please help. Regards Mads Jensen. Hello, I'm not a Windows Guy(tm), but what sort of errors are being emitted when the installation fails?
After the error, is there anything left in the installation target directory? Check if the following path exists and contains any files: (I think) C: program files (x86) openvpn bin Specifically, I'm looking for the tapinstall.exe binary. If it doesn't it might be getting cleaned up if you exit the installer. If this is the case, try running the installation again but not exiting the installer after it pukes. If you can get an admin CLI with the tapinstall binary present, from openvpn bin, run the following command and post the output: tapinstall install. Driver oemwin2k.inf tap0901 Regards, Stephen.
Code: Previous Service REMOVE (if exists) Output folder: C: Program Files (x86) OpenVPN bin Extract: openvpn.exe. 100% Output folder: C: Program Files (x86) OpenVPN bin Extract: openvpn-gui-1.0.3.exe. 100% Output folder: C: Program Files (x86) OpenVPN easy-rsa Extract: openssl.cnf.sample. 100% Extract: vars.bat.sample. 100% Extract: init-config.bat. 100% Extract: README.txt.
![Failed Failed](https://hetmanrecovery.com/wp-content/themes/soft/images/device-manager/driver-installation.jpg)
100% Extract: build-ca.bat. 100% Extract: build-dh.bat. 100% Extract: build-key-server.bat. 100% Extract: build-key.bat.
100% Extract: build-key-pkcs12.bat. 100% Extract: clean-all.bat. 100% Extract: index.txt.start Extract: revoke-full.bat. 100% Extract: serial.start Output folder: C: Program Files (x86) OpenVPN bin Extract: openvpnserv.exe. 100% Output folder: C: Program Files (x86) OpenVPN config Output folder: C: Program Files (x86) OpenVPN sample-config Extract: sample.ovpn. 100% Extract: client.ovpn.
100% Extract: server.ovpn. 100% Create folder: C: Program Files (x86) OpenVPN log Output folder: C: Program Files (x86) OpenVPN bin Extract: libeay32.dll. 100% Extract: libssl32.dll. 100% Output folder: C: Program Files (x86) OpenVPN bin Extract: openssl.exe.
100% Output folder: C: Program Files (x86) OpenVPN bin Extract: libpkcs11-helper-1.dll. 100% We are running on a 64-bit system. Output folder: C: Program Files (x86) OpenVPN bin Extract: tapinstall.exe.
100% Output folder: C: Program Files (x86) OpenVPN driver Extract: OemWin2k.inf. 100% Extract: tap0901.cat. 100% Extract: tap0901.sys. 100% Create folder: C: Users Mads AppData Roaming Microsoft Windows Start Menu Programs OpenVPN Create folder: C: Users Mads AppData Roaming Microsoft Windows Start Menu Programs OpenVPN Documentation Create shortcut: C: Users Mads AppData Roaming Microsoft Windows Start Menu Programs OpenVPN Uninstall OpenVPN.lnk Output folder: C: Program Files (x86) OpenVPN Extract: INSTALL-win32.txt.
100% Extract: license.txt. 100% Extract: icon.ico. 100% tapinstall hwids returned: 0 TAP REMOVE OLD TAP No devices were removed. Tapinstall remove TAP0801 returned: 0 TAP INSTALL (tap0901) Device node created. Install is complete when drivers are installed.
Updating drivers for tap0901 from C: Program Files (x86) OpenVPN driver OemWin2k.inf. UpdateDriverForPlugAndPlayDevices failed, GetLastError=32 tapinstall.exe failed. Tapinstall install returned: 2 tapinstall cumulative status: 2 Service INSTALL OpenVPN Service installed. I tried to update the driver using Windows device manager, and it told me that the driver file was locked due to being used by another process.
Googling for a solution to this problem yielded no solution (quelle surprise), but the the universal Windows problem fixer solution (A.K.A. Reboot) released the lock on the file, and I was then able to install the driver with success. I feel a little silly for not trying this in the first place, but atleast thing are working for me again.
Regards Mads Jensen.