TAP installer failed on Windows 10 1709 with 2.4.6

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
Hugo1
OpenVpn Newbie
Posts: 2
Joined: Wed Apr 25, 2018 7:25 am

TAP installer failed on Windows 10 1709 with 2.4.6

Post by Hugo1 » Wed Apr 25, 2018 7:07 pm

Installed OpenVP 2.4.6

"An error occurred installing the TAP device driver."

Windows:
Device-Manager (Error-Code 52)

Please Help me.
Thanks

Tom7320
OpenVPN User
Posts: 37
Joined: Thu Jan 28, 2016 7:44 pm

Re: TAP installer failed on Windows 10 1709 with 2.4.6

Post by Tom7320 » Wed Apr 25, 2018 8:35 pm

Hi!

Same problem here. I had this problem a couple times in the past and was always able to solve it. This time I am not. The driver installs but there is a signature problem (Code 52, little yellow exclamation mark in device manager). Thus the driver does not start and there is no tap device.

I tried to uninstall old versions, clean the registry, removed suspicious 3rd party software and so on. No success....

Is there anything else I coud try?

mhab12
OpenVpn Newbie
Posts: 2
Joined: Wed Apr 25, 2018 11:38 pm

Re: TAP installer failed on Windows 10 1709 with 2.4.6

Post by mhab12 » Wed Apr 25, 2018 11:39 pm

same issue here. I believe the driver signing is the issue and the devs will have to correct it, otherwise you could allow unsigned drivers by following this:
https://windowsreport.com/driver-signat ... indows-10/

Tom7320
OpenVPN User
Posts: 37
Joined: Thu Jan 28, 2016 7:44 pm

Re: TAP installer failed on Windows 10 1709 with 2.4.6

Post by Tom7320 » Thu Apr 26, 2018 7:02 am

Yes I agree! It is possible to correctly install the TAP driver by disabling driver signature enforcement (solution 1). BUT you also have to disable secure boot in the UEFI BIOS settings of your computer to make it work permanently after reboot. This in turn means that bitlocker drive encrypton does only work if you are willing to type in your 40 digit key on every boot which is unacceptable. Turning off bitlocker on a business notebook is also unacceptable.

