TAP installer failed on Windows 10 1709 with 2.4.6
Moderators: TinCanTech, TinCanTech, TinCanTech, TinCanTech, TinCanTech, TinCanTech
Forum rules
Please visit (and READ) the OpenVPN HowTo http://openvpn.net/howto prior to asking any questions in here!
Please visit (and READ) the OpenVPN HowTo http://openvpn.net/howto prior to asking any questions in here!
-
- OpenVpn Newbie
- Posts: 2
- Joined: Wed Apr 25, 2018 7:25 am
TAP installer failed on Windows 10 1709 with 2.4.6
Installed OpenVP 2.4.6
"An error occurred installing the TAP device driver."
Windows:
Device-Manager (Error-Code 52)
Please Help me.
Thanks
"An error occurred installing the TAP device driver."
Windows:
Device-Manager (Error-Code 52)
Please Help me.
Thanks
-
- OpenVPN User
- Posts: 38
- Joined: Thu Jan 28, 2016 7:44 pm
Re: TAP installer failed on Windows 10 1709 with 2.4.6
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?
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?
-
- OpenVpn Newbie
- Posts: 2
- Joined: Wed Apr 25, 2018 11:38 pm
Re: TAP installer failed on Windows 10 1709 with 2.4.6
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/
https://windowsreport.com/driver-signat ... indows-10/
-
- OpenVPN User
- Posts: 38
- Joined: Thu Jan 28, 2016 7:44 pm
Re: TAP installer failed on Windows 10 1709 with 2.4.6
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....
So please dear developers fix the signining issues. Unfortunately I do not know how to do it myself....
- samuli
- OpenVPN Inc.
- Posts: 49
- Joined: Fri Aug 13, 2010 9:05 pm
Re: TAP installer failed on Windows 10 1709 with 2.4.6
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.
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 Seppänen
Community Manager
OpenVPN Technologies, Inc
irc freenode net: mattock
- samuli
- OpenVPN Inc.
- Posts: 49
- Joined: Fri Aug 13, 2010 9:05 pm
Re: TAP installer failed on Windows 10 1709 with 2.4.6
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
Samuli Seppänen
Community Manager
OpenVPN Technologies, Inc
irc freenode net: mattock
-
- OpenVPN User
- Posts: 38
- Joined: Thu Jan 28, 2016 7:44 pm
Re: TAP installer failed on Windows 10 1709 with 2.4.6
Thx for the answer! Here is my setupapi.dev.log:samuli wrote: ↑Thu Apr 26, 2018 3:45 pmYou'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.
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]
-
- OpenVPN User
- Posts: 38
- Joined: Thu Jan 28, 2016 7:44 pm
Re: TAP installer failed on Windows 10 1709 with 2.4.6
No, sorry, does not work. Here ist the log:samuli wrote: ↑Thu Apr 26, 2018 7:02 pmPlease test this installer and let me know if it works on the affected systems.
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]
-
- OpenVpn Newbie
- Posts: 2
- Joined: Wed Apr 25, 2018 11:38 pm
Re: TAP installer failed on Windows 10 1709 with 2.4.6
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: 49
- Joined: Fri Aug 13, 2010 9:05 pm
Re: TAP installer failed on Windows 10 1709 with 2.4.6
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
Samuli Seppänen
Community Manager
OpenVPN Technologies, Inc
irc freenode net: mattock
-
- OpenVPN User
- Posts: 38
- Joined: Thu Jan 28, 2016 7:44 pm
Re: TAP installer failed on Windows 10 1709 with 2.4.6
Strange! 9.21.2 also does not work on my system! Same problem! As soon as I switch off secure boot it works flawlessly!
-
- OpenVPN User
- Posts: 38
- Joined: Thu Jan 28, 2016 7:44 pm
Re: TAP installer failed on Windows 10 1709 with 2.4.6
...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?
-
- OpenVpn Newbie
- Posts: 1
- Joined: Sun Jul 08, 2018 1:15 am
Re: TAP installer failed on Windows 10 1709 with 2.4.6
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.
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.
-
- OpenVpn Newbie
- Posts: 1
- Joined: Fri Sep 21, 2018 8:39 pm
Re: TAP installer failed on Windows 10 1709 with 2.4.6
I hopefully tried the last suggested solution. Sigh. It failed again. Here are the contents of the Installation Window:
We are running on a 64-bit system.
Output folder: C:\Program Files\TAP-Windows\bin
Extract: tapinstall.exe... 100%
Output folder: C:\Program Files\TAP-Windows\driver
Extract: OemVista.inf... 100%
Extract: tap0901.cat... 100%
Extract: tap0901.sys... 100%
Delete file: C:\ProgramData\Microsoft\Windows\Start Menu\Programs\TAP-Windows\Utilities\Add a new TAP virtual ethernet adapter.lnk
Delete file: C:\ProgramData\Microsoft\Windows\Start Menu\Programs\TAP-Windows\Utilities\Delete ALL TAP virtual ethernet adapters.lnk
Remove folder: C:\ProgramData\Microsoft\Windows\Start Menu\Programs\TAP-Windows\Utilities\
Remove folder: C:\ProgramData\Microsoft\Windows\Start Menu\Programs\TAP-Windows\
Create folder: C:\ProgramData\Microsoft\Windows\Start Menu\Programs\TAP-Windows\Utilities
Create shortcut: C:\ProgramData\Microsoft\Windows\Start Menu\Programs\TAP-Windows\Utilities\Add a new TAP virtual ethernet adapter.lnk
Create shortcut: C:\ProgramData\Microsoft\Windows\Start Menu\Programs\TAP-Windows\Utilities\Delete ALL TAP virtual ethernet adapters.lnk
Output folder: C:\Program Files\TAP-Windows
Extract: license.txt... 100%
Extract: icon.ico... 100%
tapinstall.exe hwids returned: 0
TAP update (tap0901) (May require confirmation)
Updating drivers for tap0901 from C:\Program Files\TAP-Windows\driver\OemVista.inf.
UpdateDriverForPlugAndPlayDevices failed, GetLastError=1460
tapinstall.exe failed.
tapinstall.exe returned: 2
tapinstall.exe cumulative status: 2
Created uninstaller: C:\Program Files\TAP-Windows\Uninstall.exe
Completed
We are running on a 64-bit system.
Output folder: C:\Program Files\TAP-Windows\bin
Extract: tapinstall.exe... 100%
Output folder: C:\Program Files\TAP-Windows\driver
Extract: OemVista.inf... 100%
Extract: tap0901.cat... 100%
Extract: tap0901.sys... 100%
Delete file: C:\ProgramData\Microsoft\Windows\Start Menu\Programs\TAP-Windows\Utilities\Add a new TAP virtual ethernet adapter.lnk
Delete file: C:\ProgramData\Microsoft\Windows\Start Menu\Programs\TAP-Windows\Utilities\Delete ALL TAP virtual ethernet adapters.lnk
Remove folder: C:\ProgramData\Microsoft\Windows\Start Menu\Programs\TAP-Windows\Utilities\
Remove folder: C:\ProgramData\Microsoft\Windows\Start Menu\Programs\TAP-Windows\
Create folder: C:\ProgramData\Microsoft\Windows\Start Menu\Programs\TAP-Windows\Utilities
Create shortcut: C:\ProgramData\Microsoft\Windows\Start Menu\Programs\TAP-Windows\Utilities\Add a new TAP virtual ethernet adapter.lnk
Create shortcut: C:\ProgramData\Microsoft\Windows\Start Menu\Programs\TAP-Windows\Utilities\Delete ALL TAP virtual ethernet adapters.lnk
Output folder: C:\Program Files\TAP-Windows
Extract: license.txt... 100%
Extract: icon.ico... 100%
tapinstall.exe hwids returned: 0
TAP update (tap0901) (May require confirmation)
Updating drivers for tap0901 from C:\Program Files\TAP-Windows\driver\OemVista.inf.
UpdateDriverForPlugAndPlayDevices failed, GetLastError=1460
tapinstall.exe failed.
tapinstall.exe returned: 2
tapinstall.exe cumulative status: 2
Created uninstaller: C:\Program Files\TAP-Windows\Uninstall.exe
Completed
-
- OpenVpn Newbie
- Posts: 1
- Joined: Wed Sep 26, 2018 9:37 am
Re: TAP installer failed on Windows 10 1709 with 2.4.6
I'm experiencing the same issue. Windows 10 1803 and installing tap-windows6 9.21.2. This started 3 days ago. Have tried all the options spoken above, and also, tried uninstalling TAP driver, and removing it from the registry. Still no change.
-
- OpenVpn Newbie
- Posts: 2
- Joined: Tue Oct 09, 2018 10:02 am
Re: TAP installer failed on Windows 10 1709 with 2.4.6
ghost887 did you fix the problem? It started for me about a week ago.
None of the fixes in this thread, or others I tried from other forums, worked for me.
-
- OpenVpn Newbie
- Posts: 2
- Joined: Tue Oct 09, 2018 10:02 am
Re: TAP installer failed on Windows 10 1709 with 2.4.6
Hey ghost887,
I just solved the problem I was having. Although re-reading this post you may be having a different problem.
Anyway on my OpenVPN client machine I ran this command "As Administrator":
C:\ProgramData\Microsoft\Windows\Start Menu\Programs\TAP-Windows\Utilities\Add a new TAP virtual ethernet adapter.lnk
I was trying to run it on my OpenVPN server machine. However it already had a properly functioning TAP virtual ethernet adapter.
Maybe this helps.
I just solved the problem I was having. Although re-reading this post you may be having a different problem.
Anyway on my OpenVPN client machine I ran this command "As Administrator":
C:\ProgramData\Microsoft\Windows\Start Menu\Programs\TAP-Windows\Utilities\Add a new TAP virtual ethernet adapter.lnk
I was trying to run it on my OpenVPN server machine. However it already had a properly functioning TAP virtual ethernet adapter.
Maybe this helps.
-
- OpenVpn Newbie
- Posts: 1
- Joined: Tue Nov 06, 2018 7:04 pm
Re: TAP installer failed on Windows 10 1709 with 2.4.6
This is happening for me too. Disabling SecureBoot isn't really an option for me.
I've tried removing all top drivers from the INF store:
https://docs.microsoft.com/en-us/previo ... 5(v=ws.11)
I've uninstalled and re-installed multiple times under different scenarios.
I've tried it with SecureBoot disabled.
I've tried it with SecureBoot disabled and driver integrity check turned off.
I've ran it as administrator.
I've tried to manually install.
Nothing works. It always locks up, and times out about 4 minutes later.
I only have windows defender for AV. Its a new laptop with a fresh install of windows 10 version 1803 Build 17134.345
setupapi.dev.log:
I've tried removing all top drivers from the INF store:
https://docs.microsoft.com/en-us/previo ... 5(v=ws.11)
I've uninstalled and re-installed multiple times under different scenarios.
I've tried it with SecureBoot disabled.
I've tried it with SecureBoot disabled and driver integrity check turned off.
I've ran it as administrator.
I've tried to manually install.
Nothing works. It always locks up, and times out about 4 minutes later.
I only have windows defender for AV. Its a new laptop with a fresh install of windows 10 version 1803 Build 17134.345
setupapi.dev.log:
Code: Select all
>>> [Device Install (UpdateDriverForPlugAndPlayDevices) - tap0901]
>>> Section start 2018/11/06 13:40:22.746
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\0001}
ndv: Search options: 0x00000080
ndv: Searching single INF 'C:\Program Files\TAP-Windows\driver\OemVista.inf'
dvi: {Build Driver List} 13:40:22.760
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/21/2016
dvi: Version - 9.0.0.21
dvi: {Build Driver List - exit(0x00000000)} 13:40:22.776
dvi: {DIF_SELECTBESTCOMPATDRV} 13:40:22.777
dvi: Default installer: Enter 13:40:22.778
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)} 13:40:22.785
ndv: Force Installing Driver:
ndv: Inf Name - oemvista.inf
ndv: Driver Date - 04/21/2016
ndv: Driver Version - 9.0.0.21
ndv: Driver package 'C:\Windows\System32\DriverStore\FileRepository\oemvista.inf_amd64_a572b7f20c402d28\oemvista.inf' is already imported.
sto: {Setup Import Driver Package: c:\program files\tap-windows\driver\oemvista.inf} 13:40:22.790
sto: Driver package already imported as 'oem70.inf'.
sto: {Setup Import Driver Package - exit (0x00000000)} 13:40:22.796
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\0001}
dvi: Driver INF Path: C:\Windows\INF\oem70.inf
dvi: Driver Node Name: oemvista.inf:3beb73aff103cc24:tap0901.ndi:9.0.0.21:tap0901,
dvi: Driver Store Path: C:\Windows\System32\DriverStore\FileRepository\oemvista.inf_amd64_a572b7f20c402d28\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} 13:40:22.857
dvi: {Install Device - ROOT\NET\0001} 13:40:22.859
dvi: Device Status: 0x01802001, Problem: 0x0 (0x00000000)
dvi: Parent device: HTREE\ROOT\0
dvi: {Configure Device - ROOT\NET\0001} 13:40:22.863
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_a572b7f20c402d28\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_a572b7f20c402d28\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 (oem70.inf:tap0901,tap0901.ndi). 13:40:22.897
dvi: Install Device: Configuring device completed. 13:40:22.900
dvi: Device Status: 0x01802001, Problem: 0x0 (0x00000000)
dvi: Install Device: Starting device 'ROOT\NET\0001'. 13:40:22.902
dvi: Install Device: Starting device completed. 13:40:22.906
! dvi: Device pending start: Device has problem: 0x38 (CM_PROB_NEED_CLASS_CONFIG), problem status: 0x00000000.
dvi: {Configure Device - exit(0x00000000)} 13:40:22.909
dvi: Device Status: 0x01802401, Problem: 0x38
dvi: {Install Device - exit(0x00000000)} 13:40:22.922
dvi: {Core Device Install - exit(0x00000000)} 13:40:22.923
dvi: Waiting for device post-install to complete. 13:40:22.925
!!! dvi: Timed out waiting for device post-install to complete. 13:44:07.928
ump: {Plug and Play Service: Device Install exit(000005b4)}
!!! ndv: Device install failed for device.
!!! ndv: Error 1460: This operation returned because the timeout period expired.
ndv: Installing NULL driver.
dvi: {Plug and Play Service: Device Install for ROOT\NET\0001}
! dvi: Installing NULL driver!
dvi: {DIF_ALLOW_INSTALL} 13:44:08.056
dvi: Default installer: Enter 13:44:08.057
dvi: Default installer: Exit
dvi: {DIF_ALLOW_INSTALL - exit(0xe000020e)} 13:44:08.059
dvi: {DIF_REGISTER_COINSTALLERS} 13:44:08.059
dvi: Default installer: Enter 13:44:08.060
dvi: Default installer: Exit
dvi: {DIF_REGISTER_COINSTALLERS - exit(0x00000000)} 13:44:08.062
dvi: {DIF_INSTALLDEVICE} 13:44:08.062
dvi: Default installer: Enter 13:44:08.063
! dvi: Installing NULL driver!
dvi: Install Null Driver: Removing device sub-tree. 13:44:08.066
dvi: Install Null Driver: Removing device sub-tree completed. 13:44:08.068
dvi: Install Null Driver: Restarting device. 13:44:08.073
dvi: Install Null Driver: Restarting device completed. 13:44:08.076
dvi: Install Device: Configuring device class. 13:44:08.077
dvi: Install Device: Configuring device class completed. 13:44:08.077
dvi: Device Status: 0x01802401, Problem: 0x1c (0x00000000)
dvi: Install Device: Starting device 'ROOT\NET\0001'. 13:44:08.080
dvi: Install Device: Starting device completed. 13:44:08.082
dvi: Default installer: Exit
dvi: {DIF_INSTALLDEVICE - exit(0x00000000)} 13:44:08.084
ump: {Plug and Play Service: Device Install exit(00000000)}
ndv: {Update Device Driver - exit(000005b4)}
!!! ndv: Failed to install device instance 'ROOT\NET\0001'. Error = 0x000005b4
<<< Section end 2018/11/06 13:44:08.090
<<< [Exit status: FAILURE(0x000005b4)]
-
- OpenVpn Newbie
- Posts: 9
- Joined: Wed Jan 18, 2012 10:52 pm
Re: TAP installer failed on Windows 10 1709 with 2.4.6
This worked for me - thank you so much! I did have to disable Secure Boot first, then do this, and then re-enable Secure Boot but it is working great now. Thanks again!funmaker wrote: ↑Sun Jul 08, 2018 1:20 amThis 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.
-
- OpenVpn Newbie
- Posts: 4
- Joined: Thu Mar 28, 2019 8:22 am
Re: TAP installer failed on Windows 10 1709 with 2.4.6
Thanks for the answer, that worked for me too