Oemvista Inf Tap0901 Tapinstall Exe Failed

| Posted on by

Updating drivers for tap0901 from C: Program Files (x86) OpenVPN driver OemWin2k. OpenVPN driver OemWin2k.inf. Tapinstall.exe failed. « Last Edit: April 06, 2010. Hi Jonathon, Not sure whether this is what caused it to appear to work or not but try copying the tpinstall.exe from the 32bit or the 64bit folder ( depending on your Windows 10 version ) to the folder C: Windows System32 When I click on NETWORK ADAPTORS in DEVICE MANAGER I now see TAP-Windows Adaptor V9 after the following command tapinstall install OemWin2k.inf TAP0901 but I had to do it in. Tapinstall.exe install OemVista.inf tap0901. Windows service installation. To be able to use the hydra service you need to install it into the system once.

Oemvista Inf Tap0901 Tap Install Exe Failed Bypass

OpenVPN GUI: 'No TAP-WIN32 adapters on this system' error fix

Last updated by Shayne M on May 22, 2013 08:38

On some versions of windows, specifically certain build of Windows 7 64-bit or when you have other VPN software installed some clients may experience the following error:

Inf

'There are no TAP-Win32 adapters on this system. You should be able to create a TAP-Win32 adapter by going to Start -> All Programs -> OpenVPN -> Add a new TAP-Win32 virtual ethernet adapter.'

To resolve this, open notepad as administrator and paste in the following:

tapinstall install OemWin2k.inf tap0901

And save this file to your vpnsecure program directory usually in C:Program Files (x86)VPNSecureMedriver32forceinstall.bat or C:Program Files (x86)VPNSecureMedriver64forceinstall.bat depending on whether you use 32 or 64 bit windows.

Then just run that batch file as administrator, the correct TUN adapter driver will be installed and the problem will be solved

Alternative 1

Install

You could install the latest version of OpenVPN GUI, which would also force this driver to be installed. Then you can use our application as normal.

There is an alternative OpenVPN portable project, that has a different way of installing TAP adapters - http://sourceforge.net/projects/ovpnp/ Prince lotus flower.

Alternative 2

You could uninstall this version of our application completely and install an older version that doesn't have this issue : http://vpnsecure.me/files/VPNS_0.9.3.0.exe

Alternative 3

There is a registry key that some users have found interfering with the TAP driver installation. If you're not comfortable with regedit, please contact our support staff for assistance - you can easily break your pc here!

Inf

1. Backup the registry (regedit > export)
2. In start>run>cmd>regedit, browse to the following registry entry:
HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlNetwork
3. Rename the key called Config to Config.bak

After renaming this key, re-run our windows openvpn installer and it should be able to install the TAP adapter this time.


VPNSecure Provides Secure VPN servers in over 45+ Countries

If you are a looking for a versatile easy to use VPN service, checkout Today

This is an NDIS 6 implementation of the TAP-Windows driver, used by OpenVPN and other apps. NDIS 6 drivers can run on Windows Vista or higher.

Build

To build, the following prerequisites are required:

  • Python 2.7
  • Microsoft Windows 7 WDK (Windows Driver Kit)
  • Windows code signing certificate
  • Git (not strictly required, but useful for running commands using bundled bash shell)
  • MakeNSIS (optional)
  • Patched source code directory of devcon sample from WDK (optional)
  • Prebuilt tapinstall.exe binaries (optional)

Make sure you add Python's install directory (usually c:python27) to the PATH environment variable.

These instructions have been tested on Windows 7 using Git Bash, as well as on Windows 2012 Server using Git Bash and Windows Powershell.

M icrosoft has removed the ISO files of Windows 10 Version 1511 (Build 10586), also known as TH2 (Threshold 2) or November Update, from public download. Microsoft had recently updated the Windows 10 Media Creation Tool, the official way to download Windows 10 ISO to download the latest version of Windows 10 November Update with the general availability of Windows 10 November Update. Windows 10 Enterprise Build 10586 64 Bit ISO Overview Windows 10 Enterprise Build 10586 ISO Free Download Latest RTM Build version. Its Full Bootable ISO Image Windows 10 Enterprise Build 10586 ISO 64 & 86 Bit. Windows 10 Build 10586 is the latest build that has hit the market. It is the first major update of the the operating system. Version 10.0.10586 build 10586. Update 2: Download links to Windows 10 Build 10586 tools are still available, as listed in step 1. Update 1: Microsoft has removed Windows 10 November Update (Version 1511 Build 10586) MCT, ADK, SDK, WDK, HLK, Mobile Emulator and ISO from TechBench.