So please dear developers fix the signining issues. Unfortunately I do not know how to do it myself.... :-(

samuli
OpenVPN Inc.
Posts: 113
Joined: Fri Aug 13, 2010 9:05 pm

Re: TAP installer failed on Windows 10 1709 with 2.4.6

Post by samuli » Thu Apr 26, 2018 3:45 pm

You're almost certainly having the same issue as here. If you can, please post your setupapi.dev.log files to that ticket so that we can be sure.

The easiest way to work around this problem is to install tap-windows6 9.21.2 from here while we figure out the proper solution.
--
Samuli Seppänen
Community Manager
OpenVPN Technologies, Inc

irc freenode net: mattock

samuli
OpenVPN Inc.
Posts: 113
Joined: Fri Aug 13, 2010 9:05 pm

Re: TAP installer failed on Windows 10 1709 with 2.4.6

Post by samuli » Thu Apr 26, 2018 7:02 pm

Please test this installer and let me know if it works on the affected systems.
--
Samuli Seppänen
Community Manager
OpenVPN Technologies, Inc

irc freenode net: mattock

Tom7320
OpenVPN User
Posts: 37
Joined: Thu Jan 28, 2016 7:44 pm

Re: TAP installer failed on Windows 10 1709 with 2.4.6

Post by Tom7320 » Thu Apr 26, 2018 7:10 pm

samuli wrote:
Thu Apr 26, 2018 3:45 pm
You're almost certainly having the same issue as here. If you can, please post your setupapi.dev.log files to that ticket so that we can be sure.

The easiest way to work around this problem is to install tap-windows6 9.21.2 from here while we figure out the proper solution.
Thx for the answer! Here is my setupapi.dev.log:

Code: Select all

[Device Install Log]
     OS Version = 10.0.16299
     Service Pack = 0.0
     Suite = 0x0100
     ProductType = 1
     Architecture = amd64

[BeginLog]

[Boot Session: 2018/04/26 20:48:11.485]

>>>  [Device Install (UpdateDriverForPlugAndPlayDevices) - tap0901]
>>>  Section start 2018/04/26 20:51:35.794
      cmd: "C:\Program Files\TAP-Windows\bin\tapinstall.exe" install "C:\Program Files\TAP-Windows\driver\OemVista.inf" tap0901
     ndv: INF path: C:\Program Files\TAP-Windows\driver\OemVista.inf
     ndv: Install flags: 0x00000001
     ndv: {Update Device Driver - ROOT\NET\0000}
     ndv:      Search options: 0x00000080
     ndv:      Searching single INF 'C:\Program Files\TAP-Windows\driver\OemVista.inf'
     dvi:      {Build Driver List} 20:51:35.826
     dvi:           Searching for hardware ID(s):
     dvi:                tap0901
     dvi:           Created Driver Node:
     dvi:                HardwareID   - tap0901
     dvi:                InfName      - c:\program files\tap-windows\driver\oemvista.inf
     dvi:                DevDesc      - TAP-Windows Adapter V9
     dvi:                Section      - tap0901.ndi
     dvi:                Rank         - 0x00ff0000
     dvi:                Signer Score - Authenticode
     dvi:                DrvDate      - 04/15/2018
     dvi:                Version      - 9.0.0.22
     dvi:      {Build Driver List - exit(0x00000000)} 20:51:35.888
     dvi:      {DIF_SELECTBESTCOMPATDRV} 20:51:35.888
     dvi:           Default installer: Enter 20:51:35.888
     dvi:                {Select Best Driver}
     dvi:                     Class GUID of device changed to: {4d36e972-e325-11ce-bfc1-08002be10318}.
     dvi:                     Selected Driver:
     dvi:                          Description - TAP-Windows Adapter V9
     dvi:                          InfFile     - c:\program files\tap-windows\driver\oemvista.inf
     dvi:                          Section     - tap0901.ndi
     dvi:                {Select Best Driver - exit(0x00000000)}
     dvi:           Default installer: Exit
     dvi:      {DIF_SELECTBESTCOMPATDRV - exit(0x00000000)} 20:51:35.935
     ndv:      Force Installing Driver:
     ndv:           Inf Name       - oemvista.inf
     ndv:           Driver Date    - 04/15/2018
     ndv:           Driver Version - 9.0.0.22
     ndv:      Driver package 'C:\Windows\System32\DriverStore\FileRepository\oemvista.inf_amd64_98fc017a6cec15eb\oemvista.inf' is already imported.
     sto:      {Setup Import Driver Package: c:\program files\tap-windows\driver\oemvista.inf} 20:51:35.951
     sto:           Driver package already imported as 'oem87.inf'.
     sto:      {Setup Import Driver Package - exit (0x00000000)} 20:51:35.982
     dvi:      Searching for hardware ID(s):
     dvi:           tap0901
     dvi:      Class GUID of device changed to: {4d36e972-e325-11ce-bfc1-08002be10318}.
     dvi:      {Plug and Play Service: Device Install for ROOT\NET\0000}
     dvi:           Driver INF Path: C:\Windows\INF\oem87.inf
     dvi:           Driver Node Name: oemvista.inf:3beb73aff103cc24:tap0901.ndi:9.0.0.22:tap0901,
     dvi:           Driver Store Path: C:\Windows\System32\DriverStore\FileRepository\oemvista.inf_amd64_98fc017a6cec15eb\oemvista.inf
     dvi:           Searching for hardware ID(s):
     dvi:                tap0901
     dvi:           Class GUID of device changed to: {4d36e972-e325-11ce-bfc1-08002be10318}.
     dvi:           {Core Device Install} 20:51:36.076
     dvi:                {Install Device - ROOT\NET\0000} 20:51:36.076
     dvi:                     Device Status: 0x01802001, Problem: 0x0 (0x00000000)
     dvi:                     Parent device: HTREE\ROOT\0
     dvi:                     {Configure Device - ROOT\NET\0000} 20:51:36.076
     dvi:                          Device Status: 0x01802001, Problem: 0x0 (0x00000000)
     dvi:                          Parent device: HTREE\ROOT\0
     sto:                          {Configure Driver Package: C:\Windows\System32\DriverStore\FileRepository\oemvista.inf_amd64_98fc017a6cec15eb\oemvista.inf}
     sto:                               Source Filter  = tap0901
     inf:                               Class GUID     = {4d36e972-e325-11ce-bfc1-08002be10318}
     inf:                               Class Options  = Configurable
     inf:                               {Configure Driver: TAP-Windows Adapter V9}
     inf:                                    Section Name = tap0901.ndi
     inf:                                    {Add Service: tap0901}
     inf:                                         Start Type    = 3
     inf:                                         Service Type  = 1
     inf:                                         Error Control = 1
     inf:                                         Image Path    = \SystemRoot\System32\drivers\tap0901.sys
     inf:                                         Display Name  = TAP-Windows Adapter V9
     inf:                                         Group         = NDIS
     inf:                                         Updated service 'tap0901'.
     inf:                                    {Add Service: exit(0x00000000)}
     inf:                                    Hardware Id  = tap0901
     inf:                                    {Configure Driver Configuration: tap0901.ndi}
     inf:                                         Service Name  = tap0901
     inf:                                         Config Flags  = 0x00000000
     inf:                                    {Configure Driver Configuration: exit(0x00000000)}
     inf:                               {Configure Driver: exit(0x00000000)}
     flq:                               Copying 'C:\Windows\System32\DriverStore\FileRepository\oemvista.inf_amd64_98fc017a6cec15eb\tap0901.sys' to 'C:\Windows\System32\drivers\tap0901.sys'.
     cpy:                               Existing file 'C:\Windows\System32\drivers\tap0901.sys' remains unchanged.
     sto:                          {Configure Driver Package: exit(0x00000000)}
     dvi:                          Install Device: Configuring device (oem87.inf:tap0901,tap0901.ndi). 20:51:36.107
     dvi:                          Install Device: Configuring device completed. 20:51:36.123
     dvi:                          Device Status: 0x01802001, Problem: 0x0 (0x00000000)
     dvi:                          Install Device: Starting device 'ROOT\NET\0000'. 20:51:36.123
     dvi:                          Install Device: Starting device completed. 20:51:36.123
!    dvi:                          Device pending start: Device has problem: 0x38 (CM_PROB_NEED_CLASS_CONFIG), problem status: 0x00000000.
     dvi:                     {Configure Device - exit(0x00000000)} 20:51:36.123
     dvi:                     Device Status: 0x01802401, Problem: 0x38
     dvi:                {Install Device - exit(0x00000000)} 20:51:36.154
     dvi:           {Core Device Install - exit(0x00000000)} 20:51:36.154
     dvi:           Waiting for device post-install to complete. 20:51:36.154
     dvi:           Device post-install completed. 20:51:36.397
!    dvi:           Device post-install problem: 0x34 (0xC0000428)
     ump:      {Plug and Play Service: Device Install exit(00000000)}
     ndv: {Update Device Driver - exit(00000000)}
     ndv: {Install Related Drivers} 20:51:36.428
     ndv: {Install Related Drivers: exit(0x00000000)} 20:51:36.448
<<<  Section end 2018/04/26 20:51:36.464
<<<  [Exit status: SUCCESS]
Windows TAP driver 9.21.2 unfortunately does not work. Same problem. I have to switch off secure boot for it to work.

Tom7320
OpenVPN User
Posts: 37
Joined: Thu Jan 28, 2016 7:44 pm

Re: TAP installer failed on Windows 10 1709 with 2.4.6

Post by Tom7320 » Thu Apr 26, 2018 7:20 pm

samuli wrote:
Thu Apr 26, 2018 7:02 pm
Please test this installer and let me know if it works on the affected systems.
No, sorry, does not work. Here ist the log:

Code: Select all

[Boot Session: 2018/04/26 21:15:21.485]

>>>  [Device Install (UpdateDriverForPlugAndPlayDevices) - tap0901]
>>>  Section start 2018/04/26 21:17:52.090
      cmd: "C:\Program Files\TAP-Windows\bin\tapinstall.exe" install "C:\Program Files\TAP-Windows\driver\OemVista.inf" tap0901
     ndv: INF path: C:\Program Files\TAP-Windows\driver\OemVista.inf
     ndv: Install flags: 0x00000001
     ndv: {Update Device Driver - ROOT\NET\0000}
     ndv:      Search options: 0x00000080
     ndv:      Searching single INF 'C:\Program Files\TAP-Windows\driver\OemVista.inf'
     dvi:      {Build Driver List} 21:17:52.121
     dvi:           Searching for hardware ID(s):
     dvi:                tap0901
     dvi:           Created Driver Node:
     dvi:                HardwareID   - tap0901
     dvi:                InfName      - c:\program files\tap-windows\driver\oemvista.inf
     dvi:                DevDesc      - TAP-Windows Adapter V9
     dvi:                Section      - tap0901.ndi
     dvi:                Rank         - 0x00ff0000
     dvi:                Signer Score - Authenticode
     dvi:                DrvDate      - 04/15/2018
     dvi:                Version      - 9.0.0.22
     dvi:      {Build Driver List - exit(0x00000000)} 21:17:52.184
     dvi:      {DIF_SELECTBESTCOMPATDRV} 21:17:52.199
     dvi:           Default installer: Enter 21:17:52.199
     dvi:                {Select Best Driver}
     dvi:                     Class GUID of device changed to: {4d36e972-e325-11ce-bfc1-08002be10318}.
     dvi:                     Selected Driver:
     dvi:                          Description - TAP-Windows Adapter V9
     dvi:                          InfFile     - c:\program files\tap-windows\driver\oemvista.inf
     dvi:                          Section     - tap0901.ndi
     dvi:                {Select Best Driver - exit(0x00000000)}
     dvi:           Default installer: Exit
     dvi:      {DIF_SELECTBESTCOMPATDRV - exit(0x00000000)} 21:17:52.246
     ndv:      Force Installing Driver:
     ndv:           Inf Name       - oemvista.inf
     ndv:           Driver Date    - 04/15/2018
     ndv:           Driver Version - 9.0.0.22
     ndv:      Driver package 'C:\Windows\System32\DriverStore\FileRepository\oemvista.inf_amd64_98fc017a6cec15eb\oemvista.inf' is already imported.
     sto:      {Setup Import Driver Package: c:\program files\tap-windows\driver\oemvista.inf} 21:17:52.262
     sto:           Driver package already imported as 'oem87.inf'.
     sto:      {Setup Import Driver Package - exit (0x00000000)} 21:17:52.293
     dvi:      Searching for hardware ID(s):
     dvi:           tap0901
     dvi:      Class GUID of device changed to: {4d36e972-e325-11ce-bfc1-08002be10318}.
     dvi:      {Plug and Play Service: Device Install for ROOT\NET\0000}
     dvi:           Driver INF Path: C:\Windows\INF\oem87.inf
     dvi:           Driver Node Name: oemvista.inf:3beb73aff103cc24:tap0901.ndi:9.0.0.22:tap0901,
     dvi:           Driver Store Path: C:\Windows\System32\DriverStore\FileRepository\oemvista.inf_amd64_98fc017a6cec15eb\oemvista.inf
     dvi:           Searching for hardware ID(s):
     dvi:                tap0901
     dvi:           Class GUID of device changed to: {4d36e972-e325-11ce-bfc1-08002be10318}.
     dvi:           {Core Device Install} 21:17:52.387
     dvi:                {Install Device - ROOT\NET\0000} 21:17:52.387
     dvi:                     Device Status: 0x01802001, Problem: 0x0 (0x00000000)
     dvi:                     Parent device: HTREE\ROOT\0
     dvi:                     {Configure Device - ROOT\NET\0000} 21:17:52.387
     dvi:                          Device Status: 0x01802001, Problem: 0x0 (0x00000000)
     dvi:                          Parent device: HTREE\ROOT\0
     sto:                          {Configure Driver Package: C:\Windows\System32\DriverStore\FileRepository\oemvista.inf_amd64_98fc017a6cec15eb\oemvista.inf}
     sto:                               Source Filter  = tap0901
     inf:                               Class GUID     = {4d36e972-e325-11ce-bfc1-08002be10318}
     inf:                               Class Options  = Configurable
     inf:                               {Configure Driver: TAP-Windows Adapter V9}
     inf:                                    Section Name = tap0901.ndi
     inf:                                    {Add Service: tap0901}
     inf:                                         Start Type    = 3
     inf:                                         Service Type  = 1
     inf:                                         Error Control = 1
     inf:                                         Image Path    = \SystemRoot\System32\drivers\tap0901.sys
     inf:                                         Display Name  = TAP-Windows Adapter V9
     inf:                                         Group         = NDIS
     inf:                                         Updated service 'tap0901'.
     inf:                                    {Add Service: exit(0x00000000)}
     inf:                                    Hardware Id  = tap0901
     inf:                                    {Configure Driver Configuration: tap0901.ndi}
     inf:                                         Service Name  = tap0901
     inf:                                         Config Flags  = 0x00000000
     inf:                                    {Configure Driver Configuration: exit(0x00000000)}
     inf:                               {Configure Driver: exit(0x00000000)}
     flq:                               Copying 'C:\Windows\System32\DriverStore\FileRepository\oemvista.inf_amd64_98fc017a6cec15eb\tap0901.sys' to 'C:\Windows\System32\drivers\tap0901.sys'.
     cpy:                               Existing file 'C:\Windows\System32\drivers\tap0901.sys' remains unchanged.
     sto:                          {Configure Driver Package: exit(0x00000000)}
     dvi:                          Install Device: Configuring device (oem87.inf:tap0901,tap0901.ndi). 21:17:52.418
     dvi:                          Install Device: Configuring device completed. 21:17:52.418
     dvi:                          Device Status: 0x01802001, Problem: 0x0 (0x00000000)
     dvi:                          Install Device: Starting device 'ROOT\NET\0000'. 21:17:52.418
     dvi:                          Install Device: Starting device completed. 21:17:52.418
!    dvi:                          Device pending start: Device has problem: 0x38 (CM_PROB_NEED_CLASS_CONFIG), problem status: 0x00000000.
     dvi:                     {Configure Device - exit(0x00000000)} 21:17:52.418
     dvi:                     Device Status: 0x01802401, Problem: 0x38
     dvi:                {Install Device - exit(0x00000000)} 21:17:52.434
     dvi:           {Core Device Install - exit(0x00000000)} 21:17:52.449
     dvi:           Waiting for device post-install to complete. 21:17:52.449
     dvi:           Device post-install completed. 21:17:52.606
!    dvi:           Device post-install problem: 0x34 (0xC0000428)
     ump:      {Plug and Play Service: Device Install exit(00000000)}
     ndv: {Update Device Driver - exit(00000000)}
     ndv: {Install Related Drivers} 21:17:52.621
     ndv: {Install Related Drivers: exit(0x00000000)} 21:17:52.637
<<<  Section end 2018/04/26 21:17:52.653
<<<  [Exit status: SUCCESS]

mhab12
OpenVpn Newbie
Posts: 2
Joined: Wed Apr 25, 2018 11:38 pm

Re: TAP installer failed on Windows 10 1709 with 2.4.6

Post by mhab12 » Thu Apr 26, 2018 7:56 pm

If it gives any clues, the publisher in the 'Programs & Features' control panel item shows up incorrectly. Perhaps this flows through the driver publisher too giving rise to the signature error? It shows up at ${PRODUCT_PUBLISHER}, not OpenVPN, Inc. as you would expect.

samuli
OpenVPN Inc.
Posts: 113
Joined: Fri Aug 13, 2010 9:05 pm

Re: TAP installer failed on Windows 10 1709 with 2.4.6

Post by samuli » Fri Apr 27, 2018 6:52 am

The PRODUCT_PUBLISHER thing is a separate problem. I've create new Windows installers which bundle the old tap-windows6 version. This is an interim solution while figuring out how to make MS sign the driver.
--
Samuli Seppänen
Community Manager
OpenVPN Technologies, Inc

irc freenode net: mattock

Tom7320
OpenVPN User
Posts: 37
Joined: Thu Jan 28, 2016 7:44 pm

Re: TAP installer failed on Windows 10 1709 with 2.4.6

Post by Tom7320 » Fri Apr 27, 2018 7:11 am

Strange! 9.21.2 also does not work on my system! Same problem! As soon as I switch off secure boot it works flawlessly!

Tom7320
OpenVPN User
Posts: 37
Joined: Thu Jan 28, 2016 7:44 pm

Re: TAP installer failed on Windows 10 1709 with 2.4.6

Post by Tom7320 » Wed May 02, 2018 4:55 am

...and it probably is a pious wish that Microsoft is so generous to add a tun/tap driver to their kernel sources, isn't it?

funmaker
OpenVpn Newbie
Posts: 1
Joined: Sun Jul 08, 2018 1:15 am

Re: TAP installer failed on Windows 10 1709 with 2.4.6

Post by funmaker » Sun Jul 08, 2018 1:20 am

This worked for me:

open cmd prompt via Start Menu, 'Windows System', right click on CMD (DOS prompt), More, then select Run as Administrator
on a command line type:

bcdedit.exe /set nointegritychecks on

This turns off integrity checking of unsigned driver - allows unsigned drivers to be installed
- run / install your software, openVPN TAP software

Test and then run the following to turn integrity checking back on

bcdedit.exe /set nointegritychecks off

This is a permanent fix, not temporary for this session.

Post Reply