TAP installer failed on Windows 10

This forum is for all inquiries relating to the installation of OpenVPN from source and with binaries.
Forum rules
Please visit (and READ) the OpenVPN HowTo http://openvpn.net/howto prior to asking any questions in here!
Post Reply
hermy9
OpenVpn Newbie
Posts: 3
Joined: Sun Nov 27, 2016 1:50 pm

TAP installer failed on Windows 10

Post by hermy9 » Sun Nov 27, 2016 2:40 pm

Hi, I hope that I am at the right place.

Installing Openvpn 2.3.13 failed on win10 with this error message, after two successful installations on other win10 systems.

"An error occurred installing the TAP device driver."

Installing TAP separately fails with the same error message. In addition, the log shows this sequence at the end:

"Updating drivers for tap0901 from C:\Program Files\TAP-Windows\driver\OemVista.inf.
UpdateDriverForPlugAndPlayDevices failed, GetLastError = -536870330
tapinstall.exe failed.
tapinstall.exe returned: 2
tapinstall cumulative status: 2
Created uninstaller: C:\Program Files\TAP-Windows\Ininstall.exe
Completed"

What is going wrong here? What does the error code mean?

I tried several things:
- Openvpn connection to my external server is not possible
- Avira Services deactivated
- Windows firewall deactivated
- reboot

The error code cannot be found with Google.

Hermy9

TinCanTech
OpenVPN Protagonist
Posts: 11142
Joined: Fri Jun 03, 2016 1:17 pm

Re: TAP installer failed on Windows 10

Post by TinCanTech » Mon Nov 28, 2016 1:59 pm

Try:

<Right-click> "Add new TAP Virtual ethernet adapter" -> Run as administrator

hermy9
OpenVpn Newbie
Posts: 3
Joined: Sun Nov 27, 2016 1:50 pm

Re: TAP installer failed on Windows 10

Post by hermy9 » Mon Nov 28, 2016 10:18 pm

Done by starting C:\Program Files\TAP-Windows\bin\addtap.bat as administrator.
Same error message.

hermy9
OpenVpn Newbie
Posts: 3
Joined: Sun Nov 27, 2016 1:50 pm

Re: TAP installer failed on Windows 10

Post by hermy9 » Sun Dec 04, 2016 8:31 am

In the meantime, I spent hours and tried a lot of things, no success up to now.

I noted that the driver is not in windows registry. Based on
https://support.vpnsecure.me/articles/g ... ters-found
I see 13 entries in registry:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e972-e325-11ce-bfc1-08002be10318}\xxxx
where
xxxx = 0000 .... 0012

None of them can be attributed to TAP-Windows Adapter V9. I followed the instruction given by the link above (which is not very clear), with no success.
On my other win10 system, I see 17 entries, and entry 0015 can be attributed to the TAP driver. There, all works fine.

Other attempts (reboot, windows secure mode, clean registry with ccleaner ...) were unsuccessful as well.

So, my question is still the same. What is going wrong when installing the TAP driver?

Last lines of C:\Windows\INF\setupapi.dev.log follow here, after having done this:
- uninstalling TAP and Openvpn using uninstall.exe for both
- cleaning c:\Benutzer\Administrator\AppData\Local\Temp