View build script options::

$ python buildtap.py Usage: buildtap.py [options]

Options: -h, --help show this help message and exit -s SRC, --src=SRC TAP-Windows top-level directory, default= --ti=TAPINSTALL tapinstall (i.e. devcon) directory (optional) -d, --debug enable debug build -c, --clean do an nmake clean before build -b, --build build TAP-Windows and possibly tapinstall (add -c to clean before build) --sign sign the driver files (disabled by default) -p, --package generate an NSIS installer from the compiled files --cert=CERT Common name of code signing certificate, default=openvpn --crosscert=CERT The cross-certificate file to use, default=MSCV- VSClass3.cer --timestamp=URL Timestamp URL to use, default=http://timestamp.verisign.c om/scripts/timstamp.dll -a, --oas Build for OpenVPN Access Server clients

Edit version.m4 and paths.py as necessary then build::

$ python buildtap.py -b

On successful completion, all build products will be placed in the dist directory as well as tap6.tar.gz. The NSIS installer package will be placed tothe build root directory.

Note that due to the strict driver signing requirements in Windows 10 you needan EV certificate to sign the driver files. These EV certificates may bestored inside a hardware device, which makes fully automated signing processdifficult, dangerous or impossible. Eventually the signing process will becomeeven more involved, with drivers having to be submitted to the WindowsHardware Developer Center Dashboard portal. Therefore, by default, thisbuildsystem no longer signs any files. You can revert to the old behaviorby using the --sign parameter.

Building tapinstall (optional)

The build system supports building tapinstall.exe (a.k.a. devcon.exe). Howeverthe devcon source code in WinDDK does not build without modifications whichcannot be made public due to licensing restrictions. For these reasons thedefault behavior is to reuse pre-built executables. To make sure the buildsystemfinds the executables create the following directory structure undertap-windows6 directory::: tapinstall 7600 objfre_wlh_amd64 amd64 tapinstall.exe objfre_wlh_x86 i386 tapinstall.exe

This structure is equal to what building tapinstall would create. Replace 7600with the major number of your WinDDK version. Finally call buildtap.py with--ti=tapinstall.

Please note that the NSIS packaging (-p) step will fail if you don't havetapinstall.exe available. Also don't use the -c flag or the above directorieswill get wiped before MakeNSIS is able to find them.

Install/Update/Remove

Oemvista

The driver can be installed using a command-line tool, tapinstall.exe, which isbundled with OpenVPN and tap-windows installers. Note that in some versions ofOpenVPN tapinstall.exe is called devcon.exe. To install, update or remove thetap-windows NDIS 6 driver follow these steps:

  • place tapinstall.exe/devcon.exe to your PATH
  • open an Administrator shell
  • cd to dist
  • cd to amd64 or i386 depending on your system's processor architecture.

Install::

$ tapinstall install OemVista.inf TAP0901

Oemvista Inf Tap0901 Tap Install Exe Failed Download

Update::

$ tapinstall update OemVista.inf TAP0901

Remove::

$ tapinstall remove TAP0901

Notes on proxies

It is possible to build tap-windows6 without connectivity to the Internet but any attempt to timestamp the driver will fail. For this reason configure your outbound proxy server before starting the build. Note that the command prompt also needs to be restarted to make use of new proxy settings.

Oemvista Inf Tap0901 Tap Install Exe Failed Windows 10

Notes on Authenticode signatures

Oemvista.inf Tap0901 Tapinstall.exe Failed

Recent Windows versions such as Windows 10 are fairly picky about theAuthenticode signatures of kernel-mode drivers. In addition making older Windowsversions such as Vista play along with signatures that Windows 10 accepts can berather challenging. A good starting point on this topic is thebuilding tap-windows6 <https://community.openvpn.net/openvpn/wiki/BuildingTapWindows6>_page on the OpenVPN community wiki. As that page points out, having twocompletely separate Authenticode signatures may be the only reasonable option.Fortunately there is a tool, Sign-Tap6 <https://github.com/mattock/sign-tap6/>_,which can be used to append secondary signatures to the tap-windows6 driver orto handle the entire signing process if necessary.

License

Oemvista Inf Tap0901 Tap Install Exe Failed Version

See the file COPYING <COPYING>_.