...
ndv: Forcing driver install:
ndv: Inf Name - oemvista.inf
ndv: Driver Date - 04/21/2016
ndv: Driver Version - 9.0.0.21
sto: {Setup Import Driver Package: c:\program files\tap-windows\driver\oemvista.inf} 09:17:52.921
sto: Driver package already imported as 'oem121.inf'.
sto: {Setup Import Driver Package - exit (0x00000000)} 09:17:52.921
inf: Opened INF: 'c:\program files\tap-windows\driver\oemvista.inf' ([strings])
dvi: Searching for hardware ID(s):
dvi: tap0901
inf: Opened INF: 'C:\WINDOWS\System32\DriverStore\FileRepository\oemvista.inf_amd64_a572b7f20c402d28\oemvista.inf' ([strings])
dvi: Created Driver Node:
dvi: HardwareID - tap0901
dvi: InfName - C:\WINDOWS\System32\DriverStore\FileRepository\oemvista.inf_amd64_a572b7f20c402d28\oemvista.inf
dvi: DevDesc - TAP-Windows Adapter V9
dvi: DrvDesc - TAP-Windows Adapter V9
dvi: Provider - TAP-Windows Provider V9
dvi: Mfg - TAP-Windows Provider V9
dvi: ModelsSec - tap0901.NTamd64
dvi: InstallSec - tap0901.ndi
dvi: Section - tap0901.ndi
dvi: Rank - 0x00ff0000
dvi: Signer - OpenVPN Technologies, Inc.
dvi: Signer Score - Authenticode
dvi: DrvDate - 04/21/2016
dvi: Version - 9.0.0.21
dvi: Enumerating INFs from path list 'C:\WINDOWS\INF'
inf: Searched 1 potential matches in published INF directory
dvi: Selected driver installs from section [tap0901.ndi] in 'c:\windows\system32\driverstore\filerepository\oemvista.inf_amd64_a572b7f20c402d28\oemvista.inf'.
dvi: Class GUID of device changed to: {4d36e972-e325-11ce-bfc1-08002be10318}.
dvi: Set selected driver complete.
ump: Installation deferred (too early)
ump: Installation will be processed asynchronously
!!! ndv: Device install failed for device.
ndv: Installing NULL driver.
ump: Installation deferred (too early)
ump: Installation will be processed asynchronously
ndv: {Update Device Driver - exit(e0000246)}
!!! ndv: Failed to install device instance 'ROOT\NET\0000'. Error = 0xe0000246
<<< Section end 2016/12/04 09:17:52.967
<<< [Exit status: FAILURE(0xe0000246)]

Renske
OpenVpn Newbie
Posts: 3
Joined: Tue Oct 17, 2017 1:49 pm

Re: TAP installer failed on Windows 10

Post by Renske » Tue Oct 17, 2017 2:00 pm

I have the same problem installing the TAP driver. I get the same error messages as mentioned by hermy9. It appears to be some problem with certificates:

From setupapi.dev.log:
! sig: Verifying file against specific (valid) catalog failed! (0x800b0109)
! sig: Error 0x800b0109: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.

I tried uninstalling, rebooting and installing (as administrator) several times, both OpenVPN and TAP separately, but I can't get it to work. My colleagues have exactly the same computer and they don't have any problems.

hermy9, did you ever manage to solve this problem? Does anyone else have any suggestions on what to try?
TinCanTech, where should I right-click for the option that you mentioned?

TinCanTech
OpenVPN Protagonist
Posts: 11142
Joined: Fri Jun 03, 2016 1:17 pm

Re: TAP installer failed on Windows 10

Post by TinCanTech » Tue Oct 17, 2017 4:59 pm

Windows Menu -> Tap Windows -> Add or Remove Tap Adapter

Must be run as administrator.

Renske
OpenVpn Newbie
Posts: 3
Joined: Tue Oct 17, 2017 1:49 pm

Re: TAP installer failed on Windows 10

Post by Renske » Thu Oct 19, 2017 7:36 am

Thanks for your reply TinCanTech. Unfortunately it is not working. I ran it as administrator, but I get the following error message:

"C:\Windows\system32>rem Add a new TAP virtual ethernet adapter

C:\Windows\system32>"C:\Program Files\TAP-Windows\bin\tapinstall.exe" install "C:\Program Files\TAP-Windows\driver\OemVista.inf" tap0901
Device node created. Install is complete when drivers are installed...
Updating drivers for tap0901 from C:\Program Files\TAP-Windows\driver\OemVista.inf.
UpdateDriverForPlugAndPlayDevices failed, GetLastError=-536870330
tapinstall.exe failed."

Do you have any other suggestions on what I could try?

TinCanTech
OpenVPN Protagonist
Posts: 11142
Joined: Fri Jun 03, 2016 1:17 pm

Re: TAP installer failed on Windows 10

Post by TinCanTech » Thu Oct 19, 2017 10:52 am

This bug has never been properly diagnosed - You may find some information here:

https://community.openvpn.net/openvpn/w ... iver-fails

https://community.openvpn.net/openvpn/q ... 1&order=id

kekster
OpenVpn Newbie
Posts: 1
Joined: Thu Apr 19, 2018 6:32 am

Re: TAP installer failed on Windows 10

Post by kekster » Thu Apr 19, 2018 6:38 am

Srry for bumping an old post... but keep getting this bloody error. Openvpn work flawlessly on my colleagues pc and we have exactly the same model. Any help will be greatly appreciated.

TinCanTech
OpenVPN Protagonist
Posts: 11142
Joined: Fri Jun 03, 2016 1:17 pm

Re: TAP installer failed on Windows 10

Post by TinCanTech » Thu Apr 19, 2018 11:55 am

There will be a new release of Openvpn very soon with updated TAP driver, hopefully these installation problems will be resolved.

Renske
OpenVpn Newbie
Posts: 3
Joined: Tue Oct 17, 2017 1:49 pm

Re: TAP installer failed on Windows 10

Post by Renske » Thu Apr 19, 2018 2:17 pm

I had the exact same problem: The TAP driver wouldn't install on my PC, while my colleagues with the same model PC didn't have any problems. In the end I solved the problem by resetting my PC in such way that it kept my personal files but uninstalled all installed programs/apps. I then installed OpenVPN first before re-installing the other programs. It was a some work of course, but I'm happy that it works now.

tojieb
OpenVpn Newbie
Posts: 1
Joined: Mon May 06, 2019 3:33 am

Re: TAP installer failed on Windows 10

Post by tojieb » Mon May 06, 2019 3:57 am

i got very same problem, tap driver can't installed. but not only using openVPN, other program like barracuda and etc had the same problem. maybe some of you, understand about driver installation policy on Windows 10? or something application blocking the installation

unknown
OpenVpn Newbie
Posts: 1
Joined: Thu Oct 10, 2019 8:15 am

Re: TAP installer failed on Windows 10 TEMP FIX

Post by unknown » Thu Oct 10, 2019 8:34 am

hey, found a temp workaround for this issue, not sure if it will work for you, but it did for me, here we go.

Steps:
  1. open control panel > device manager
  2. scroll down to "Network adapters"
  3. there should be one that shows as "unknown device", double click on it, head to the "Details" tab, then select the property "Device instance path", this should have a value of "ROOT/NET/0000"
  4. once you confirm the Infos above, head back to the "Network adapters" tab, and right-click the unknown device, then select "Update driver software", then a new window should open up, select "Search automatically for updated driver software".

    you should receive a notification saying that windows found and updated the driver software, and it will no longer show up as an unknown device on the network adapters tab, make sure you restart Open VPN if it was running, and Voila!!

adreyfus
OpenVpn Newbie
Posts: 1
Joined: Fri Nov 15, 2019 2:12 pm

Re: TAP installer failed on Windows 10

Post by adreyfus » Fri Nov 15, 2019 2:15 pm

Hi,

Same error for me. The solutions proposed above did not work.

But uninstalling Check Point VPN client worked !

rejerh
OpenVpn Newbie
Posts: 1
Joined: Fri Apr 10, 2020 3:45 am

Re: TAP installer failed on Windows 10

Post by rejerh » Fri Apr 10, 2020 3:46 am

Hi,

I am having the same problem on any of the version of TAP I could find (9.21, 9.22, 9.24)
This is very frustrating. Nothing I could find in this thread helped me resolve this issue.

Has anyone found a robust fix?

Thanks
Cheers

Bantic
OpenVpn Newbie
Posts: 1
Joined: Tue Jun 15, 2021 7:48 am

Re: TAP installer failed on Windows 10

Post by Bantic » Tue Jun 15, 2021 7:50 am

I fixed problem with installing adapter ( this is one of many solution becouse reason may be more then one)

Go to:
Control Panel -> Device Menager -> Networ adapters -> find TAP Windows Open VPN adapter -> delete it

After that intall as administrator TAP Adapter once agian.

sid11
OpenVpn Newbie
Posts: 1
Joined: Sun Sep 12, 2021 8:54 pm

Re: TAP installer failed on Windows 10

Post by sid11 » Sun Sep 12, 2021 10:57 pm

Unfortunately, none of the suggestions worked.

Got the same issue, here is my experience.

1. Running Windows 7, Ultimate edition, x64;

2. OpenVPN 2.5.3 gets installed fine;
however, setupapi.dev.log contains following:
sig: {_VERIFY_FILE_SIGNATURE} 15:18:46.274
sig: Key = oemvista.inf
sig: FilePath = c:\program files\tap-windows\driver\oemvista.inf
sig: Catalog = c:\program files\tap-windows\driver\tap0901.cat
! sig: Verifying file against specific (valid) catalog failed! (0x800b0109)
! sig: Error 0x800b0109: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.
sig: {_VERIFY_FILE_SIGNATURE exit(0x800b0109)} 15:18:46.331
sig: {_VERIFY_FILE_SIGNATURE} 15:18:46.331
sig: Key = oemvista.inf
sig: FilePath = c:\program files\tap-windows\driver\oemvista.inf
sig: Catalog = c:\program files\tap-windows\driver\tap0901.cat
sig: Success: File is signed in Authenticode(tm) catalog.
sig: Error 0xe0000241: The INF was signed with an Authenticode(tm) catalog from a trusted publisher.
sig: {_VERIFY_FILE_SIGNATURE exit(0xe0000241)} 15:18:46.351
(same applies to wintun)

So tap driver isn't being recognized by the system (go to device manager/check network section/see tap driver with yellow triangle on the icon:
"This device is not working properly because Windows cannot load the drivers required for this device. (Code 31)"

3. To resolve the tap driver challenges, tried:

3.1 Full system cleanup (delete all the drivers, openvpn installs, tap installer/reinstalled everything w/ and w/o tap installer)
(i still do wander why other drivers may interfere with the install from openvpn, but that's a diff story)
3.2 bcedit experiments & windows reboot with "disable driver signature enforcement"
3.3 manually imported certificates (via certmgr & mmc snap in for the local computer; to root & trusted publisher)
3.4 signed driver myself & used self-signed certificate

As an experiment, took clean windows 7 x64 sp1 - installed openvpn - has challenges too, works only under "disable driver signature enforcement".
But at least - tap driver is recognized as a driver - and is loaded properly if one chooses "disable driver signature"; so it sorta works.

~~~

After all the experiments, this is what i came down to:

There seem to be two issues that the latest OpenVPN installer has;
and latest tap driver installer has;
(and they seem to have it (at least) for the past ~8-10 releases (went as far as 9.9 with tap installer; and 2.0 with openvpn))

a) Challenge one: digital signature. Technically, one can bypass it by either experimenting bcedits; enabling test mode; or by loading via F8/disable driver signature. Who's at fault - Microsoft, who started enforcing driver signatures; that's annoying exercise to go through, a lot of projects out there choose not to do it;

b) Challenge two: busted certificate chain.
(that's the one is unable to overcome).
Something is screwed up with certificates associated with openvpn/tap installer.
And not with the certificate itself - the one that's assigned to it; it's good and legit; but specifically with the intermediate certificate: the one that (in theory) you could get from the digisign guys.

Funny enough, Microsoft has exactly the same challenges with one of their .NET library installs: and to resolve it, they have provided combined - proper - certificate - that you can install yourself and make it work.

But with OpenVPN - we do not have (direct) access to combined (and verified!) certificate (yes, i tried to get it exported/imported; including chain of certs; didn't work. tried to go to the source - digi sign website - to grab intermediate cert - no good either)
So cert challenges combined with digital signature challenges - and entire application becomes useless.

Direction that (in theory) could work:

If one updates registry; and adds following record to the driver:
"ComponentId" with the value "tap0901":
It makes "Network card" to be visible to openVPN app;
So error from "hey, you have no tap devices out there":
Turns into "hey, you have tap device there, but it's busy".
(chances are, OpenVPN queries registry directly, bypassing Windows API; which is why it makes a difference)

Therefore if one manages to mimic "properly enabled driver" through regedits - it might actually work, and provide solution to all those people who have troubles. I'll keep digging this direction, but if someone with a bit more experience could assist - help would be very much appreciated.

Alternative, is to provide chained certificate for the software (that's question to openvpn devs) that's been properly validated and considered to be valid by Microsoft.
That way, digital signature can be overrulled with bcedits/and/or/F8/disable driver signature enforcement):
And certs is legit:
And we'd be good.

Third alternative (unlikely) - is to include proper certificate & proper digital signature in the future releases of openvpn:
But while first one should be easy; getting proper signature in place doesn't seem to look too good.

~~

any other suggestions/comments/possible ways to resolve it - will seriously appreciate some help here.

For now it doesn't look too promising.

Post Reply