Opened 9 years ago
Last modified 3 years ago
#592 accepted Bug / Defect
Tap-Windows Adapter not work Windows 10
Reported by: | hmsgcr | Owned by: | Samuli Seppänen |
---|---|---|---|
Priority: | major | Milestone: | |
Component: | tap-windows6 | Version: | OpenVPN 2.3.8 (Community Ed) |
Severity: | Not set (select this one, unless your'e a OpenVPN developer) | Keywords: | tap |
Cc: | hsilescr@… |
Description
No work Windows 10 Tap-Windows Adapter
Add ComponentId?: tap0901 not fix the problem
Change History (81)
comment:2 Changed 9 years ago by
Component: | Generic / unclassified → tap-windows6 |
---|---|
Owner: | set to Samuli Seppänen |
Status: | new → assigned |
Version: | 2.2.2 → 2.3.8 |
comment:3 Changed 9 years ago by
End of file C:\Windows\INF\setupapi.dev.log: http://i.imgur.com/ZTQqsyh.png
comment:4 Changed 9 years ago by
Microsoft Windows [Version 10.0.10240] (c) 2015 Microsoft Corporation. All rights reserved. C:\WINDOWS\system32>"C:\Program Files\TAP-Windows\bin\tapinstall.exe" update "C:\Program Files\TAP-Windows\driver\OemVista.inf" tap0901 Updating drivers for tap0901 from C:\Program Files\TAP-Windows\driver\OemVista.inf. UpdateDriverForPlugAndPlayDevices failed, GetLastError=1460 tapinstall.exe failed. C:\WINDOWS\system32>sfc /scannow Beginning system scan. This process will take some time. Beginning verification phase of system scan. Verification 100% complete. Windows Resource Protection did not find any integrity violations. C:\WINDOWS\system32>
comment:5 Changed 9 years ago by
I can confirm I have this same issue while installing openvpn-install-2.3.8-I601-x86_64.exe or openvpn-install-2.3.8-I001-x86_64.exe on Windows 10 RTM.
I have also tried installing tap-windows-9.21.1.exe and get the following error.
UpdateDriverForPlugAndPlayDevices? failed, GetLastError?=1460
Image of failure: http://i.imgur.com/LilBhEq.png
comment:7 Changed 9 years ago by
This problem seems to stem from the new driver code-signing requirements from Microsoft:
- http://blogs.msdn.com/b/windows_hardware_certification/archive/2015/04/01/driver-signing-changes-in-windows-10.aspx
- https://msdn.microsoft.com/en-us/library/windows/hardware/hh801887.aspx
I'll notify people responsible for obtaining code-signing certificates and start jumping through these additional hoops...
comment:8 Changed 9 years ago by
Status: | assigned → accepted |
---|
comment:9 Changed 9 years ago by
I have the same problem too! Can't connect to my homelab((
How long this code-signing process will take?
comment:10 Changed 9 years ago by
I upgraded to Windows 10 x64 professionnal last week.
I found it smart to also update my VPN application just after, which in turn tried to update TAP-driver to v 9.21.1 (I was using 9.009 before that and it worked for months on 8.1)...
BUT
TAP-windows9.21.1 setup stopped , just after a UpdateDriverForPlugAndPlayDevices? fail with GetLastError? = 1460
and since... that must be the longer 7 days at googling and trying every way to get past the installer :
I tried rebooting, installing drivers and manually delete or disable meanwhile or after Tap-windows 9.21.1 setup stopped...
I tried editing registry, adding string "ComponentId?"="tap0901", importing the whole key when is was missing...
I tried ifcleanup.x64.exe utility to find any ghost network adapter...
I tried disabling any ethernet card, Antivirus, Windows builtin firewall...
I even tried (but with no success) to manually suppress TAP drivers from system32 driver store using pnp utility commandline.
Now I think the problem is not related with *my* config or parameters but more a tricky behaviour of the pilot which does not satisfy windows 10
Here is an extract of c:\Windows\INF\setupapi.dev.log :
flq: Copying 'C:\WINDOWS\System32\DriverStore\FileRepository\oemvista.inf_amd64_690431ea2d4f48b2\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 (oem78.inf:tap0901,tap0901.ndi). 01:06:18.701 dvi: Install Device: Configuring device completed. 01:06:18.705 dvi: Install Device: Starting device. 01:06:18.705 dvi: Install Device: Starting device completed. 01:06:18.712 ndv: {Installing device - exit(0x00000000)} 01:06:18.714 ndv: {Core Device Install - exit(0x00000000)} 01:06:18.714 ndv: Waiting for device post-install to complete. 01:06:18.715 !!! ndv: Timed out waiting for device post-install to complete. 01:10:18.715 ump: {Plug and Play Service: Device Install exit(000005b4)} !!! ndv: Device install failed for device. ndv: Installing NULL driver. dvi: {Plug and Play Service: Device Install for ROOT\NET\0000} ! ndv: Installing NULL driver!
It seems to wait 4 minutes or a "post-install" flag or answer from the TAP driver. Since it doesn't come, the installer just put a dummy component and... I'm screwed !
I hope this feedback can help you find out what goes wrong ?
comment:11 Changed 9 years ago by
The standard 64-bit 2.3.8 installer worked just fine on a fresh Windows 10 Pro 64-bit VM. I have also received similar success stories from others using fresh Windows 10 installs.
That said, there are 5 people in this report having issues, so the problem must be fairly widespread. A few questions:
- Has anyone reproduced this on a fresh Windows 10 install (=not an upgrade)?
- Did you have the old NDIS 5 driver (tap-windows, version 9.9.2_3) installed before trying to install the new NDIS 6 driver (tap-windows6, version 9.21.1)? The old driver is bundled in OpenVPN installers with build numbers such as I00x, whereas the new one is bundled with installer marked as I60x.
- Have you upgraded from some really old OpenVPN version, such as 2.2.2?
One thing to try is to completely remove any traces of OpenVPN and tap-windows/tap-windows6 before installing the latest I600x build. The removal is done best using the uninstaller installed by the old OpenVPN version you had installed - they're all still available on our download servers. The more recent uninstallers bundled in recent OpenVPN installers may or may not remove all traces of (really) old OpenVPN versions. Manually verifying the removal is probably a good idea. OpenVPN installer does a lot of stuff, but here are the main things:
- Adds registry keys to HKEY_LOCAL_MACHINE\SOFTWARE\OpenVPN
- Installs files to C:\Program Files\OpenVPN or C:\Program Files (x86)\OpenVPN
- Installs the tap-windows or tap-windows6 driver using devcon.exe (new installers) or tapinstall.exe (old installer)
- Adds the OpenVPN Technologies code-signing certificate to the certificate store under "Local computer -> Trusted Publishers".
You can manually verify if there are any leftovers after you've run the OpenVPN uninstaller. Registry keys can be manually removed using regedit.exe. Files can be removed using Windows Explorer. Tap-windows drivers can probably be removed using Device manager and/or devcon.exe (tapinstall.exe in older installers). Certificates can be removed using mmc.exe's certificates snap-in.
As for getting the EV certs for signing the tap-windows6 driver... this problem does not seem directly related to changes in code-signing requirements after all, as it only affects some Windows 10 systems.
comment:12 Changed 9 years ago by
Oh, and please note that it is the NDIS 5 tap-windows driver (bundled in I00x installers) does not work on Windows 10. Or if it still does, it will cease to work sooner or later. This is because Microsoft announced a year or so ago that it is removing support for NDIS 5 drivers from Windows.
So please make sure you're using OpenVPN installers builds marked as I60x (NDIS 6) not those marked as I00x (NDIS 5).
comment:14 Changed 9 years ago by
brilic: I had a good look at your setupapi.dev.log. The error at top seems related to some other driver (VMWare network adapter?). There are several tapinstall.exe lines, first one being "install", the remaining three "update". I see no tapinstall.exe-related errors, though. In any case, the tap-windows driver was not removed in between installs, i.e. you installed on top of an earlier OpenVPN install. I suggest completely uninstalling OpenVPN and tap-windows before installing a new version. Tap-windows updates usually work just fine, but I've heard that uninstall/reinstall occasionally works when update does not. Instructions for manually removing tap-windows/tap-windows6 drivers and verifying removal are here.
hsilescr: what improvements are you talking about?
To all people affected: please do a complete cleanup (see comment 11) first. Then try to install the latest release version of OpenVPN (32-bit, 64-bit). If this fixes your problem, please let us know. If it does not fix your problem, please answer these questions:
- Are you running 32-bit or 64-bit Windows?
- Are you running Windows 10 upgraded from Windows 7/8, or a clean install?
- Have you had some really old OpenVPN version, such as 2.2.2, installed before on the same computer?
- Please provide the relevant part of your setupapi.dev.log (instructions)
We need this information to narrow this down and hopefully manage to reproduce it ourselves.
comment:15 follow-up: 16 Changed 9 years ago by
Sadly all the steps doesn't fix the tap adapter.
Deinstalled all Tap adapter, also hidden ones in the device manager.
Cleaned Registry and folders and deleted the certificates.
Clean install isn't really a option for me.
64 bit upgraded from 8.1
Sadly doesn't know if there was some really old version installed. To long ago xD
Posting the log later, currently at work.
Edit: Also have vmware workstation installed. Maybe some problem with vmware?
comment:16 Changed 9 years ago by
Replying to Recoilmaster:
Edit: Also have vmware workstation installed. Maybe some problem with vmware?
RecoilMaster: that is possible - the setupapi.dev.log from brilic also indicated that VMWare was installed.
comment:17 Changed 9 years ago by
Replying to samuli:
RecoilMaster: that is possible - the setupapi.dev.log from brilic also indicated that VMWare was installed.
Yes, I also installed VMware Workstation 11.1.2 build-2780323.
On freshly installed Windows 10, Openvpn installed normally (no errors).
I also tried to remove completely OpenVPN, as it is written in the manual, but it did not help.
Since my last comment I rolled Windows up to control point at which OpenVPN worked.
comment:18 Changed 9 years ago by
Sadly deinstallation of VmWare? doesn't fix the problem.
>>> [Device Install (UpdateDriverForPlugAndPlayDevices) - tap0901] >>> Section start 2015/08/28 19:01:29.993 cmd: "C:\Program Files\TAP-Windows\bin\tapinstall.exe" install "C:\Program Files\TAP-Windows\driver\OemVista.inf" tap0901 dvi: {Update Device Driver - ROOT\NET\0000} dvi: {Build Driver List} 19:01:29.998 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 - 11/05/2014 dvi: Version - 9.0.0.21 dvi: {Build Driver List - exit(0x00000000)} 19:01:30.002 dvi: {DIF_SELECTBESTCOMPATDRV} 19:01:30.002 dvi: Default installer: Enter 19:01:30.002 dvi: {Select Best Driver} dvi: Class GUID of device changed to: {4d36e972-e325-11ce-bfc1-08002be10318}. dvi: Selected: 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)} 19:01:30.003 ndv: Forcing driver install: ndv: Inf Name - oemvista.inf ndv: Driver Date - 11/05/2014 ndv: Driver Version - 9.0.0.21 ndv: Driver package 'c:\program files\tap-windows\driver\oemvista.inf' exists under 'C:\WINDOWS\System32\DriverStore\FileRepository\oemvista.inf_amd64_690431ea2d4f48b2\oemvista.inf' (oem22.inf). 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} ndv: Driver INF Path: C:\WINDOWS\INF\oem22.inf ndv: Driver Node Name: oemvista.inf:3beb73aff103cc24:tap0901.ndi:9.0.0.21:tap0901 ndv: Driver Store Path: C:\WINDOWS\System32\DriverStore\FileRepository\oemvista.inf_amd64_690431ea2d4f48b2\oemvista.inf dvi: Searching for hardware ID(s): dvi: tap0901 dvi: Class GUID of device changed to: {4d36e972-e325-11ce-bfc1-08002be10318}. ndv: {Core Device Install} 19:01:30.019 ndv: {Installing device - ROOT\NET\0000} 19:01:30.020 sto: {Configure Driver Package: C:\WINDOWS\System32\DriverStore\FileRepository\oemvista.inf_amd64_690431ea2d4f48b2\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_690431ea2d4f48b2\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 (oem22.inf:tap0901,tap0901.ndi). 19:01:30.039 dvi: Install Device: Configuring device completed. 19:01:30.043 dvi: Install Device: Starting device. 19:01:30.043 dvi: Install Device: Starting device completed. 19:01:30.048 ndv: {Installing device - exit(0x00000000)} 19:01:30.050 ndv: {Core Device Install - exit(0x00000000)} 19:01:30.050 ndv: Waiting for device post-install to complete. 19:01:30.051 !!! ndv: Timed out waiting for device post-install to complete. 19:05:30.051 ump: {Plug and Play Service: Device Install exit(000005b4)} !!! ndv: Device install failed for device. ndv: Installing NULL driver. dvi: {Plug and Play Service: Device Install for ROOT\NET\0000} ! ndv: Installing NULL driver! dvi: {DIF_ALLOW_INSTALL} 19:05:30.090 dvi: Default installer: Enter 19:05:30.091 dvi: Default installer: Exit dvi: {DIF_ALLOW_INSTALL - exit(0xe000020e)} 19:05:30.091 dvi: {DIF_REGISTER_COINSTALLERS} 19:05:30.091 dvi: Default installer: Enter 19:05:30.092 dvi: Default installer: Exit dvi: {DIF_REGISTER_COINSTALLERS - exit(0x00000000)} 19:05:30.092 dvi: {DIF_INSTALLDEVICE} 19:05:30.092 dvi: Default installer: Enter 19:05:30.093 ! dvi: Installing NULL driver! dvi: Install Null Driver: Removing device sub-tree. 19:05:30.094 dvi: Install Null Driver: Removing device sub-tree completed. 19:05:30.096 dvi: Install Null Driver: Restarting device. 19:05:30.105 dvi: Install Null Driver: Restarting device completed. 19:05:30.106 dvi: Install Device: Configuring device class. 19:05:30.106 dvi: Install Device: Configuring device class completed. 19:05:30.107 dvi: Install Device: Starting device. 19:05:30.107 dvi: Install Device: Starting device completed. 19:05:30.108 dvi: Default installer: Exit dvi: {DIF_INSTALLDEVICE - exit(0x00000000)} 19:05:30.109 ump: {Plug and Play Service: Device Install exit(00000000)} ndv: {Update Device Driver - exit(000005b4)} !!! ndv: Failed to install device instance ROOT\NET\0000 (Error 0x000005b4) <<< Section end 2015/08/28 19:05:30.111 <<< [Exit status: FAILURE(0x000005b4)]
Some interesting fact.
After deinstallation of VMWare Workstation i want to reinstall it again.
Looks like it's Network Adapter also doesn't install again.
Same error as with the TAP Adapter. Shitty Windows 10.
>>> [Device Install (UpdateDriverForPlugAndPlayDevices) - *VMnetAdapter1] >>> Section start 2015/08/28 19:34:17.227 cmd: "D:\Program Files (x86)\VMware\VMware Workstation\vnetlib64.exe" -- add adapter vmnet1 dvi: {Update Device Driver - ROOT\VMWARE\0000} dvi: {Build Driver List} 19:34:17.233 dvi: Searching for hardware ID(s): dvi: *vmnetadapter1 dvi: Created Driver Node: dvi: HardwareID - *VMnetAdapter1 dvi: InfName - d:\program files (x86)\vmware\vmware workstation\netadapter.inf dvi: DevDesc - VMware Virtual Ethernet Adapter for VMnet1 dvi: Section - VMnetAdapter1.Install dvi: Rank - 0x00ff0000 dvi: Signer Score - WHQL dvi: DrvDate - 01/23/2014 dvi: Version - 4.2.3.0 dvi: {Build Driver List - exit(0x00000000)} 19:34:17.237 dvi: {DIF_SELECTBESTCOMPATDRV} 19:34:17.237 dvi: Default installer: Enter 19:34:17.237 dvi: {Select Best Driver} dvi: Class GUID of device changed to: {4d36e972-e325-11ce-bfc1-08002be10318}. dvi: Selected: dvi: Description - [VMware Virtual Ethernet Adapter for VMnet1] dvi: InfFile - [d:\program files (x86)\vmware\vmware workstation\netadapter.inf] dvi: Section - [VMnetAdapter1.Install] dvi: {Select Best Driver - exit(0x00000000)} dvi: Default installer: Exit dvi: {DIF_SELECTBESTCOMPATDRV - exit(0x00000000)} 19:34:17.239 ndv: Forcing driver install: ndv: Inf Name - netadapter.inf ndv: Driver Date - 01/23/2014 ndv: Driver Version - 4.2.3.0 ndv: Driver package 'd:\program files (x86)\vmware\vmware workstation\netadapter.inf' exists under 'C:\WINDOWS\System32\DriverStore\FileRepository\netadapter.inf_amd64_6a0f50617799c89d\netadapter.inf' (oem34.inf). dvi: Searching for hardware ID(s): dvi: *vmnetadapter1 dvi: Class GUID of device changed to: {4d36e972-e325-11ce-bfc1-08002be10318}. dvi: {Plug and Play Service: Device Install for ROOT\VMWARE\0000} ndv: Driver INF Path: C:\WINDOWS\INF\oem34.inf ndv: Driver Node Name: netadapter.inf:fc9f1aa2477c2bb3:VMnetAdapter1.Install:4.2.3.0:*vmnetadapter1 ndv: Driver Store Path: C:\WINDOWS\System32\DriverStore\FileRepository\netadapter.inf_amd64_6a0f50617799c89d\netadapter.inf dvi: Searching for hardware ID(s): dvi: *vmnetadapter1 dvi: Class GUID of device changed to: {4d36e972-e325-11ce-bfc1-08002be10318}. ndv: {Core Device Install} 19:34:17.256 ndv: {Installing device - ROOT\VMWARE\0000} 19:34:17.257 dvi: {DIF_ALLOW_INSTALL} 19:34:17.262 dvi: Default installer: Enter 19:34:17.263 dvi: Default installer: Exit dvi: {DIF_ALLOW_INSTALL - exit(0xe000020e)} 19:34:17.263 dvi: {DIF_INSTALLDEVICEFILES} 19:34:17.264 dvi: Default installer: Enter 19:34:17.264 dvi: Default installer: Exit dvi: {DIF_INSTALLDEVICEFILES - exit(0x00000000)} 19:34:17.265 flq: File 'C:\WINDOWS\system32\DRIVERS\vmnet.sys' pruned from copy. flq: Copying 'C:\WINDOWS\System32\DriverStore\FileRepository\netadapter.inf_amd64_6a0f50617799c89d\vmnetadapter.sys' to 'C:\WINDOWS\system32\DRIVERS\vmnetadapter.sys'. flq: Copying 'C:\WINDOWS\System32\DriverStore\FileRepository\netadapter.inf_amd64_6a0f50617799c89d\vnetinst.dll' to 'C:\WINDOWS\system32\vnetinst.dll'. dvi: {DIF_REGISTER_COINSTALLERS} 19:34:17.297 dvi: Reset Device: Resetting device configuration. 19:34:17.298 dvi: Reset Device: Resetting device configuration completed. 19:34:17.298 dvi: Default installer: Enter 19:34:17.298 dvi: Default installer: Exit dvi: {DIF_REGISTER_COINSTALLERS - exit(0x00000000)} 19:34:17.299 dvi: {DIF_INSTALLINTERFACES} 19:34:17.300 dvi: Using exported function 'VNL_AdapterCoinstaller' in module 'C:\WINDOWS\system32\vnetinst.dll'. dvi: CoInstaller 1 == vnetinst.dll,VNL_AdapterCoinstaller dvi: CoInstaller 1: Enter 19:34:17.330 dvi: CoInstaller 1: Exit dvi: Default installer: Enter 19:34:17.331 dvi: Default installer: Exit dvi: {DIF_INSTALLINTERFACES - exit(0x00000000)} 19:34:17.332 dvi: {DIF_INSTALLDEVICE} 19:34:17.332 dvi: CoInstaller 1: Enter 19:34:17.332 dvi: CoInstaller 1: Exit dvi: Default installer: Enter 19:34:17.333 dvi: {Install DEVICE} dvi: {Writing Device Properties} dvi: Strong Name=oem34.inf:fc9f1aa2477c2bb3:VMnetAdapter1.Install:4.2.3.0:*vmnetadapter1 dvi: {Writing Device Properties - Complete} inf: AddService=VMnetAdapter,2,VMnetAdapter.Service,VMnetAdapter.EventLog,,VMnetAdapter (netadapter.inf line 370) dvi: Add Service: Created service 'VMnetAdapter'. dvi: {Install DEVICE exit (0x00000000)} sto: {Configure Driver Package: c:\windows\system32\driverstore\filerepository\netadapter.inf_amd64_6a0f50617799c89d\netadapter.inf} sto: Source Filter = VMnetAdapter1.Install sto: Target Filter = ROOT\VMWARE\0000 inf: Class GUID = {4d36e972-e325-11ce-bfc1-08002be10318} inf: Class Options = Configurable inf: {Configure Driver: VMware Virtual Ethernet Adapter for VMnet1} inf: Section Name = VMnetAdapter1.Install inf: {Configure Device: ROOT\VMWARE\0000} inf: {Configure Device: exit(0x00000000)} inf: {Configure Driver: exit(0x00000000)} sto: {Configure Driver Package: exit(0x00000000)} dvi: Install Device: Configuring device class. 19:34:17.352 dvi: Install Device: Configuring device class completed. 19:34:17.352 dvi: {Restarting Devices} 19:34:17.352 dvi: Restart: ROOT\VMWARE\0000 dvi: {Restarting Devices exit} 19:34:17.373 dvi: Default installer: Exit dvi: CoInstaller 1: Enter (Post Processing) 19:34:17.374 dvi: CoInstaller 1: Exit (Post Processing) dvi: {DIF_INSTALLDEVICE - exit(0x00000000)} 19:34:17.392 dvi: {DIF_NEWDEVICEWIZARD_FINISHINSTALL} 19:34:17.393 dvi: CoInstaller 1: Enter 19:34:17.393 dvi: CoInstaller 1: Exit dvi: Default installer: Enter 19:34:17.393 dvi: Default installer: Exit dvi: {DIF_NEWDEVICEWIZARD_FINISHINSTALL - exit(0xe000020e)} 19:34:17.394 ndv: {Installing device - exit(0x00000000)} 19:34:17.396 ndv: {Core Device Install - exit(0x00000000)} 19:34:17.396 ndv: Waiting for device post-install to complete. 19:34:17.397 !!! ndv: Timed out waiting for device post-install to complete. 19:38:17.398 dvi: {DIF_DESTROYPRIVATEDATA} 19:38:17.398 dvi: CoInstaller 1: Enter 19:38:17.398 dvi: CoInstaller 1: Exit dvi: Default installer: Enter 19:38:17.399 dvi: Default installer: Exit dvi: {DIF_DESTROYPRIVATEDATA - exit(0xe000020e)} 19:38:17.399 ump: {Plug and Play Service: Device Install exit(000005b4)} !!! ndv: Device install failed for device. ndv: Installing NULL driver. dvi: {Plug and Play Service: Device Install for ROOT\VMWARE\0000} ! ndv: Installing NULL driver! dvi: {DIF_ALLOW_INSTALL} 19:38:17.421 dvi: Using exported function 'VNL_AdapterCoinstaller' in module 'C:\WINDOWS\system32\vnetinst.dll'. dvi: CoInstaller 1 == vnetinst.dll,VNL_AdapterCoinstaller dvi: CoInstaller 1: Enter 19:38:17.425 dvi: CoInstaller 1: Exit dvi: Default installer: Enter 19:38:17.425 dvi: Default installer: Exit dvi: {DIF_ALLOW_INSTALL - exit(0xe000020e)} 19:38:17.426 dvi: {DIF_REGISTER_COINSTALLERS} 19:38:17.426 dvi: CoInstaller 1: Enter 19:38:17.426 dvi: CoInstaller 1: Exit dvi: Default installer: Enter 19:38:17.426 dvi: Default installer: Exit dvi: {DIF_DESTROYPRIVATEDATA} 19:38:17.427 dvi: CoInstaller 1: Enter 19:38:17.427 dvi: CoInstaller 1: Exit dvi: Default installer: Enter 19:38:17.427 dvi: Default installer: Exit dvi: {DIF_DESTROYPRIVATEDATA - exit(0xe000020e)} 19:38:17.427 dvi: {DIF_REGISTER_COINSTALLERS - exit(0x00000000)} 19:38:17.428 dvi: {DIF_INSTALLDEVICE} 19:38:17.428 dvi: Using exported function 'VNL_AdapterCoinstaller' in module 'C:\WINDOWS\system32\vnetinst.dll'. dvi: CoInstaller 1 == vnetinst.dll,VNL_AdapterCoinstaller dvi: CoInstaller 1: Enter 19:38:17.428 dvi: CoInstaller 1: Exit dvi: Default installer: Enter 19:38:17.429 ! dvi: Installing NULL driver! dvi: Install Null Driver: Removing device sub-tree. 19:38:17.430 dvi: Install Null Driver: Removing device sub-tree completed. 19:38:17.432 dvi: Install Null Driver: Restarting device. 19:38:17.439 dvi: Install Null Driver: Restarting device completed. 19:38:17.440 dvi: Install Device: Configuring device class. 19:38:17.440 dvi: Install Device: Configuring device class completed. 19:38:17.440 dvi: Install Device: Starting device. 19:38:17.441 dvi: Install Device: Starting device completed. 19:38:17.442 dvi: Default installer: Exit dvi: CoInstaller 1: Enter (Post Processing) 19:38:17.442 dvi: CoInstaller 1: Exit (Post Processing) dvi: {DIF_INSTALLDEVICE - exit(0x00000000)} 19:38:17.458 dvi: {DIF_DESTROYPRIVATEDATA} 19:38:17.458 dvi: CoInstaller 1: Enter 19:38:17.459 dvi: CoInstaller 1: Exit dvi: Default installer: Enter 19:38:17.459 dvi: Default installer: Exit dvi: {DIF_DESTROYPRIVATEDATA - exit(0xe000020e)} 19:38:17.459 ump: {Plug and Play Service: Device Install exit(00000000)} ndv: {Update Device Driver - exit(000005b4)} !!! ndv: Failed to install device instance ROOT\VMWARE\0000 (Error 0x000005b4) <<< Section end 2015/08/28 19:38:17.462 <<< [Exit status: FAILURE(0x000005b4)]
Setting the installation timeout for drivers like mentioned from vmware for error 0x000005b4 doesnt fix the problem.
comment:19 Changed 9 years ago by
Clean install with "Windows 10" same effect as a software update 8.1 or 7 revised on 64 and 32 bytes.
comment:20 Changed 9 years ago by
Seems to be Kaspersky NDIS 6 intermediate driver which interfere with TAP-windows. Uninstalling antivirus made Tap adapter appear in local network connections at once.
I'm performing some other tests to re-enable Kaspersky now
comment:22 follow-up: 23 Changed 9 years ago by
I'm using Kaspersky Total Security 2016 and got the same problem. So I think this can be confirmed.
But what will be the solution on this? I cannot uninstall my Anti-Virus tool or switch to another.
In addition I bet, that there are other tools as well, using those Tap devices.
comment:23 Changed 9 years ago by
Replying to ABauer:
I'm using Kaspersky Total Security 2016 and got the same problem. So I think this can be confirmed.
But what will be the solution on this? I cannot uninstall my Anti-Virus tool or switch to another.
In addition I bet, that there are other tools as well, using those Tap devices.
I was able to upgrade OpenVPN in this way:
1) completely removed the Kaspersky (2015/2016) with program http://media.kaspersky.com/utilities/ConsumerUtilities/kavremover.exe ;
2) Install the latest version of OpenVPN;
3) Install Kaspersky (http://www.kaspersky.ru/product-updates);
By the way, Kaspersky did not allow to install not only OpenVPN, but even the network card and wifi drivers.
comment:24 follow-up: 27 Changed 9 years ago by
I suggest contacting Kaspersky support, summarizing the problem and providing them with a link to this bug report. There is nothing we can really do at the OpenVPN end.
comment:25 follow-up: 26 Changed 9 years ago by
I desistale all antivirus + firewall and not working I seem to not want to give him the necessary support from openvpn
comment:26 Changed 9 years ago by
Replying to hsilescr:
I desistale all antivirus + firewall and not working I seem to not want to give him the necessary support from openvpn
I do not know what is your antivirus, but in the case of Kaspersky, disabling antivirus did not help install OpenVPN. Only full uninstall of Kaspersky.
comment:27 follow-up: 28 Changed 9 years ago by
Replying to samuli:
I suggest contacting Kaspersky support, summarizing the problem and providing them with a link to this bug report. There is nothing we can really do at the OpenVPN end.
Replying to myself to clarify this a bit. The problem with antivirus software is that they add low-level hooks into the operating system. OpenVPN and tap-windows operate above those hooks and have no way to affect or modify the protective measures the antivirus has in place. If we could circumvent antivirus software, so could a virus.
That said, I notified Kaspersky of this issue. I will let you guys know what their response is.
comment:28 Changed 9 years ago by
@samuli: Thanks a lot for pointing this out and contacting Kaspersky. Hopefully they have some good news for us.
comment:29 follow-up: 30 Changed 9 years ago by
Response from Kaspersky:
"We have tried to reproduce the issue in a windows 10 virtual machine with Kaspersky Internet Security 2016 (16.0.0.614) installed. OpenVPN 2.3.8 64 bit version installed with no errors or issues. Also installed the tap-windows drivers from your separate download link and it installed with no issue."
Are you all using Kaspersky Total Security 2016? If not, let me know what you are using. Also, have you modified the default settings of Kaspersky in some way?
comment:30 Changed 9 years ago by
Replying to samuli:
Response from Kaspersky:
"We have tried to reproduce the issue in a windows 10 virtual machine with Kaspersky Internet Security 2016 (16.0.0.614) installed. OpenVPN 2.3.8 64 bit version installed with no errors or issues. Also installed the tap-windows drivers from your separate download link and it installed with no issue."
Are you all using Kaspersky Total Security 2016? If not, let me know what you are using. Also, have you modified the default settings of Kaspersky in some way?
I asked Kaspersky to test with Kaspersky Total Security 2016. I hope they manage to reproduce this bug now.
comment:31 Changed 9 years ago by
The problem occures on Kaspersky Total Security 2016. You're on the right track :)
comment:32 Changed 9 years ago by
Hi Everone,
today, I made a retry with Kaspersky Total Sec Version 16.0.0.614(a) and OpenVPN Connect 2.0.18.202 and it worked (on Windows 10 64bit)!
I deinstalled Kaspersky using the uninstaller found on their homepage and deinstalled any OpenVPN/Tap NDIS stuff maybe left over.
Then I reinstalled Kaspersky, upgraded to latest Version, rebooted and then installed OpenVPN. Now it works like a charm.
I got no good explanaition for that and I refuse to make any guess.
Can anyone please try this as well and confirm or decline this solution?
Uninstaller can be found here:
http://support.kaspersky.com/common/service.aspx?el=1464#block1
Fresh Kaspersky can be downloaded here:
http://www.kaspersky.com/de/downloads
comment:33 Changed 9 years ago by
I confirm that with Kaspersky Total Security 2015 installed, TAP driver was hanging on installation. It's not the case with 2016.0.0.614, and the installation process get on term. But there are still huge interferences between Kaspersky NDIS6 and TAP-windows driver when it gets installed :
- random disconnections from VPN server
- "shadow" connections still dangling while trying to reconnect, even when closing and relaunching every application/OS
- routing and in particular DNS validation is faulty, more often down than working.
Disabling the antivirus, or removing the NDIS6 filter on every Ethernet connections, even [uninstall] that NDIS filter in a connection properties made nothing work better.
The only remedy so far to get OpenVPN work (install for once, then stable at use) has been to remove totally Kaspersky from my system (versions 2015, or 2016 the same).
So the combo Win10 x64 + KTS 2016 + TAP-windows is still non-functional.
Has anyone got KIS 2016 (Internet Security) working better than KTS (Total Security) in the same conditions ? (I doubt it, but why I could ask Kaspersky to change my licence if it's the case) :
Please try to sustain the VPN connection for some time and donwload something. I haven't been able to get it stable more than a few minutes. Then random websites began to timeout, connection speed was falling then I was disconnected from VPN server with no hope of restoring DNS routing without rebooting the OS.
PS : I'm going to make every action ABauer said, in the same order, notably with the removal tool I haven't tried yet.
comment:34 Changed 9 years ago by
Hi, finally I managed to get things work stable, using ABauer method. Here is what I've done :
1) uninstall Kaspersky antivirus
2) using Kaspersky remover utility , select KTS 2015 (2 versions proposed) then another turn for 2016. Please note that this step erases every information like antispam collection, licensing info etc.)
3) reboot
4) uninstall TAP-windows
5) optionnaly, I uninstalled every program that could interfere or filter over my network connections (here, Hagel DU meter 7.09)
6) reboot
7) reinstall fresh KIS 2016 (not KTS bescause it wasn't proposed for my language yet) - at this point, I let it work on '30 days evaluation period) - update bases...
8) reinstall OpenVPN / TAP-windows last version. No problem encountered.
Here I checked if VPN connection was sustainable, with no loose DNS /routing like before.
9) reinstall third-party programs
10) re-enter Kaspersky license info (for KTS), and let KIS convert itself to the right version (very short process btw)
No problem encountered so far, and it works like a charm, indeed.
As a matter of fact, there is no trace left of the infamous "Kaspersky antivirus NDIS 6 driver" in any of my network connections properties.
I can only suppose it was removal-tool major effect.
I hope this whole ticket will help any fellow with trouble installing OpenVPN. Antivirus and Firewalls (any brand) are definitely something to double-check when encountering weird problems using VPN.
Thx again everyone for the team work !
comment:35 Changed 9 years ago by
A response from Kaspersky. Published with their permission as-is:
Unfortunately neither our developers were able to reproduce the issue, either on KIS or KTS 2016. One suggestion we were given is to try the installation procedure after you have disabled Self-Defense feature.
In order to disable Self-defense of Kaspersky:
- If the main window of Kaspersky application is not on your desktop, bring it up by double-clicking the Kaspersky desktop shortcut (icon) or by double clicking on the Kaspersky icon in the bottom right corner of the screen;
- Click on the Gear icon in the bottom left corner of the Kaspersky window;
- On the left side menu select 'Additional';
- On the right side menu select 'Self-defense'
- Uncheck the box 'Enable Self-Defense' and click 'Continue'
A detailed "How to" guide is available here: http://support.kaspersky.com/11145 (click on the link to bring up the guide)
If that makes no difference we would require the following information to further investigate the issue, since we cannot reproduce it in our environment:
A) A screenshot of the error message that comes up when you try to install your application/drivers, as well as a screenshot of the network connections window as it should be with the tap drivers installed.
B) GSI report with Kaspersky installed and another one, where the installation wasn't prevented and the application/drivers were installed correctly.
To submit the GetSystemInfo report:
1) Download the utility GetSystemInfo.exe from the following direct link: http://media.kaspersky.com/utilities/ConsumerUtilities/GetSystemInfo6.0.exe (click on it to initiate download)
2) Restart your computer.
3) Run the GetSystemInfo.exe and click Accept
4) Click on the green Play symbol. The process can take up to 10 minutes and the progress bar may remain below 10% for most of the time.
5) A *.zip file with a name similar to this will be saved on your desktop automatically:
eg. GetSystemInfo_PC_Name_Username_Date_Time.zip
6) Please send us that .zip archive containing the report as an attachment in a reply to this email.
Further support (including a video) on how to use the GetSystemInfo utility can be found here: http://support.kaspersky.com/general/dumps/3632 (click on that link to bring up the detailed guide)
C) Please submit traces:
1) Pause Protection. To do that simply right-click the Red & Black Kaspersky icon in System Tray (on the bottom right corner of your screen) and select “Pause Protection”.
2) Enable Tracing: Click on the customer support icon in the bottom left corner of the main Kaspersky window – Support Tools - Enable traces.
3) Reproduce the issue where the installation fails.
4) Disable Tracing. Click on the customer support icon in the bottom left corner of the main Kaspersky window – Support Tools - Disable traces (stop).
5) Send us the resulting traces. A guide on ‘How to locate trace files’ is available via the link: http://support.kaspersky.com/11139#block1
Note that these instructions apply to 2016 version as well.
Traces are *.log files with a specific name:
[Product].[Version]_[Date]_[Time]_[Random].[Type]. For example:
- KAV.16.0.0.614._._*.SRV.log
- KAV.16.0.0.614._._*.GUI.log
Please note that we require both GUI and SRV traces.
Please upload traces to our FTP: http://support.kaspersky.com/faq/myaccount#section2 or to any freeware file-hosting service and submit a download link.
If possible, please pack traces in an archive with maximum compression.
We will be waiting for your feedback in order to proceed.
I suggest that those affected open a support request with Kaspersky and provide them the information they are requesting. Reporting the results of the debugging here would be most welcome!
comment:36 Changed 9 years ago by
- This problem is now happening on our Windows 10 X64 desktops as well.
- Kaspersky is not used.
- Virus scanners are disabled.
- Windows 10.0 x64 (Build 10240)
- Tried full openVPN package openvpn-install-2.3.8-I601-x86_64.exe as Administrator
- Inital install of tap-windows-9.21.1.exe stand-alone package on another Windows 10 x64 Desktop first, asks for you to trust certificate, installes certificate no issue, then it fails to continue to install the driver.
- Subsiquent uninstall / reinstall just fails. (no further certificate notifications)
- Tried running under Compatibility mode for 8,7 etc.. No Change
- Registry key entry to check for "ComponentId??"="tap0901" doesn't exist as TAP is not installed.
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\include
Extract: tap-windows.h... 100%
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)
- This takes about a minute or so before it fails.
- Pop-Up box for TAP-Windows 9.21.1 Setup (An error occurred installing the TAP device driver.)
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\include
Extract: tap-windows.h... 100%
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
Windows 10 Event Viewer
Driver Management concluded the process to install driver oemvista.inf_amd64_690431ea2d4f48b2\oemvista.inf for Device Instance ID ROOT\NET\0000 with the following status: 0x0.
- Trying to use Add-Tap from C:\Program Files\TAP-Windows\bin (Run as Administrator)
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.
---Stalls here for 2 or more minutes---
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?=1460
tapinstall.exe failed.
C:\WINDOWS\system32>pause
Press any key to continue . . .
- If we look in the Device Manager and see the "Unknown Device", click on it and try to update the driver from the TAP install folder, we get a windows saying "Installing driver software..." Which continues for a minuite or two before failing.
Error message reads:
Windows encountered a problem installing the driver software for your device.
Windows found driver software for your device but encountered an error wile attempting to install it.
TAP-Windows adaptor V9
This operation returned because the timeout period expired.
If you know the manufacturer of your device, you can visit its website and check the support section for driver software.
Driver Management concluded the process to install driver oemvista.inf_amd64_690431ea2d4f48b2\oemvista.inf for Device Instance ID ROOT\NET\0000 with the following status: 0x0.
- Below here is the Windows 10 setupapi.dev.log informaiton
[Device Install Log]
OS Version = 10.0.10240
Service Pack = 0.0
Suite = 0x0100
ProductType? = 1
Architecture = amd64
[Boot Session: 2015/11/09 18:22:15.497]
[Device Install (DiShowUpdateDevice?) - ROOT\NET\0000]
Section start 2015/11/10 12:56:37.311
cmd: "C:\WINDOWS\system32\mmc.exe" "C:\WINDOWS\system32\compmgmt.msc" /s
dvi: {DIF_UPDATEDRIVER_UI} 12:56:37.311
dvi: Default installer: Enter 12:56:37.311
dvi: Default installer: Exit
dvi: {DIF_UPDATEDRIVER_UI - exit(0xe000020e)} 12:56:37.311
ndv: {Update Driver Software Wizard for ROOT\NET\0000}
ndv: Driver package 'C:\WINDOWS\INF\oem86.inf' exists under 'C:\WINDOWS\System32\DriverStore?\FileRepository?\oemvista.inf_amd64_690431ea2d4f48b2\oemvista.inf' (oem86.inf).
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}
ndv: Driver INF Path: C:\WINDOWS\INF\oem86.inf
ndv: Driver Node Name: oemvista.inf:3beb73aff103cc24:tap0901.ndi:9.0.0.21:tap0901
ndv: Driver Store Path: C:\WINDOWS\System32\DriverStore?\FileRepository?\oemvista.inf_amd64_690431ea2d4f48b2\oemvista.inf
dvi: Searching for hardware ID(s):
dvi: tap0901
dvi: Class GUID of device changed to: {4d36e972-e325-11ce-bfc1-08002be10318}.
ndv: {Core Device Install} 12:56:45.468
ndv: {Installing device - ROOT\NET\0000} 12:56:45.468
sto: {Configure Driver Package: C:\WINDOWS\System32\DriverStore?\FileRepository?\oemvista.inf_amd64_690431ea2d4f48b2\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_690431ea2d4f48b2\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 (oem86.inf:tap0901,tap0901.ndi). 12:56:45.484
dvi: Install Device: Configuring device completed. 12:56:45.484
dvi: Install Device: Starting device. 12:56:45.484
dvi: Install Device: Starting device completed. 12:56:45.484
ndv: {Installing device - exit(0x00000000)} 12:56:45.484
ndv: {Core Device Install - exit(0x00000000)} 12:56:45.484
ndv: Waiting for device post-install to complete. 12:56:45.499
!!! ndv: Timed out waiting for device post-install to complete. 13:00:45.511
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\0000}
! ndv: Installing NULL driver!
dvi: {DIF_ALLOW_INSTALL} 13:00:45.527
dvi: Default installer: Enter 13:00:45.527
dvi: Default installer: Exit
dvi: {DIF_ALLOW_INSTALL - exit(0xe000020e)} 13:00:45.527
dvi: {DIF_REGISTER_COINSTALLERS} 13:00:45.527
dvi: Default installer: Enter 13:00:45.527
dvi: Default installer: Exit
dvi: {DIF_REGISTER_COINSTALLERS - exit(0x00000000)} 13:00:45.527
dvi: {DIF_INSTALLDEVICE} 13:00:45.527
dvi: Default installer: Enter 13:00:45.527
! dvi: Installing NULL driver!
dvi: Install Null Driver: Removing device sub-tree. 13:00:45.527
dvi: Install Null Driver: Removing device sub-tree completed. 13:00:45.543
dvi: Install Null Driver: Restarting device. 13:00:45.543
dvi: Install Null Driver: Restarting device completed. 13:00:45.543
dvi: Install Device: Configuring device class. 13:00:45.543
dvi: Install Device: Configuring device class completed. 13:00:45.543
dvi: Install Device: Starting device. 13:00:45.543
dvi: Install Device: Starting device completed. 13:00:45.543
dvi: Default installer: Exit
dvi: {DIF_INSTALLDEVICE - exit(0x00000000)} 13:00:45.543
ump: {Plug and Play Service: Device Install exit(00000000)}
ndv: {Update Driver Software Wizard exit(000005b4)}
<<< Section end 2015/11/10 13:06:29.133
<<< [Exit status: FAILURE(0x000005b4)]
- Tried Manually adding in Device Manager via Legacy Hardware (Network, Have disk, etc) also fails.
comment:37 Changed 9 years ago by
- Here is a comparison from a windows 10 x64 Desktop that did work.
- This is the ONLY desktop that has worked so far out of 5 tried.
[Device Install (UpdateDriverForPlugAndPlayDevices?) - tap0901]
Section start 2015/11/10 13:36:43.120
cmd: "C:\Program Files\TAP-Windows\bin\tapinstall.exe" install "C:\Program Files\TAP-Windows\driver\OemVista?.inf" tap0901
dvi: {Update Device Driver - ROOT\NET\0002}
dvi: {Build Driver List} 13:36:43.136
dvi: Searching for hardware ID(s):
dvi: tap0901
sig: {_VERIFY_FILE_SIGNATURE} 13:36:43.136
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)} 13:36:43.167
sig: {_VERIFY_FILE_SIGNATURE} 13:36:43.167
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 0xe0000242: The publisher of an Authenticode(tm) signed catalog has not yet been established as trusted.
sig: {_VERIFY_FILE_SIGNATURE exit(0xe0000242)} 13:36:43.198
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? - 11/05/2014
dvi: Version - 9.0.0.21
dvi: {Build Driver List - exit(0x00000000)} 13:36:43.214
dvi: {DIF_SELECTBESTCOMPATDRV} 13:36:43.214
dvi: Default installer: Enter 13:36:43.214
dvi: {Select Best Driver}
dvi: Class GUID of device changed to: {4d36e972-e325-11ce-bfc1-08002be10318}.
dvi: Selected:
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:36:43.229
ndv: Forcing driver install:
ndv: Inf Name - oemvista.inf
ndv: Driver Date - 11/05/2014
ndv: Driver Version - 9.0.0.21
sto: {Setup Import Driver Package: c:\program files\tap-windows\driver\oemvista.inf} 13:36:43.245
inf: Provider: TAP-Windows Provider V9
inf: Class GUID: {4d36e972-e325-11ce-bfc1-08002be10318}
inf: Driver Version: 11/05/2014,9.00.00.21
inf: Catalog File: tap0901.cat
sto: {Copy Driver Package: c:\program files\tap-windows\driver\oemvista.inf} 13:36:43.261
sto: Driver Package = c:\program files\tap-windows\driver\oemvista.inf
sto: Flags = 0x00000007
sto: Destination = C:\Users\admin\AppData?\Local\Temp\{50ddd1fa-a48b-5141-83ae-b42659d54f73}
sto: Copying driver package files to 'C:\Users\admin\AppData?\Local\Temp\{50ddd1fa-a48b-5141-83ae-b42659d54f73}'.
flq: Copying 'c:\program files\tap-windows\driver\oemvista.inf' to 'C:\Users\admin\AppData?\Local\Temp\{50ddd1fa-a48b-5141-83ae-b42659d54f73}\oemvista.inf'.
flq: Copying 'c:\program files\tap-windows\driver\tap0901.cat' to 'C:\Users\admin\AppData?\Local\Temp\{50ddd1fa-a48b-5141-83ae-b42659d54f73}\tap0901.cat'.
flq: Copying 'c:\program files\tap-windows\driver\tap0901.sys' to 'C:\Users\admin\AppData?\Local\Temp\{50ddd1fa-a48b-5141-83ae-b42659d54f73}\tap0901.sys'.
sto: {Copy Driver Package: exit(0x00000000)} 13:36:43.276
pol: {Driver package policy check} 13:36:43.308
pol: {Driver package policy check - exit(0x00000000)} 13:36:43.308
sto: {Stage Driver Package: C:\Users\admin\AppData?\Local\Temp\{50ddd1fa-a48b-5141-83ae-b42659d54f73}\oemvista.inf} 13:36:43.308
inf: {Query Configurability: C:\Users\admin\AppData?\Local\Temp\{50ddd1fa-a48b-5141-83ae-b42659d54f73}\oemvista.inf} 13:36:43.308
inf: Driver package 'oemvista.inf' is configurable.
inf: {Query Configurability: exit(0x00000000)} 13:36:43.308
flq: Copying 'C:\Users\admin\AppData?\Local\Temp\{50ddd1fa-a48b-5141-83ae-b42659d54f73}\oemvista.inf' to 'C:\WINDOWS\System32\DriverStore?\Temp\{9407284b-8b6f-2348-88d7-ac1b7d0fa27b}\oemvista.inf'.
flq: Copying 'C:\Users\admin\AppData?\Local\Temp\{50ddd1fa-a48b-5141-83ae-b42659d54f73}\tap0901.cat' to 'C:\WINDOWS\System32\DriverStore?\Temp\{9407284b-8b6f-2348-88d7-ac1b7d0fa27b}\tap0901.cat'.
flq: Copying 'C:\Users\admin\AppData?\Local\Temp\{50ddd1fa-a48b-5141-83ae-b42659d54f73}\tap0901.sys' to 'C:\WINDOWS\System32\DriverStore?\Temp\{9407284b-8b6f-2348-88d7-ac1b7d0fa27b}\tap0901.sys'.
sto: {DRIVERSTORE IMPORT VALIDATE} 13:36:43.339
sig: {_VERIFY_FILE_SIGNATURE} 13:36:43.339
sig: Key = oemvista.inf
sig: FilePath? = C:\WINDOWS\System32\DriverStore?\Temp\{9407284b-8b6f-2348-88d7-ac1b7d0fa27b}\oemvista.inf
sig: Catalog = C:\WINDOWS\System32\DriverStore?\Temp\{9407284b-8b6f-2348-88d7-ac1b7d0fa27b}\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)} 13:36:43.355
sig: {_VERIFY_FILE_SIGNATURE} 13:36:43.355
sig: Key = oemvista.inf
sig: FilePath? = C:\WINDOWS\System32\DriverStore?\Temp\{9407284b-8b6f-2348-88d7-ac1b7d0fa27b}\oemvista.inf
sig: Catalog = C:\WINDOWS\System32\DriverStore?\Temp\{9407284b-8b6f-2348-88d7-ac1b7d0fa27b}\tap0901.cat
sig: Success: File is signed in Authenticode(tm) catalog.
sig: Error 0xe0000242: The publisher of an Authenticode(tm) signed catalog has not yet been established as trusted.
sig: {_VERIFY_FILE_SIGNATURE exit(0xe0000242)} 13:36:43.386
! sig: Driver package signer is unknown, but user trusts signer.
sig: Driver package certificate was successfully installed.
sto: {DRIVERSTORE IMPORT VALIDATE: exit(0x00000000)} 13:36:47.955
sig: Signer Score = 0x0F000000
sig: Signer Name = OpenVPN Technologies, Inc.
sto: {DRIVERSTORE IMPORT BEGIN} 13:36:47.955
sto: {DRIVERSTORE IMPORT BEGIN: exit(0x00000000)} 13:36:47.955
cpy: {Copy Directory: C:\WINDOWS\System32\DriverStore?\Temp\{9407284b-8b6f-2348-88d7-ac1b7d0fa27b}} 13:36:47.955
cpy: Target Path = C:\WINDOWS\System32\DriverStore?\FileRepository?\oemvista.inf_amd64_690431ea2d4f48b2
cpy: {Copy Directory: exit(0x00000000)} 13:36:47.955
idb: {Register Driver Package: C:\WINDOWS\System32\DriverStore?\FileRepository?\oemvista.inf_amd64_690431ea2d4f48b2\oemvista.inf} 13:36:47.955
idb: Created driver package object 'oemvista.inf_amd64_690431ea2d4f48b2' in DRIVERS database node.
idb: Created driver INF file object 'oem84.inf' in DRIVERS database node.
idb: Registered driver package 'oemvista.inf_amd64_690431ea2d4f48b2' with 'oem84.inf'.
idb: {Register Driver Package: exit(0x00000000)} 13:36:47.970
idb: {Publish Driver Package: C:\WINDOWS\System32\DriverStore?\FileRepository?\oemvista.inf_amd64_690431ea2d4f48b2\oemvista.inf} 13:36:47.970
idb: Activating driver package 'oemvista.inf_amd64_690431ea2d4f48b2'.
cpy: Published 'oemvista.inf_amd64_690431ea2d4f48b2\oemvista.inf' to 'oem84.inf'.
idb: Indexed 3 device IDs for 'oemvista.inf_amd64_690431ea2d4f48b2'.
sto: Flushed driver database node 'DRIVERS'. Time = 0 ms
sto: Flushed driver database node 'SYSTEM'. Time = 16 ms
idb: {Publish Driver Package: exit(0x00000000)} 13:36:47.986
sto: {DRIVERSTORE IMPORT END} 13:36:47.986
sig: Installed catalog 'tap0901.cat' as 'oem84.cat'.
sto: {DRIVERSTORE IMPORT END: exit(0x00000000)} 13:36:48.017
sto: {Stage Driver Package: exit(0x00000000)} 13:36:48.033
sto: {Setup Import Driver Package - exit (0x00000000)} 13:36:48.033
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\0002}
ndv: Driver INF Path: C:\WINDOWS\INF\oem84.inf
ndv: Driver Node Name: oemvista.inf:3beb73aff103cc24:tap0901.ndi:9.0.0.21:tap0901
ndv: Driver Store Path: C:\WINDOWS\System32\DriverStore?\FileRepository?\oemvista.inf_amd64_690431ea2d4f48b2\oemvista.inf
dvi: Searching for hardware ID(s):
dvi: tap0901
dvi: Class GUID of device changed to: {4d36e972-e325-11ce-bfc1-08002be10318}.
ndv: {Core Device Install} 13:36:48.064
ndv: {Installing device - ROOT\NET\0002} 13:36:48.064
sto: {Configure Driver Package: C:\WINDOWS\System32\DriverStore?\FileRepository?\oemvista.inf_amd64_690431ea2d4f48b2\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: Created new 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_690431ea2d4f48b2\tap0901.sys' to 'C:\WINDOWS\System32\drivers\tap0901.sys'.
dvi: Existing files modified, may need to restart related services.
sto: {Configure Driver Package: exit(0x00000bc3)}
ndv: Restart required for any devices using this driver.
dvi: Install Device: Configuring device (oem84.inf:tap0901,tap0901.ndi). 13:36:48.095
dvi: Install Device: Configuring device completed. 13:36:48.095
dvi: {Restarting Devices} 13:36:48.095
dvi: Restart: ROOT\NET\0002
dvi: {Restarting Devices exit} 13:36:49.424
ndv: {Installing device - exit(0x00000000)} 13:36:49.424
ndv: {Core Device Install - exit(0x00000000)} 13:36:49.424
ndv: Waiting for device post-install to complete. 13:36:49.424
ndv: Device post-install completed. 13:36:49.580
ump: {Plug and Play Service: Device Install exit(00000000)}
ndv: {Update Device Driver - exit(00000000)}
<<< Section end 2015/11/10 13:36:49.611
<<< [Exit status: SUCCESS]
- All other Desktops have failed. No idea why this one, worked.
comment:38 Changed 9 years ago by
In Windows 10 Build 10240 (the version shipped in August 2015) my issue below is NOT reproducible.
In Windows 10 version 1511 Build 10586.0 (the patch shipped November 15, 2015) the issue is ALWAYS reproducible.
I have two machine with build 10586, one upgraded from Windows 8, and another is a fresh install from MSDN. So upgrading is not correlated in my case.
I tested NDIS 6 tap-windows-9.21.1.exe.
Full installer openvpn-install-2.3.8-I601-x86_64.exe have the same issue.
If i install the tap-windows on a fresh install, it works perfectly, without need a reboot.
But if after i uninstall and reinstall (directly, without reboot, uninstall don't ask a reboot),
it hangs for FIVE minute and after throw this error:
http://pastebin.com/Z74uZLzn
and finish with a wrong situation: Device Manager show a 'Unknown device'.
Connecting with OpenVPN GUI throw a 'There are no TAP-Windows adapters on this system.' (i think a full log is useless).
If i relaunch the tap-installer, still hang for FIVE minute and throw the same error.
If i reboot Windows, it detect automatically the 'Unknown device' and OpenVPN GUI start to work, WITHOUT need to relaunch the tap-installer.
It's always reproducible on two machine, please tell me if you need any other informations.
Thanks
Clodo
comment:39 Changed 8 years ago by
I can confirm that what Clodo has reported is being experienced by us with the latest Windows 10 patch.
We have a number of laptops on which the OpenVPN client was installed prior to W10v1511b10585.0, which continue to work fine. However, we have one laptop which was updated to this latest version of Windows 10 on which now the OpenVPN installation times out during the TAP driver installation.
Again as Clodo has reported I see the TAP-V9 device show up under Device Manager, but then switch to Unknown Device after the post-install fail. I will attempt to reboot and see if the adapter shows up properly. However, our usecase is slightly different in that we start openvpn as a Delayed Start service so that the user in the field doesn't require Administrator privileges. OpenVPN-GUI is not used.
The c:\Windows\INF\setupapi.dev.log log file is as reported above, and so I won't repeat. However, I am enclosing a screenshot of the error displayed when attempting a manual installation of tap-windows. A (possible) relevant line might be "UpdateDriverForPlugAndPlayDeviceFailed?, Get Last Error=1460"
comment:41 Changed 8 years ago by
Responding to my own post from a couple of hours ago, I think I may have found at least part of the issue.
Following the instructions at
http://community.openvpn.net/openvpn/wiki/ManagingWindowsTAPDrivers
and from there to:
https://technet.microsoft.com/en-us/library/cc730875.aspx
I found that there were two TAP drivers installed. I used pnputil.exe to remove both, rebooted, and then attempted to install openvpn-install-2.3.8-I601-x86_64, and it installed without a hitch.
Now, I am uncertain how/if this correlates to W10v1511b10586.0.
Now on to testing the OpenVPN service with Delayed Start for non-Administrator users!
comment:42 Changed 8 years ago by
We have the same problem, as we ship openvpn as part or our product. For us it is a showstopper, so I did some investigation what's going on here and would like to share my findings.
First of all, this is not a problem of antivirus or vmware, these are all red herrings. I have tested on Win10 1511 both on clean installed hardware and in VMs, all without any antivirus (except for the oob stuff) and the problem exists on both. Our software exhibits this behaviour when updating, where we do a "devcon remove tap0901" and a "devcon install OemVista?.inf tap0901" in rapid succession. If we do so, we get the 4 minute timeout and the tap adapter is gone. However, everything works if we reboot either inbetween these two devcon calls or afterwards (which is a rather strange behaviour I have never seen before for root enumerated devices such as the openvpn tap adapter). This is why it works for people after some time: They have simply rebooted their boxes in the mean time and the tap adapter either reappears or can be installed successfully. It also works if you start ncpa.cpl and then update. So what I currently do in our software: detect win10 1511, launch "control ncpa.cpl", wait for 10 seconds or so, run "devcon remove tap0901" and "devcon install OemVista?.inf tap0901" and everything works. Not really scientific, but it seems to work in our installer. This ncpa.cpl-thingie kinda reminds me of the hoops I had to go through when using the ndis5 openvpn adapter on Windows 8, where I had to launch ncpa.cpl as part of my ovpn file when connecting to my openvpn server.
Just for the records, this is the call stack in devcon during the 4 minute hang which is followed by the timeout error of UpdateDriverForPlugAndPlayDevices? (ddinstx64.exe is our renamed version of devcon):
ntdll.dllZwWaitForSingleObject() + 0x14 Bytes
KernelBase?.dllWaitForSingleObjectEx() + 0x8f Bytes
cfgmgr32.dll!Local_CM_Install_DevNode() + 0x1fc Bytes
cfgmgr32.dll!CM_Install_DevNodeW() + 0xf4 Bytes
cfgmgr32.dll!CM_Install_DevNode_ExW() + 0xa7 Bytes
newdev.dllInstallSelectedDriverOnDevice() + 0xee Bytes
newdev.dll!pInstallDev() + 0x1b7 Bytes
newdev.dllInstallDev() + 0x2a Bytes
newdev.dll!pInstallDeviceInstanceUpdateDeviceSilent() + 0x226 Bytes
newdev.dllInstallDeviceInstance() + 0x2a6 Bytes
newdev.dllEnumAndUpgradeDevices() + 0x30f Bytes
newdev.dll!UpdateDriverForPlugAndPlayDevicesW() + 0x2b3 Bytes
ddinstx64.exe!cmdUpdate(const wchar_t * BaseName?=0x00000000007156b8, const wchar_t * Machine=0x0000000000000000, unsigned long Flags=0, int argc=2, wchar_t * * argv=0x00000000007156a0) Zeile 1203 + 0x25 Bytes C++
ddinstx64.exe!cmdInstall(const wchar_t * BaseName?=0x00000000007156b8, const wchar_t * Machine=0x0000000000000000, unsigned long Flags=0, int argc=2, wchar_t * * argv=0x00000000007156a0) Zeile 1352 + 0x32 Bytes C++
ddinstx64.exe!wmain(int argc=4, wchar_t * * argv=0x0000000000715690) Zeile 1136 + 0x49 Bytes C++
ddinstx64.exe__wmainCRTStartup() Zeile 690 + 0x19 Bytes C
kernel32.dllBaseThreadInitThunk() + 0x22 Bytes
ntdll.dllRtlUserThreadStart() + 0x34 Bytes
So maybe someone else can jump in and has an idea why launching ncpa.cpl makes things work or what causes this wait operation in the call stack above. I have debugged devcon for these two calls and I cannot see why a reboot should be required, there is no indication for it in the API calls being made in these two calls (UpdateDriverForPlugAndPlayDevices? usually does, but only if it is successful, but in our case it fails entirely). So I guess that this is either a long standing bug in the ndis6 driver that never raised its head until lately or a bug in win10 1511.
HTH,
--
Stefan
comment:43 Changed 8 years ago by
Oh yes, another thing: It doesn't make a difference whether Win 10 1511 is running as installed from the ISO or if the latest patches are applied to 1511. Somewhere someone purportedly had success when applying the latest patches, but I suppose that this just led to a reboot which heals all problems as described above.
HTH,
--
Stefan
comment:44 Changed 8 years ago by
another observation I have made is this: removing the tap adapter driver from the local driver store after the "devcon remove tap0901" doesn't change anything. I also do not think that this has anything to do with the new driver signing policy in Windows 10 because the currently shipping driver has been signed *before* windows 10 has shipped, so the old driver signing rules still apply. It is going to be another thing for the next version of the driver, this will have to be signed using an EV certificate.
comment:45 Changed 8 years ago by
- I have tried the http://community.openvpn.net/openvpn/wiki/ManagingWindowsTAPDrivers
and confirmed there was no additional TAP drivers installed also using pnputil.exe with no change. I still am not able to install TAP driver.
comment:46 Changed 8 years ago by
I am having the same issue, I can confirm that the pnputil to remove the driver from the driverstore doesn't actually fix the problem. It seems that rebooting and trying to install the drivers again sometimes works but not in all cases.
Any update from the developers?
comment:47 Changed 8 years ago by
Ok i have a workaround that seems to work on all Windows 10 1511 systems ive tried this so far on. Remove the NIC and any "Other Device" which are present. Reboot and try again.
We use the TAP driver in our software product and run the tapinstall command directly in the install process which just simply timesout after 5 minutes with an error. Performing the above workaround has worked on all machines experiencing this problem so far.
comment:48 Changed 8 years ago by
I cannot seem to reproduce it anymore with Win 10 build 11082. I did about 5 installs and none of them failed, previously i only had 2/5 actually work. Im wondering what kind of luck you guys have with this build.
This is the insider preview (Fast Ring) build 11082
comment:49 Changed 8 years ago by
I have a simple work around that I have confirmed works on 3 different WIN 10 x64 machines so far that wouldn't install TAP previously. I'm running Kaspersky Small Office Security 4.
- Temporarily disable your antivirus (you don't need to uninstall it)
- Navigate to C:\Users\*CURRENT USER* and open it up
- Go to the "View" tab and click "Options" on the right side
- When the Folder Options window pops up, select the "View" tab
- Select "Show hidden files, folders, and drives
- Uncheck "Hide protect operating system files (Recommended)"
- Hit "Apply" at the bottom
- Run the OpenVPN installer as administrator
- Change everything back
BAM! It will finish installing and will not hang. If you want to live dangerously, you can start the installer first, let it hang, then complete the steps. It will become unstuck as soon as you hit "Apply" button after making the changes.
Have fun :-)
comment:50 Changed 8 years ago by
I am also experiencing the problem on a Windows 8 machine. I have no antivirus software installed. I tried all the methods above. Removed the driver from the driver store using pnputil, it does not help. The TAP driver just does not install.
I am putting my setupapi.dev.log bellow.
[Device Install Log] OS Version = 6.3.9600 Service Pack = 0.0 Suite = 0x0300 ProductType = 1 Architecture = amd64 [BeginLog] [Boot Session: 2016/06/28 10:55:57.486] >>> [Device Install (UpdateDriverForPlugAndPlayDevices) - tap0901] >>> Section start 2016/06/28 11:46:22.459 cmd: tapinstall.exe install "C:\Program Files\TAP-Windows\driver\OemVista.inf" tap0901 dvi: {Update Device Driver - ROOT\NET\0001} dvi: {Build Driver List} 11:46:22.494 dvi: Searching for hardware ID(s): dvi: tap0901 sig: {_VERIFY_FILE_SIGNATURE} 11:46:22.510 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: {_VERIFY_FILE_SIGNATURE exit(0x800b0109)} 11:46:22.588 sig: {_VERIFY_FILE_SIGNATURE} 11:46:22.588 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: {_VERIFY_FILE_SIGNATURE exit(0xe0000241)} 11:46:22.661 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 - 11/05/2014 dvi: Version - 9.0.0.21 dvi: {Build Driver List - exit(0x00000000)} 11:46:22.723 dvi: {DIF_SELECTBESTCOMPATDRV} 11:46:22.723 dvi: Using exported function 'NetClassInstaller' in module 'C:\Windows\system32\NetCfgx.dll'. dvi: Class installer == NetCfgx.dll,NetClassInstaller dvi: Using exported function 'WlanDeviceClassCoInstaller' in module 'C:\Windows\system32\wlaninst.dll'. dvi: CoInstaller 1 == wlaninst.dll,WlanDeviceClassCoInstaller dvi: Using exported function 'WwanDeviceClassCoInstaller' in module 'C:\Windows\system32\wwaninst.dll'. dvi: CoInstaller 2 == wwaninst.dll,WwanDeviceClassCoInstaller dvi: CoInstaller 1: Enter 11:46:22.770 dvi: CoInstaller 1: Exit dvi: CoInstaller 2: Enter 11:46:22.770 dvi: CoInstaller 2: Exit dvi: Class installer: Enter 11:46:22.795 dvi: Class installer: Exit dvi: Default installer: Enter 11:46:22.802 dvi: {Select Best Driver} dvi: Class GUID of device remains: {4d36e972-e325-11ce-bfc1-08002be10318}. dvi: Selected: 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)} 11:46:22.864 ndv: Forcing driver install: ndv: Inf Name - oemvista.inf ndv: Driver Date - 11/05/2014 ndv: Driver Version - 9.0.0.21 sto: {Setup Import Driver Package: c:\program files\tap-windows\driver\oemvista.inf} 11:46:22.896 inf: Provider: TAP-Windows Provider V9 inf: Class GUID: {4d36e972-e325-11ce-bfc1-08002be10318} inf: Driver Version: 11/05/2014,9.00.00.21 inf: Catalog File: tap0901.cat sto: {Copy Driver Package: c:\program files\tap-windows\driver\oemvista.inf} 11:46:22.927 sto: Driver Package = c:\program files\tap-windows\driver\oemvista.inf sto: Flags = 0x00000007 sto: Destination = C:\Users\admin\AppData\Local\Temp\{7d9cab62-0dc3-704b-80aa-5753abc52a64} sto: Copying driver package files to 'C:\Users\admin\AppData\Local\Temp\{7d9cab62-0dc3-704b-80aa-5753abc52a64}'. flq: Copying 'c:\program files\tap-windows\driver\oemvista.inf' to 'C:\Users\admin\AppData\Local\Temp\{7d9cab62-0dc3-704b-80aa-5753abc52a64}\oemvista.inf'. flq: Copying 'c:\program files\tap-windows\driver\tap0901.cat' to 'C:\Users\admin\AppData\Local\Temp\{7d9cab62-0dc3-704b-80aa-5753abc52a64}\tap0901.cat'. flq: Copying 'c:\program files\tap-windows\driver\tap0901.sys' to 'C:\Users\admin\AppData\Local\Temp\{7d9cab62-0dc3-704b-80aa-5753abc52a64}\tap0901.sys'. sto: {Copy Driver Package: exit(0x00000000)} 11:46:22.989 pol: {Driver package policy check} 11:46:23.005 pol: {Driver package policy check - exit(0x00000000)} 11:46:23.005 sto: {Stage Driver Package: C:\Users\admin\AppData\Local\Temp\{7d9cab62-0dc3-704b-80aa-5753abc52a64}\oemvista.inf} 11:46:23.005 inf: {Query Configurability: C:\Users\admin\AppData\Local\Temp\{7d9cab62-0dc3-704b-80aa-5753abc52a64}\oemvista.inf} 11:46:23.005 inf: Driver package 'oemvista.inf' is configurable. inf: {Query Configurability: exit(0x00000000)} 11:46:23.005 flq: Copying 'C:\Users\admin\AppData\Local\Temp\{7d9cab62-0dc3-704b-80aa-5753abc52a64}\oemvista.inf' to 'C:\Windows\System32\DriverStore\Temp\{0cc7c347-fb50-3a42-bc3b-da297636044c}\oemvista.inf'. flq: Copying 'C:\Users\admin\AppData\Local\Temp\{7d9cab62-0dc3-704b-80aa-5753abc52a64}\tap0901.cat' to 'C:\Windows\System32\DriverStore\Temp\{0cc7c347-fb50-3a42-bc3b-da297636044c}\tap0901.cat'. flq: Copying 'C:\Users\admin\AppData\Local\Temp\{7d9cab62-0dc3-704b-80aa-5753abc52a64}\tap0901.sys' to 'C:\Windows\System32\DriverStore\Temp\{0cc7c347-fb50-3a42-bc3b-da297636044c}\tap0901.sys'. sto: {DRIVERSTORE IMPORT VALIDATE} 11:46:23.052 sig: {_VERIFY_FILE_SIGNATURE} 11:46:23.067 sig: Key = oemvista.inf sig: FilePath = C:\Windows\System32\DriverStore\Temp\{0cc7c347-fb50-3a42-bc3b-da297636044c}\oemvista.inf sig: Catalog = C:\Windows\System32\DriverStore\Temp\{0cc7c347-fb50-3a42-bc3b-da297636044c}\tap0901.cat ! sig: Verifying file against specific (valid) catalog failed! (0x800b0109) sig: {_VERIFY_FILE_SIGNATURE exit(0x800b0109)} 11:46:23.114 sig: {_VERIFY_FILE_SIGNATURE} 11:46:23.130 sig: Key = oemvista.inf sig: FilePath = C:\Windows\System32\DriverStore\Temp\{0cc7c347-fb50-3a42-bc3b-da297636044c}\oemvista.inf sig: Catalog = C:\Windows\System32\DriverStore\Temp\{0cc7c347-fb50-3a42-bc3b-da297636044c}\tap0901.cat sig: Success: File is signed in Authenticode(tm) catalog. sig: {_VERIFY_FILE_SIGNATURE exit(0xe0000241)} 11:46:23.177 sto: {DRIVERSTORE IMPORT VALIDATE: exit(0x00000000)} 11:46:23.177 sig: Signer Score = 0x0F000000 sig: Signer Name = OpenVPN Technologies, Inc. sto: {DRIVERSTORE IMPORT BEGIN} 11:46:23.177 sto: {DRIVERSTORE IMPORT BEGIN: exit(0x00000000)} 11:46:23.177 cpy: {Copy Directory: C:\Windows\System32\DriverStore\Temp\{0cc7c347-fb50-3a42-bc3b-da297636044c}} 11:46:23.177 cpy: Target Path = C:\Windows\System32\DriverStore\FileRepository\oemvista.inf_amd64_690431ea2d4f48b2 cpy: {Copy Directory: exit(0x00000000)} 11:46:23.192 idb: {Register Driver Package: C:\Windows\System32\DriverStore\FileRepository\oemvista.inf_amd64_690431ea2d4f48b2\oemvista.inf} 11:46:23.192 idb: Created driver package object 'oemvista.inf_amd64_690431ea2d4f48b2' in DRIVERS database node. idb: Created driver INF file object 'oem20.inf' in DRIVERS database node. idb: Registered driver package 'oemvista.inf_amd64_690431ea2d4f48b2' with 'oem20.inf'. idb: {Register Driver Package: exit(0x00000000)} 11:46:23.192 idb: {Publish Driver Package: C:\Windows\System32\DriverStore\FileRepository\oemvista.inf_amd64_690431ea2d4f48b2\oemvista.inf} 11:46:23.192 idb: Activating driver package 'oemvista.inf_amd64_690431ea2d4f48b2'. cpy: Published 'oemvista.inf_amd64_690431ea2d4f48b2\oemvista.inf' to 'oem20.inf'. idb: Indexed 3 device IDs for 'oemvista.inf_amd64_690431ea2d4f48b2'. idb: {Publish Driver Package: exit(0x00000000)} 11:46:23.208 sto: {DRIVERSTORE IMPORT END} 11:46:23.208 sig: Installed catalog 'tap0901.cat' as 'oem20.cat'. sto: {DRIVERSTORE IMPORT END: exit(0x00000000)} 11:46:23.271 sto: {Stage Driver Package: exit(0x00000000)} 11:46:23.271 sto: {Setup Import Driver Package - exit (0x00000000)} 11:46:23.286 dvi: Searching for hardware ID(s): dvi: tap0901 dvi: Class GUID of device remains: {4d36e972-e325-11ce-bfc1-08002be10318}. dvi: {Plug and Play Service: Device Install for ROOT\NET\0001} ndv: Driver INF Path: C:\Windows\INF\oem20.inf ndv: Driver Node Name: oemvista.inf:3beb73aff103cc24:tap0901.ndi:9.0.0.21:tap0901 ndv: Driver Store Path: C:\Windows\System32\DriverStore\FileRepository\oemvista.inf_amd64_690431ea2d4f48b2\oemvista.inf dvi: Searching for hardware ID(s): dvi: tap0901 dvi: Class GUID of device changed to: {4d36e972-e325-11ce-bfc1-08002be10318}. ndv: {Core Device Install} 11:46:23.333 dvi: {DIF_ALLOW_INSTALL} 11:46:23.364 dvi: Using exported function 'NetClassInstaller' in module 'C:\Windows\system32\NetCfgx.dll'. dvi: Class installer == NetCfgx.dll,NetClassInstaller dvi: Using exported function 'WlanDeviceClassCoInstaller' in module 'C:\Windows\system32\wlaninst.dll'. dvi: CoInstaller 1 == wlaninst.dll,WlanDeviceClassCoInstaller dvi: Using exported function 'WwanDeviceClassCoInstaller' in module 'C:\Windows\system32\wwaninst.dll'. dvi: CoInstaller 2 == wwaninst.dll,WwanDeviceClassCoInstaller dvi: CoInstaller 1: Enter 11:46:23.380 dvi: CoInstaller 1: Exit dvi: CoInstaller 2: Enter 11:46:23.380 dvi: CoInstaller 2: Exit dvi: Class installer: Enter 11:46:23.380 dvi: Class installer: Exit dvi: Default installer: Enter 11:46:23.380 dvi: Default installer: Exit dvi: {DIF_ALLOW_INSTALL - exit(0xe000020e)} 11:46:23.380 dvi: {DIF_INSTALLDEVICEFILES} 11:46:23.396 dvi: CoInstaller 1: Enter 11:46:23.396 dvi: CoInstaller 1: Exit dvi: CoInstaller 2: Enter 11:46:23.396 dvi: CoInstaller 2: Exit dvi: Class installer: Enter 11:46:23.396 dvi: Class installer: Exit dvi: Default installer: Enter 11:46:23.396 ! inf: Empty Section! [tap0901.files] dvi: Default installer: Exit dvi: {DIF_INSTALLDEVICEFILES - exit(0x00000000)} 11:46:23.396 flq: File 'C:\Windows\system32\DRIVERS\tap0901.sys' pruned from copy. ! sig: VerifyTrustFailed for C:\Windows\system32\DRIVERS\tap0901.sys. dvi: {DIF_REGISTER_COINSTALLERS} 11:46:23.505 dvi: CoInstaller 1: Enter 11:46:23.521 dvi: CoInstaller 1: Exit dvi: CoInstaller 2: Enter 11:46:23.521 dvi: CoInstaller 2: Exit dvi: Class installer: Enter 11:46:23.536 dvi: Class installer: Exit dvi: Default installer: Enter 11:46:23.536 dvi: {DIF_DESTROYPRIVATEDATA} 11:46:23.552 dvi: CoInstaller 1: Enter 11:46:23.552 dvi: CoInstaller 1: Exit dvi: CoInstaller 2: Enter 11:46:23.552 dvi: CoInstaller 2: Exit dvi: Class installer: Enter 11:46:23.552 dvi: Class installer: Exit dvi: {DIF_DESTROYPRIVATEDATA - exit(0x00000000)} 11:46:23.552 dvi: Default installer: Exit dvi: {DIF_REGISTER_COINSTALLERS - exit(0x00000000)} 11:46:23.567 dvi: {DIF_INSTALLINTERFACES} 11:46:23.567 dvi: Using exported function 'WlanDeviceClassCoInstaller' in module 'C:\Windows\system32\wlaninst.dll'. dvi: CoInstaller 1 == wlaninst.dll,WlanDeviceClassCoInstaller dvi: Using exported function 'WwanDeviceClassCoInstaller' in module 'C:\Windows\system32\wwaninst.dll'. dvi: CoInstaller 2 == wwaninst.dll,WwanDeviceClassCoInstaller dvi: CoInstaller 1: Enter 11:46:23.583 dvi: CoInstaller 1: Exit dvi: CoInstaller 2: Enter 11:46:23.583 dvi: CoInstaller 2: Exit dvi: Class installer: Enter 11:46:23.583 dvi: Class installer: Exit dvi: Default installer: Enter 11:46:23.583 dvi: Default installer: Exit dvi: {DIF_INSTALLINTERFACES - exit(0x00000000)} 11:46:23.599 dvi: {DIF_INSTALLDEVICE} 11:46:23.599 dvi: CoInstaller 1: Enter 11:46:23.599 dvi: CoInstaller 1: Exit dvi: CoInstaller 2: Enter 11:46:23.599 dvi: CoInstaller 2: Exit dvi: Class installer: Enter 11:46:23.614 dvi: {Install DEVICE} dvi: {Writing Device Properties} dvi: Strong Name=oem20.inf:3beb73aff103cc24:tap0901.ndi:9.0.0.21:tap0901 dvi: {Writing Device Properties - Complete} inf: AddService=tap0901,2,tap0901.service (oemvista.inf line 97) dvi: Add Service: Modified existing service 'tap0901'. dvi: {Install DEVICE exit (0x00000000)} ! dvi: Device restart was skipped (DONOTCALLCONFIGMG). dvi: {DIF_REMOVE} 11:46:23.833 dvi: Using exported function 'NetClassInstaller' in module 'C:\Windows\system32\NetCfgx.dll'. dvi: Class installer == NetCfgx.dll,NetClassInstaller dvi: Using exported function 'WlanDeviceClassCoInstaller' in module 'C:\Windows\system32\wlaninst.dll'. dvi: CoInstaller 1 == wlaninst.dll,WlanDeviceClassCoInstaller dvi: Using exported function 'WwanDeviceClassCoInstaller' in module 'C:\Windows\system32\wwaninst.dll'. dvi: CoInstaller 2 == wwaninst.dll,WwanDeviceClassCoInstaller dvi: CoInstaller 1: Enter 11:46:23.849 dvi: CoInstaller 1: Exit dvi: CoInstaller 2: Enter 11:46:23.849 dvi: CoInstaller 2: Exit dvi: Class installer: Enter 11:46:23.849 dvi: {Remove DEVICE} dvi: InstanceID = 'ROOT\DNI_DNEMP\0000' dvi: Query-and-Remove succeeded dvi: {Remove DEVICE exit (0x00000000)} dvi: Class installer: Exit dvi: {DIF_REMOVE - exit(0x00000000)} 11:46:23.896 dvi: {Build Driver List} 11:46:23.896 dvi: Searching for hardware ID(s): dvi: dni_dnemp dvi: Created Driver Node: dvi: HardwareID - dni_dnemp dvi: InfName - C:\Windows\System32\DriverStore\FileRepository\dne2000m.inf_amd64_402958294a9e4eb3\dne2000m.inf dvi: DevDesc - Deterministic Network Enhancer Miniport dvi: Section - DneMP.ndi.NTamd64 dvi: Rank - 0x00ff0000 dvi: Signer Score - Authenticode dvi: DrvDate - 10/28/2008 dvi: Version - 3.22.4.17992 dvi: {Build Driver List - exit(0x00000000)} 11:46:24.191 dvi: {Select Best Driver} dvi: Class GUID of device changed to: {4d36e972-e325-11ce-bfc1-08002be10318}. dvi: Selected: dvi: Description - [Deterministic Network Enhancer Miniport] dvi: InfFile - [c:\windows\system32\driverstore\filerepository\dne2000m.inf_amd64_402958294a9e4eb3\dne2000m.inf] dvi: Section - [DneMP.ndi.NTamd64] dvi: {Select Best Driver - exit(0x00000000)} dvi: {DIF_REGISTERDEVICE} 11:46:24.207 dvi: Using exported function 'NetClassInstaller' in module 'C:\Windows\system32\NetCfgx.dll'. dvi: Class installer == NetCfgx.dll,NetClassInstaller dvi: Using exported function 'WlanDeviceClassCoInstaller' in module 'C:\Windows\system32\wlaninst.dll'. dvi: CoInstaller 1 == wlaninst.dll,WlanDeviceClassCoInstaller dvi: Using exported function 'WwanDeviceClassCoInstaller' in module 'C:\Windows\system32\wwaninst.dll'. dvi: CoInstaller 2 == wwaninst.dll,WwanDeviceClassCoInstaller dvi: CoInstaller 1: Enter 11:46:24.207 dvi: CoInstaller 1: Exit dvi: CoInstaller 2: Enter 11:46:24.223 dvi: CoInstaller 2: Exit dvi: Class installer: Enter 11:46:24.223 dvi: Class installer: Exit dvi: Default installer: Enter 11:46:24.223 dvi: Default installer: Exit dvi: {DIF_REGISTERDEVICE - exit(0x00000000)} 11:46:24.223 dvi: {DIF_ALLOW_INSTALL} 11:46:24.223 dvi: CoInstaller 1: Enter 11:46:24.223 dvi: CoInstaller 1: Exit dvi: CoInstaller 2: Enter 11:46:24.223 dvi: CoInstaller 2: Exit dvi: Class installer: Enter 11:46:24.239 dvi: Class installer: Exit dvi: Default installer: Enter 11:46:24.239 dvi: Default installer: Exit dvi: {DIF_ALLOW_INSTALL - exit(0xe000020e)} 11:46:24.239 dvi: {DIF_INSTALLDEVICEFILES} 11:46:24.239 dvi: CoInstaller 1: Enter 11:46:24.239 dvi: CoInstaller 1: Exit dvi: CoInstaller 2: Enter 11:46:24.239 dvi: CoInstaller 2: Exit dvi: Class installer: Enter 11:46:24.239 dvi: Class installer: Exit dvi: Default installer: Enter 11:46:24.239 ! inf: Empty Section! [DneMP.CopyFiles.None] dvi: Default installer: Exit dvi: {DIF_INSTALLDEVICEFILES - exit(0x00000000)} 11:46:24.254 dvi: {DIF_REGISTER_COINSTALLERS} 11:46:24.254 dvi: CoInstaller 1: Enter 11:46:24.254 dvi: CoInstaller 1: Exit dvi: CoInstaller 2: Enter 11:46:24.254 dvi: CoInstaller 2: Exit dvi: Class installer: Enter 11:46:24.254 dvi: Class installer: Exit dvi: Default installer: Enter 11:46:24.254 dvi: {DIF_DESTROYPRIVATEDATA} 11:46:24.254 dvi: CoInstaller 1: Enter 11:46:24.271 dvi: CoInstaller 1: Exit dvi: CoInstaller 2: Enter 11:46:24.273 dvi: CoInstaller 2: Exit dvi: Class installer: Enter 11:46:24.276 dvi: Class installer: Exit dvi: {DIF_DESTROYPRIVATEDATA - exit(0x00000000)} 11:46:24.278 dvi: Default installer: Exit dvi: {DIF_REGISTER_COINSTALLERS - exit(0x00000000)} 11:46:24.280 dvi: {DIF_INSTALLINTERFACES} 11:46:24.281 dvi: Using exported function 'WlanDeviceClassCoInstaller' in module 'C:\Windows\system32\wlaninst.dll'. dvi: CoInstaller 1 == wlaninst.dll,WlanDeviceClassCoInstaller dvi: Using exported function 'WwanDeviceClassCoInstaller' in module 'C:\Windows\system32\wwaninst.dll'. dvi: CoInstaller 2 == wwaninst.dll,WwanDeviceClassCoInstaller dvi: CoInstaller 1: Enter 11:46:24.288 dvi: CoInstaller 1: Exit dvi: CoInstaller 2: Enter 11:46:24.291 dvi: CoInstaller 2: Exit dvi: Class installer: Enter 11:46:24.293 dvi: Class installer: Exit dvi: Default installer: Enter 11:46:24.295 dvi: Default installer: Exit dvi: {DIF_INSTALLINTERFACES - exit(0x00000000)} 11:46:24.295 dvi: {DIF_INSTALLDEVICE} 11:46:24.295 dvi: CoInstaller 1: Enter 11:46:24.295 dvi: CoInstaller 1: Exit dvi: CoInstaller 2: Enter 11:46:24.295 dvi: CoInstaller 2: Exit dvi: Class installer: Enter 11:46:24.295 dvi: {Install DEVICE} dvi: {Writing Device Properties} dvi: Strong Name=oem12.inf:53aaf94b0668ddae:DneMP.ndi.NTamd64:3.22.4.17992:dni_dnemp dvi: {Writing Device Properties - Complete} inf: AddService=DNE,0x2,DneMP.NTamd64.AddService (dne2000m.inf line 44) dvi: Add Service: Modified existing service 'DNE'. dvi: {Install DEVICE exit (0x00000000)} ! dvi: Device restart was skipped (DONOTCALLCONFIGMG). dvi: Class installer: Exit dvi: CoInstaller 1: Enter (Post Processing) 11:46:24.389 dvi: CoInstaller 1: Exit (Post Processing) dvi: {DIF_INSTALLDEVICE - exit(0x00000000)} 11:46:24.389 dvi: {Build Driver List} 11:46:24.389 dvi: Searching for hardware ID(s): dvi: dni_dnemp dvi: Created Driver Node: dvi: HardwareID - dni_dnemp dvi: InfName - C:\Windows\System32\DriverStore\FileRepository\dne2000m.inf_amd64_402958294a9e4eb3\dne2000m.inf dvi: DevDesc - Deterministic Network Enhancer Miniport dvi: Section - DneMP.ndi.NTamd64 dvi: Rank - 0x00ff0000 dvi: Signer Score - Authenticode dvi: DrvDate - 10/28/2008 dvi: Version - 3.22.4.17992 dvi: {Build Driver List - exit(0x00000000)} 11:46:24.694 dvi: {Select Best Driver} dvi: Class GUID of device changed to: {4d36e972-e325-11ce-bfc1-08002be10318}. dvi: Selected: dvi: Description - [Deterministic Network Enhancer Miniport] dvi: InfFile - [c:\windows\system32\driverstore\filerepository\dne2000m.inf_amd64_402958294a9e4eb3\dne2000m.inf] dvi: Section - [DneMP.ndi.NTamd64] dvi: {Select Best Driver - exit(0x00000000)} dvi: {DIF_REGISTERDEVICE} 11:46:24.694 dvi: Using exported function 'NetClassInstaller' in module 'C:\Windows\system32\NetCfgx.dll'. dvi: Class installer == NetCfgx.dll,NetClassInstaller dvi: Using exported function 'WlanDeviceClassCoInstaller' in module 'C:\Windows\system32\wlaninst.dll'. dvi: CoInstaller 1 == wlaninst.dll,WlanDeviceClassCoInstaller dvi: Using exported function 'WwanDeviceClassCoInstaller' in module 'C:\Windows\system32\wwaninst.dll'. dvi: CoInstaller 2 == wwaninst.dll,WwanDeviceClassCoInstaller dvi: CoInstaller 1: Enter 11:46:24.709 dvi: CoInstaller 1: Exit dvi: CoInstaller 2: Enter 11:46:24.709 dvi: CoInstaller 2: Exit dvi: Class installer: Enter 11:46:24.709 dvi: Class installer: Exit dvi: Default installer: Enter 11:46:24.709 dvi: Default installer: Exit dvi: {DIF_REGISTERDEVICE - exit(0x00000000)} 11:46:24.725 dvi: {DIF_ALLOW_INSTALL} 11:46:24.725 dvi: CoInstaller 1: Enter 11:46:24.725 dvi: CoInstaller 1: Exit dvi: CoInstaller 2: Enter 11:46:24.725 dvi: CoInstaller 2: Exit dvi: Class installer: Enter 11:46:24.725 dvi: Class installer: Exit dvi: Default installer: Enter 11:46:24.741 dvi: Default installer: Exit dvi: {DIF_ALLOW_INSTALL - exit(0xe000020e)} 11:46:24.741 dvi: {DIF_INSTALLDEVICEFILES} 11:46:24.741 dvi: CoInstaller 1: Enter 11:46:24.741 dvi: CoInstaller 1: Exit dvi: CoInstaller 2: Enter 11:46:24.741 dvi: CoInstaller 2: Exit dvi: Class installer: Enter 11:46:24.741 dvi: Class installer: Exit dvi: Default installer: Enter 11:46:24.741 ! inf: Empty Section! [DneMP.CopyFiles.None] dvi: Default installer: Exit dvi: {DIF_INSTALLDEVICEFILES - exit(0x00000000)} 11:46:24.756 dvi: {DIF_REGISTER_COINSTALLERS} 11:46:24.756 dvi: CoInstaller 1: Enter 11:46:24.756 dvi: CoInstaller 1: Exit dvi: CoInstaller 2: Enter 11:46:24.756 dvi: CoInstaller 2: Exit dvi: Class installer: Enter 11:46:24.756 dvi: Class installer: Exit dvi: Default installer: Enter 11:46:24.756 dvi: {DIF_DESTROYPRIVATEDATA} 11:46:24.756 dvi: CoInstaller 1: Enter 11:46:24.772 dvi: CoInstaller 1: Exit dvi: CoInstaller 2: Enter 11:46:24.774 dvi: CoInstaller 2: Exit dvi: Class installer: Enter 11:46:24.777 dvi: Class installer: Exit dvi: {DIF_DESTROYPRIVATEDATA - exit(0x00000000)} 11:46:24.780 dvi: Default installer: Exit dvi: {DIF_REGISTER_COINSTALLERS - exit(0x00000000)} 11:46:24.783 dvi: {DIF_INSTALLINTERFACES} 11:46:24.784 dvi: Using exported function 'WlanDeviceClassCoInstaller' in module 'C:\Windows\system32\wlaninst.dll'. dvi: CoInstaller 1 == wlaninst.dll,WlanDeviceClassCoInstaller dvi: Using exported function 'WwanDeviceClassCoInstaller' in module 'C:\Windows\system32\wwaninst.dll'. dvi: CoInstaller 2 == wwaninst.dll,WwanDeviceClassCoInstaller dvi: CoInstaller 1: Enter 11:46:24.788 dvi: CoInstaller 1: Exit dvi: CoInstaller 2: Enter 11:46:24.788 dvi: CoInstaller 2: Exit dvi: Class installer: Enter 11:46:24.788 dvi: Class installer: Exit dvi: Default installer: Enter 11:46:24.788 dvi: Default installer: Exit dvi: {DIF_INSTALLINTERFACES - exit(0x00000000)} 11:46:24.788 dvi: {DIF_INSTALLDEVICE} 11:46:24.788 dvi: CoInstaller 1: Enter 11:46:24.804 dvi: CoInstaller 1: Exit dvi: CoInstaller 2: Enter 11:46:24.804 dvi: CoInstaller 2: Exit dvi: Class installer: Enter 11:46:24.804 dvi: {Install DEVICE} dvi: {Writing Device Properties} dvi: Strong Name=oem12.inf:53aaf94b0668ddae:DneMP.ndi.NTamd64:3.22.4.17992:dni_dnemp dvi: {Writing Device Properties - Complete} inf: AddService=DNE,0x2,DneMP.NTamd64.AddService (dne2000m.inf line 44) dvi: Add Service: Modified existing service 'DNE'. dvi: {Install DEVICE exit (0x00000000)} ! dvi: Device restart was skipped (DONOTCALLCONFIGMG). dvi: Class installer: Exit dvi: CoInstaller 1: Enter (Post Processing) 11:46:24.898 dvi: CoInstaller 1: Exit (Post Processing) dvi: {DIF_INSTALLDEVICE - exit(0x00000000)} 11:46:24.898 !!! dvi: Exception encountered while calling Class Installer! !!! dvi: Class installer: failed(0x000003e6)! dvi: CoInstaller 1: Enter (Post Processing) 11:46:24.916 dvi: CoInstaller 1: Exit (Post Processing) dvi: {DIF_INSTALLDEVICE - exit(0x000003e6)} 11:46:24.919 !!! ndv: Error(000003e6) installing device! ! ndv: Queueing up error report since device installation failed... ndv: {Core Device Install - exit(0x000003e6)} 11:46:24.925 dvi: {DIF_DESTROYPRIVATEDATA} 11:46:24.927 dvi: CoInstaller 1: Enter 11:46:24.928 dvi: CoInstaller 1: Exit dvi: CoInstaller 2: Enter 11:46:24.930 dvi: CoInstaller 2: Exit dvi: Class installer: Enter 11:46:24.933 dvi: Class installer: Exit dvi: {DIF_DESTROYPRIVATEDATA - exit(0x00000000)} 11:46:24.935 ump: {Plug and Play Service: Device Install exit(000003e6)} !!! ndv: Device install failed for device. ndv: Installing NULL driver. dvi: {Plug and Play Service: Device Install for ROOT\NET\0001} ! ndv: Installing NULL driver! dvi: {DIF_ALLOW_INSTALL} 11:46:25.052 dvi: Using exported function 'NetClassInstaller' in module 'C:\Windows\system32\NetCfgx.dll'. dvi: Class installer == NetCfgx.dll,NetClassInstaller dvi: Using exported function 'WlanDeviceClassCoInstaller' in module 'C:\Windows\system32\wlaninst.dll'. dvi: CoInstaller 1 == wlaninst.dll,WlanDeviceClassCoInstaller dvi: Using exported function 'WwanDeviceClassCoInstaller' in module 'C:\Windows\system32\wwaninst.dll'. dvi: CoInstaller 2 == wwaninst.dll,WwanDeviceClassCoInstaller dvi: CoInstaller 1: Enter 11:46:25.073 dvi: CoInstaller 1: Exit dvi: CoInstaller 2: Enter 11:46:25.076 dvi: CoInstaller 2: Exit dvi: Class installer: Enter 11:46:25.079 dvi: Class installer: Exit dvi: Default installer: Enter 11:46:25.082 dvi: Default installer: Exit dvi: {DIF_ALLOW_INSTALL - exit(0xe000020e)} 11:46:25.083 dvi: {DIF_REGISTER_COINSTALLERS} 11:46:25.083 dvi: CoInstaller 1: Enter 11:46:25.083 dvi: CoInstaller 1: Exit dvi: CoInstaller 2: Enter 11:46:25.083 dvi: CoInstaller 2: Exit dvi: Class installer: Enter 11:46:25.083 dvi: Class installer: Exit dvi: Default installer: Enter 11:46:25.099 dvi: Default installer: Exit dvi: {DIF_DESTROYPRIVATEDATA} 11:46:25.099 dvi: CoInstaller 1: Enter 11:46:25.099 dvi: CoInstaller 1: Exit dvi: CoInstaller 2: Enter 11:46:25.099 dvi: CoInstaller 2: Exit dvi: Class installer: Enter 11:46:25.099 dvi: Class installer: Exit dvi: {DIF_DESTROYPRIVATEDATA - exit(0x00000000)} 11:46:25.099 dvi: {DIF_REGISTER_COINSTALLERS - exit(0x00000000)} 11:46:25.099 dvi: {DIF_INSTALLDEVICE} 11:46:25.099 dvi: Using exported function 'WlanDeviceClassCoInstaller' in module 'C:\Windows\system32\wlaninst.dll'. dvi: CoInstaller 1 == wlaninst.dll,WlanDeviceClassCoInstaller dvi: Using exported function 'WwanDeviceClassCoInstaller' in module 'C:\Windows\system32\wwaninst.dll'. dvi: CoInstaller 2 == wwaninst.dll,WwanDeviceClassCoInstaller dvi: CoInstaller 1: Enter 11:46:25.115 dvi: CoInstaller 1: Exit dvi: CoInstaller 2: Enter 11:46:25.115 dvi: CoInstaller 2: Exit dvi: Class installer: Enter 11:46:25.115 dvi: {DIF_REMOVE} 11:46:25.115 dvi: CoInstaller 1: Enter 11:46:25.115 dvi: CoInstaller 1: Exit dvi: CoInstaller 2: Enter 11:46:25.130 dvi: CoInstaller 2: Exit dvi: Class installer: Enter 11:46:25.130 dvi: {Remove DEVICE} dvi: InstanceID = 'ROOT\NET\0001' dvi: Query-and-Remove succeeded dvi: {Remove DEVICE exit (0x00000000)} dvi: {DIF_REMOVE} 11:46:25.284 dvi: Using exported function 'NetClassInstaller' in module 'C:\Windows\system32\NetCfgx.dll'. dvi: Class installer == NetCfgx.dll,NetClassInstaller dvi: Using exported function 'WlanDeviceClassCoInstaller' in module 'C:\Windows\system32\wlaninst.dll'. dvi: CoInstaller 1 == wlaninst.dll,WlanDeviceClassCoInstaller dvi: Using exported function 'WwanDeviceClassCoInstaller' in module 'C:\Windows\system32\wwaninst.dll'. dvi: CoInstaller 2 == wwaninst.dll,WwanDeviceClassCoInstaller dvi: CoInstaller 1: Enter 11:46:25.284 dvi: CoInstaller 1: Exit dvi: CoInstaller 2: Enter 11:46:25.284 dvi: CoInstaller 2: Exit dvi: Class installer: Enter 11:46:25.284 dvi: {Remove DEVICE} dvi: InstanceID = 'ROOT\DNI_DNEMP\0000' dvi: Query-and-Remove succeeded dvi: {Remove DEVICE exit (0x00000000)} dvi: Class installer: Exit dvi: {DIF_REMOVE - exit(0x00000000)} 11:46:25.316 dvi: {DIF_REMOVE} 11:46:25.316 dvi: Using exported function 'NetClassInstaller' in module 'C:\Windows\system32\NetCfgx.dll'. dvi: Class installer == NetCfgx.dll,NetClassInstaller dvi: Using exported function 'WlanDeviceClassCoInstaller' in module 'C:\Windows\system32\wlaninst.dll'. dvi: CoInstaller 1 == wlaninst.dll,WlanDeviceClassCoInstaller dvi: Using exported function 'WwanDeviceClassCoInstaller' in module 'C:\Windows\system32\wwaninst.dll'. dvi: CoInstaller 2 == wwaninst.dll,WwanDeviceClassCoInstaller dvi: CoInstaller 1: Enter 11:46:25.316 dvi: CoInstaller 1: Exit dvi: CoInstaller 2: Enter 11:46:25.331 dvi: CoInstaller 2: Exit dvi: Class installer: Enter 11:46:25.331 dvi: {Remove DEVICE} dvi: InstanceID = 'ROOT\DNI_DNEMP\0001' dvi: Query-and-Remove succeeded dvi: {Remove DEVICE exit (0x00000000)} dvi: Class installer: Exit dvi: {DIF_REMOVE - exit(0x00000000)} 11:46:25.347 dvi: {Build Driver List} 11:46:25.347 dvi: Searching for hardware ID(s): dvi: dni_dnemp dvi: Created Driver Node: dvi: HardwareID - dni_dnemp dvi: InfName - C:\Windows\System32\DriverStore\FileRepository\dne2000m.inf_amd64_402958294a9e4eb3\dne2000m.inf dvi: DevDesc - Deterministic Network Enhancer Miniport dvi: Section - DneMP.ndi.NTamd64 dvi: Rank - 0x00ff0000 dvi: Signer Score - Authenticode dvi: DrvDate - 10/28/2008 dvi: Version - 3.22.4.17992 dvi: {Build Driver List - exit(0x00000000)} 11:46:25.615 dvi: {Select Best Driver} dvi: Class GUID of device changed to: {4d36e972-e325-11ce-bfc1-08002be10318}. dvi: Selected: dvi: Description - [Deterministic Network Enhancer Miniport] dvi: InfFile - [c:\windows\system32\driverstore\filerepository\dne2000m.inf_amd64_402958294a9e4eb3\dne2000m.inf] dvi: Section - [DneMP.ndi.NTamd64] dvi: {Select Best Driver - exit(0x00000000)} dvi: {DIF_REGISTERDEVICE} 11:46:25.644 dvi: Using exported function 'NetClassInstaller' in module 'C:\Windows\system32\NetCfgx.dll'. dvi: Class installer == NetCfgx.dll,NetClassInstaller dvi: Using exported function 'WlanDeviceClassCoInstaller' in module 'C:\Windows\system32\wlaninst.dll'. dvi: CoInstaller 1 == wlaninst.dll,WlanDeviceClassCoInstaller dvi: Using exported function 'WwanDeviceClassCoInstaller' in module 'C:\Windows\system32\wwaninst.dll'. dvi: CoInstaller 2 == wwaninst.dll,WwanDeviceClassCoInstaller dvi: CoInstaller 1: Enter 11:46:25.646 dvi: CoInstaller 1: Exit dvi: CoInstaller 2: Enter 11:46:25.646 dvi: CoInstaller 2: Exit dvi: Class installer: Enter 11:46:25.662 dvi: Class installer: Exit dvi: Default installer: Enter 11:46:25.662 dvi: Default installer: Exit dvi: {DIF_REGISTERDEVICE - exit(0x00000000)} 11:46:25.662 dvi: {DIF_ALLOW_INSTALL} 11:46:25.662 dvi: CoInstaller 1: Enter 11:46:25.662 dvi: CoInstaller 1: Exit dvi: CoInstaller 2: Enter 11:46:25.662 dvi: CoInstaller 2: Exit dvi: Class installer: Enter 11:46:25.662 dvi: Class installer: Exit dvi: Default installer: Enter 11:46:25.678 dvi: Default installer: Exit dvi: {DIF_ALLOW_INSTALL - exit(0xe000020e)} 11:46:25.678 dvi: {DIF_INSTALLDEVICEFILES} 11:46:25.678 dvi: CoInstaller 1: Enter 11:46:25.678 dvi: CoInstaller 1: Exit dvi: CoInstaller 2: Enter 11:46:25.678 dvi: CoInstaller 2: Exit dvi: Class installer: Enter 11:46:25.678 dvi: Class installer: Exit dvi: Default installer: Enter 11:46:25.678 ! inf: Empty Section! [DneMP.CopyFiles.None] dvi: Default installer: Exit dvi: {DIF_INSTALLDEVICEFILES - exit(0x00000000)} 11:46:25.693 dvi: {DIF_REGISTER_COINSTALLERS} 11:46:25.693 dvi: CoInstaller 1: Enter 11:46:25.693 dvi: CoInstaller 1: Exit dvi: CoInstaller 2: Enter 11:46:25.693 dvi: CoInstaller 2: Exit dvi: Class installer: Enter 11:46:25.693 dvi: Class installer: Exit dvi: Default installer: Enter 11:46:25.693 dvi: {DIF_DESTROYPRIVATEDATA} 11:46:25.693 dvi: CoInstaller 1: Enter 11:46:25.693 dvi: CoInstaller 1: Exit dvi: CoInstaller 2: Enter 11:46:25.693 dvi: CoInstaller 2: Exit dvi: Class installer: Enter 11:46:25.709 dvi: Class installer: Exit dvi: {DIF_DESTROYPRIVATEDATA - exit(0x00000000)} 11:46:25.711 dvi: Default installer: Exit dvi: {DIF_REGISTER_COINSTALLERS - exit(0x00000000)} 11:46:25.714 dvi: {DIF_INSTALLINTERFACES} 11:46:25.715 dvi: Using exported function 'WlanDeviceClassCoInstaller' in module 'C:\Windows\system32\wlaninst.dll'. dvi: CoInstaller 1 == wlaninst.dll,WlanDeviceClassCoInstaller dvi: Using exported function 'WwanDeviceClassCoInstaller' in module 'C:\Windows\system32\wwaninst.dll'. dvi: CoInstaller 2 == wwaninst.dll,WwanDeviceClassCoInstaller dvi: CoInstaller 1: Enter 11:46:25.723 dvi: CoInstaller 1: Exit dvi: CoInstaller 2: Enter 11:46:25.725 dvi: CoInstaller 2: Exit dvi: Class installer: Enter 11:46:25.727 dvi: Class installer: Exit dvi: Default installer: Enter 11:46:25.728 dvi: Default installer: Exit dvi: {DIF_INSTALLINTERFACES - exit(0x00000000)} 11:46:25.728 dvi: {DIF_INSTALLDEVICE} 11:46:25.728 dvi: CoInstaller 1: Enter 11:46:25.728 dvi: CoInstaller 1: Exit dvi: CoInstaller 2: Enter 11:46:25.728 dvi: CoInstaller 2: Exit dvi: Class installer: Enter 11:46:25.728 dvi: {Install DEVICE} dvi: {Writing Device Properties} dvi: Strong Name=oem12.inf:53aaf94b0668ddae:DneMP.ndi.NTamd64:3.22.4.17992:dni_dnemp dvi: {Writing Device Properties - Complete} inf: AddService=DNE,0x2,DneMP.NTamd64.AddService (dne2000m.inf line 44) dvi: Add Service: Modified existing service 'DNE'. dvi: {Install DEVICE exit (0x00000000)} ! dvi: Device restart was skipped (DONOTCALLCONFIGMG). dvi: Class installer: Exit dvi: CoInstaller 1: Enter (Post Processing) 11:46:25.837 dvi: CoInstaller 1: Exit (Post Processing) dvi: {DIF_INSTALLDEVICE - exit(0x00000000)} 11:46:25.837 !!! dvi: Exception encountered while calling Class Installer! !!! dvi: Class installer: failed(0x000003e6)! dvi: {DIF_REMOVE - exit(0x000003e6)} 11:46:25.837 dvi: Class installer: Exit dvi: Default installer: Enter 11:46:25.837 !!! dvi: Error obtaining device ID! !!! dvi: Cleaning up failed installation (00000006) ! dvi: Failed to set Config Flags property: 0x00000020 !!! dvi: Default installer: failed! dvi: {DIF_INSTALLDEVICE - exit(0x00000006)} 11:46:25.855 dvi: {DIF_DESTROYPRIVATEDATA} 11:46:25.857 dvi: CoInstaller 1: Enter 11:46:25.858 dvi: CoInstaller 1: Exit dvi: CoInstaller 2: Enter 11:46:25.860 dvi: CoInstaller 2: Exit dvi: Class installer: Enter 11:46:25.863 dvi: Class installer: Exit dvi: {DIF_DESTROYPRIVATEDATA - exit(0x00000000)} 11:46:25.865 ump: {Plug and Play Service: Device Install exit(00000006)} ndv: {Update Device Driver - exit(000003e6)} !!! ndv: Failed to install device instance ROOT\NET\0001 (Error 0x000003e6) dvi: {DIF_DESTROYPRIVATEDATA} 11:46:25.890 dvi: CoInstaller 1: Enter 11:46:25.894 dvi: CoInstaller 1: Exit dvi: CoInstaller 2: Enter 11:46:25.894 dvi: CoInstaller 2: Exit dvi: Class installer: Enter 11:46:25.910 dvi: Class installer: Exit dvi: {DIF_DESTROYPRIVATEDATA - exit(0x00000000)} 11:46:25.926 <<< Section end 2016/06/28 11:46:25.926 <<< [Exit status: FAILURE(0x000003e6)]
comment:51 Changed 8 years ago by
Can this be reproduced with tap-windows-9.21.2? That version is included in latest openvpn Windows installer releases, such as 2.3.12.
comment:52 Changed 7 years ago by
Hello, I've been having the same problem since yesterday, while trying to update the TAP driver.
The following is from the setupapi.dev.log.
[Device Install Log] OS Version = 10.0.14393 Service Pack = 0.0 Suite = 0x0300 ProductType = 1 Architecture = amd64 [BeginLog] >>> [Device Install (UpdateDriverForPlugAndPlayDevices) - tap0901] >>> Section start 2016/12/01 22:40:38.031 cmd: 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} 22:55:43.889 dvi: Searching for hardware ID(s): dvi: tap0901 sig: {_VERIFY_FILE_SIGNATURE} 22:55:43.889 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)} 22:55:43.905 sig: {_VERIFY_FILE_SIGNATURE} 22:55:43.905 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)} 22:55:43.920 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)} 22:55:43.920 dvi: {DIF_SELECTBESTCOMPATDRV} 22:55:43.920 dvi: Default installer: Enter 22:55:43.920 dvi: {Select Best Driver} dvi: Class GUID of device changed to: {4d36e972-e325-11ce-bfc1-08002be10318}. dvi: Selected: 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)} 22:55:43.920 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} 22:55:43.920 inf: Provider: TAP-Windows Provider V9 inf: Class GUID: {4d36e972-e325-11ce-bfc1-08002be10318} inf: Driver Version: 04/21/2016,9.00.00.21 inf: Catalog File: tap0901.cat sto: {Copy Driver Package: c:\program files\tap-windows\driver\oemvista.inf} 22:55:43.920 sto: Driver Package = c:\program files\tap-windows\driver\oemvista.inf sto: Flags = 0x00000007 sto: Destination = C:\Users\Minwoo\AppData\Local\Temp\{88e224b7-d71a-0c41-92ae-62237bbd7658} sto: Copying driver package files to 'C:\Users\Minwoo\AppData\Local\Temp\{88e224b7-d71a-0c41-92ae-62237bbd7658}'. flq: Copying 'c:\program files\tap-windows\driver\oemvista.inf' to 'C:\Users\Minwoo\AppData\Local\Temp\{88e224b7-d71a-0c41-92ae-62237bbd7658}\oemvista.inf'. flq: Copying 'c:\program files\tap-windows\driver\tap0901.cat' to 'C:\Users\Minwoo\AppData\Local\Temp\{88e224b7-d71a-0c41-92ae-62237bbd7658}\tap0901.cat'. flq: Copying 'c:\program files\tap-windows\driver\tap0901.sys' to 'C:\Users\Minwoo\AppData\Local\Temp\{88e224b7-d71a-0c41-92ae-62237bbd7658}\tap0901.sys'. sto: {Copy Driver Package: exit(0x00000000)} 22:55:43.936 pol: {Driver package policy check} 22:55:43.936 pol: {Driver package policy check - exit(0x00000000)} 22:55:43.936 sto: {Stage Driver Package: C:\Users\Minwoo\AppData\Local\Temp\{88e224b7-d71a-0c41-92ae-62237bbd7658}\oemvista.inf} 22:55:43.936 inf: {Query Configurability: C:\Users\Minwoo\AppData\Local\Temp\{88e224b7-d71a-0c41-92ae-62237bbd7658}\oemvista.inf} 22:55:43.936 inf: Driver package 'oemvista.inf' is configurable. inf: {Query Configurability: exit(0x00000000)} 22:55:43.936 flq: Copying 'C:\Users\Minwoo\AppData\Local\Temp\{88e224b7-d71a-0c41-92ae-62237bbd7658}\oemvista.inf' to 'C:\WINDOWS\System32\DriverStore\Temp\{90dfe2ff-b695-f54b-9154-19025d36f15a}\oemvista.inf'. flq: Copying 'C:\Users\Minwoo\AppData\Local\Temp\{88e224b7-d71a-0c41-92ae-62237bbd7658}\tap0901.cat' to 'C:\WINDOWS\System32\DriverStore\Temp\{90dfe2ff-b695-f54b-9154-19025d36f15a}\tap0901.cat'. flq: Copying 'C:\Users\Minwoo\AppData\Local\Temp\{88e224b7-d71a-0c41-92ae-62237bbd7658}\tap0901.sys' to 'C:\WINDOWS\System32\DriverStore\Temp\{90dfe2ff-b695-f54b-9154-19025d36f15a}\tap0901.sys'. sto: {DRIVERSTORE IMPORT VALIDATE} 22:55:43.936 sig: {_VERIFY_FILE_SIGNATURE} 22:55:43.951 sig: Key = oemvista.inf sig: FilePath = C:\WINDOWS\System32\DriverStore\Temp\{90dfe2ff-b695-f54b-9154-19025d36f15a}\oemvista.inf sig: Catalog = C:\WINDOWS\System32\DriverStore\Temp\{90dfe2ff-b695-f54b-9154-19025d36f15a}\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)} 22:55:43.967 sig: {_VERIFY_FILE_SIGNATURE} 22:55:43.967 sig: Key = oemvista.inf sig: FilePath = C:\WINDOWS\System32\DriverStore\Temp\{90dfe2ff-b695-f54b-9154-19025d36f15a}\oemvista.inf sig: Catalog = C:\WINDOWS\System32\DriverStore\Temp\{90dfe2ff-b695-f54b-9154-19025d36f15a}\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)} 22:55:43.983 sto: {DRIVERSTORE IMPORT VALIDATE: exit(0x00000000)} 22:55:43.983 sig: Signer Score = 0x0F000000 sig: Signer Name = OpenVPN Technologies, Inc. sto: {DRIVERSTORE IMPORT BEGIN} 22:55:43.983 sto: {DRIVERSTORE IMPORT BEGIN: exit(0x00000000)} 22:55:43.983 cpy: {Copy Directory: C:\WINDOWS\System32\DriverStore\Temp\{90dfe2ff-b695-f54b-9154-19025d36f15a}} 22:55:43.983 cpy: Target Path = C:\WINDOWS\System32\DriverStore\FileRepository\oemvista.inf_amd64_a572b7f20c402d28 cpy: {Copy Directory: exit(0x00000000)} 22:55:43.983 idb: {Register Driver Package: C:\WINDOWS\System32\DriverStore\FileRepository\oemvista.inf_amd64_a572b7f20c402d28\oemvista.inf} 22:55:43.983 idb: Created driver package object 'oemvista.inf_amd64_a572b7f20c402d28' in DRIVERS database node. idb: Created driver INF file object 'oem14.inf' in DRIVERS database node. idb: Registered driver package 'oemvista.inf_amd64_a572b7f20c402d28' with 'oem14.inf'. idb: {Register Driver Package: exit(0x00000000)} 22:55:43.983 idb: {Publish Driver Package: C:\WINDOWS\System32\DriverStore\FileRepository\oemvista.inf_amd64_a572b7f20c402d28\oemvista.inf} 22:55:43.983 idb: Activating driver package 'oemvista.inf_amd64_a572b7f20c402d28'. cpy: Published 'oemvista.inf_amd64_a572b7f20c402d28\oemvista.inf' to 'oem14.inf'. idb: Indexed 3 device IDs for 'oemvista.inf_amd64_a572b7f20c402d28'. sto: Flushed driver database node 'DRIVERS'. Time = 62 ms sto: Flushed driver database node 'SYSTEM'. Time = 32 ms idb: {Publish Driver Package: exit(0x00000000)} 22:55:44.080 sto: {DRIVERSTORE IMPORT END} 22:55:44.080 dvi: Flushed all driver package files to disk. Time = 46 ms sig: Installed catalog 'tap0901.cat' as 'oem14.cat'. sto: {DRIVERSTORE IMPORT END: exit(0x00000000)} 22:55:44.142 sto: {Stage Driver Package: exit(0x00000000)} 22:55:44.142 sto: {Setup Import Driver Package - exit (0x00000000)} 22:55:44.158 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} ndv: Driver INF Path: C:\WINDOWS\INF\oem14.inf ndv: Driver Node Name: oemvista.inf:3beb73aff103cc24:tap0901.ndi:9.0.0.21:tap0901 ndv: 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}. ndv: {Core Device Install} 22:55:44.158 ndv: {Install Device - ROOT\NET\0000} 22:55:44.158 ndv: Parent device: HTREE\ROOT\0 ndv: {Configure Device - ROOT\NET\0000} 22:55:44.158 ndv: 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 (oem14.inf:tap0901,tap0901.ndi). 22:55:44.174 dvi: Install Device: Configuring device completed. 22:55:44.174 dvi: Install Device: Starting device. 22:55:44.174 dvi: Install Device: Starting device completed. 22:55:44.252 ndv: {Configure Device - exit(0x00000000)} 22:55:44.252 ndv: {Install Device - exit(0x00000000)} 22:55:44.252 ndv: {Core Device Install - exit(0x00000000)} 22:55:44.252 ndv: Waiting for device post-install to complete. 22:55:44.252 !!! ndv: Timed out waiting for device post-install to complete. 22:59:44.261 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\0000} ! ndv: Installing NULL driver! dvi: {DIF_ALLOW_INSTALL} 22:59:44.777 dvi: Default installer: Enter 22:59:44.777 dvi: Default installer: Exit dvi: {DIF_ALLOW_INSTALL - exit(0xe000020e)} 22:59:44.777 dvi: {DIF_REGISTER_COINSTALLERS} 22:59:44.777 dvi: Default installer: Enter 22:59:44.777 dvi: Default installer: Exit dvi: {DIF_REGISTER_COINSTALLERS - exit(0x00000000)} 22:59:44.777 dvi: {DIF_INSTALLDEVICE} 22:59:44.777 dvi: Default installer: Enter 22:59:44.777 ! dvi: Installing NULL driver! dvi: Install Null Driver: Removing device sub-tree. 22:59:44.777 dvi: Install Null Driver: Removing device sub-tree completed. 22:59:44.824 dvi: Install Null Driver: Restarting device. 22:59:44.824 dvi: Install Null Driver: Restarting device completed. 22:59:44.886 dvi: Install Device: Configuring device class. 22:59:44.886 dvi: Install Device: Configuring device class completed. 22:59:44.886 dvi: Install Device: Starting device. 22:59:44.886 dvi: Install Device: Starting device completed. 22:59:44.933 dvi: Default installer: Exit dvi: {DIF_INSTALLDEVICE - exit(0x00000000)} 22:59:44.933 ump: {Plug and Play Service: Device Install exit(00000000)} ndv: {Update Device Driver - exit(000005b4)} !!! ndv: Failed to install device instance 'ROOT\NET\0000'. Error = 0x000005b4 <<< Section end 2016/12/01 22:59:44.933 <<< [Exit status: FAILURE(0x000005b4)]
I've tried most of the solutions that are out there regarding this, including:
running as admin
deleting and reinstalling
editing the registry
disabling antivirus
installing in safe mode
removing driver with pnputil and trying to reinstall
This is Windows 10, 64 bit, and occurred while trying to install with tap-windows-9.21.2 installer.
comment:53 Changed 7 years ago by
Since a week ago, I try to install the TAP driver, oem121.inf, Version 9.0.0.21, at my win10 system.
Win10 has been upgraded from Win7 in July this year.
I have installed TightVNC
I checked registry, no entry of the TAP driver can be found in
HKEY_LOCAL_MACHINE\SYSTEM\Control\Class\{4d36r972...\0000 ... 0012
I tried a lot of things, similar to mandu1021.
- reboot, secure mode, shut down and start
- uninstall/install TAP driver as administrator
- delete content of Users/administrator/AppData/Local/Temp
- pnputil.exe -d oem121.inf
- tried 32bit Version and TAP windows 9.9.2 as well, same bug
Content of C:\Windows\INF\setupapi.dev.log follows
[Boot Session: 2016/12/04 14:41:23.491]
[Device Install (UpdateDriverForPlugAndPlayDevices?) - tap0901]
Section start 2016/12/04 14:44:29.403
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}
dvi: Set selected driver complete.
ndv: Search options: 0x00000080
ndv: Searching single INF 'C:\Program Files\TAP-Windows\driver\OemVista?.inf'
dvi: {Build Driver List} 14:44:29.434
dvi: Searching for hardware ID(s):
dvi: tap0901
dvi: Processing a single INF: 'c:\program files\tap-windows\driver\oemvista.inf'
inf: Opened INF: 'c:\program files\tap-windows\driver\oemvista.inf' ([strings])
sig: {_VERIFY_FILE_SIGNATURE} 14:44:29.466
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: {_VERIFY_FILE_SIGNATURE exit(0x800b0109)} 14:44:29.528
sig: {_VERIFY_FILE_SIGNATURE} 14:44:29.528
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: {_VERIFY_FILE_SIGNATURE exit(0xe0000241)} 14:44:29.575
dvi: Created Driver Node:
dvi: HardwareID - tap0901
dvi: InfName? - c:\program files\tap-windows\driver\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: {Build Driver List - exit(0x00000000)} 14:44:29.622
dvi: {DIF_SELECTBESTCOMPATDRV} 14:44:29.638
dvi: Looking for class installer for 'Netzwerkadapter'...
dvi: No class installer for 'Netzwerkadapter'
dvi: Looking for co-installer modules for 'Netzwerkadapter'.
dvi: No CoInstallers? found
dvi: Default installer: Enter 14:44:29.653
dvi: {Select Best Driver}
dvi: Selected driver installs from section [tap0901.ndi] in 'c:\program files\tap-windows\driver\oemvista.inf'.
dvi: Class GUID of device changed to: {4d36e972-e325-11ce-bfc1-08002be10318}.
dvi: Set selected driver complete.
dvi: Selected:
dvi: Description - [TAP-Windows Adapter V9]
dvi: InfFile? - [c:\program files\tap-windows\driver\oemvista.inf]
dvi: Section - [tap0901.ndi]
dvi: Signer - [OpenVPN Technologies, Inc.]
dvi: Rank - [0x00ff0000]
dvi: {Select Best Driver - exit(0x00000000)}
dvi: Default installer: Exit
dvi: {DIF_SELECTBESTCOMPATDRV - exit(0x00000000)} 14:44:29.700
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} 14:44:29.716
inf: Opened INF: 'c:\program files\tap-windows\driver\oemvista.inf' ([strings])
inf: Provider: TAP-Windows Provider V9
inf: Class GUID: {4d36e972-e325-11ce-bfc1-08002be10318}
inf: Driver Version: 04/21/2016,9.00.00.21
inf: Catalog File: tap0901.cat
sto: {Copy Driver Package: c:\program files\tap-windows\driver\oemvista.inf} 14:44:29.731
sto: Driver Package = c:\program files\tap-windows\driver\oemvista.inf
sto: Flags = 0x00000007
sto: Destination = C:\Users\ADMINI~1\AppData?\Local\Temp\{58ad0f87-1d83-1e4b-a7f9-51457acc4f11}
sto: Copying driver package files to 'C:\Users\ADMINI~1\AppData?\Local\Temp\{58ad0f87-1d83-1e4b-a7f9-51457acc4f11}'.
inf: Opened INF: 'c:\program files\tap-windows\driver\oemvista.inf' ([strings])
inf: Opened INF: 'c:\program files\tap-windows\driver\oemvista.inf' ([strings])
flq: {FILE_QUEUE_COPY}
flq: CopyStyle? - 0x00000000
flq: SourceRootPath? - 'c:\program files\tap-windows\driver'
flq: SourceFilename? - 'oemvista.inf'
flq: TargetDirectory?- 'C:\Users\ADMINI~1\AppData?\Local\Temp\{58ad0f87-1d83-1e4b-a7f9-51457acc4f11}'
flq: {FILE_QUEUE_COPY exit(0x00000000)}
flq: {FILE_QUEUE_COPY}
flq: CopyStyle? - 0x00000000
flq: SourceRootPath? - 'c:\program files\tap-windows\driver'
flq: SourceFilename? - 'tap0901.cat'
flq: TargetDirectory?- 'C:\Users\ADMINI~1\AppData?\Local\Temp\{58ad0f87-1d83-1e4b-a7f9-51457acc4f11}'
flq: {FILE_QUEUE_COPY exit(0x00000000)}
flq: {FILE_QUEUE_COPY}
flq: CopyStyle? - 0x00000000
flq: SourceRootPath? - 'c:\program files\tap-windows\driver'
flq: SourceFilename? - 'tap0901.sys'
flq: TargetDirectory?- 'C:\Users\ADMINI~1\AppData?\Local\Temp\{58ad0f87-1d83-1e4b-a7f9-51457acc4f11}'
flq: SourceDesc? - 'tap0901.sys'
flq: SourceTagfile? - 'tap0901.sys'
flq: {FILE_QUEUE_COPY exit(0x00000000)}
flq: {FILE_QUEUE_COMMIT} 14:44:29.841
flq: {SPFQNOTIFY_STARTQUEUE}
flq: {SPFQNOTIFY_STARTQUEUE - returned 0x00000001}
flq: {FILE_QUEUE_COMMIT_COPY_SUBQUEUE}
flq: {SPFQNOTIFY_STARTSUBQUEUE}
flq: {SPFQNOTIFY_STARTSUBQUEUE - returned 0x00000001}
flq: Source Media:
flq: SourcePath? - [c:\program files\tap-windows\driver]
flq: SourceFile? - [oemvista.inf]
flq: Flags - 0x00000000
flq: Commit: skip NEEDMEDIA (non-interactive)
flq: {FILE_QUEUE_COMMIT_COPY_FILE}
flq: {FILE_QUEUE_UNWIND_BACKUP}
flq: C:\Users\ADMINI~1\AppData?\Local\Temp\{58ad0f87-1d83-1e4b-a7f9-51457acc4f11}\oemvista.inf
flq: {FILE_QUEUE_UNWIND_BACKUP exit OK}
flq: {SPFQNOTIFY_STARTCOPY}
flq: {SPFQNOTIFY_STARTCOPY - returned 0x00000001}
flq: Copying 'c:\program files\tap-windows\driver\oemvista.inf' to 'C:\Users\ADMINI~1\AppData?\Local\Temp\{58ad0f87-1d83-1e4b-a7f9-51457acc4f11}\oemvista.inf'.
flq: CopyFile?: 'c:\program files\tap-windows\driver\oemvista.inf' to 'C:\Users\ADMINI~1\AppData?\Local\Temp\{58ad0f87-1d83-1e4b-a7f9-51457acc4f11}\SETD8D2.tmp'
flq: {SPFQNOTIFY_PREPARECOPY}
flq: {SPFQNOTIFY_PREPARECOPY - returned 0x00000005}
flq: MoveFile?: 'C:\Users\ADMINI~1\AppData?\Local\Temp\{58ad0f87-1d83-1e4b-a7f9-51457acc4f11}\SETD8D2.tmp' to 'C:\Users\ADMINI~1\AppData?\Local\Temp\{58ad0f87-1d83-1e4b-a7f9-51457acc4f11}\oemvista.inf'
flq: {SPFQNOTIFY_FILECOPIED}
flq: {SPFQNOTIFY_FILECOPIED - returned 0x00000005}
flq: {SPFQNOTIFY_FINISHCOPY}
flq: {SPFQNOTIFY_FINISHCOPY - returned 0x00000005}
flq: {SPFQNOTIFY_ENDCOPY}
flq: {SPFQNOTIFY_ENDCOPY - returned 0x00000005}
flq: {FILE_QUEUE_COMMIT_COPY_FILE exit OK}
flq: {FILE_QUEUE_COMMIT_COPY_FILE}
flq: {FILE_QUEUE_UNWIND_BACKUP}
flq: C:\Users\ADMINI~1\AppData?\Local\Temp\{58ad0f87-1d83-1e4b-a7f9-51457acc4f11}\tap0901.cat
flq: {FILE_QUEUE_UNWIND_BACKUP exit OK}
flq: {SPFQNOTIFY_STARTCOPY}
flq: {SPFQNOTIFY_STARTCOPY - returned 0x00000001}
flq: Copying 'c:\program files\tap-windows\driver\tap0901.cat' to 'C:\Users\ADMINI~1\AppData?\Local\Temp\{58ad0f87-1d83-1e4b-a7f9-51457acc4f11}\tap0901.cat'.
flq: CopyFile?: 'c:\program files\tap-windows\driver\tap0901.cat' to 'C:\Users\ADMINI~1\AppData?\Local\Temp\{58ad0f87-1d83-1e4b-a7f9-51457acc4f11}\SETD911.tmp'
flq: {SPFQNOTIFY_PREPARECOPY}
flq: {SPFQNOTIFY_PREPARECOPY - returned 0x00000005}
flq: MoveFile?: 'C:\Users\ADMINI~1\AppData?\Local\Temp\{58ad0f87-1d83-1e4b-a7f9-51457acc4f11}\SETD911.tmp' to 'C:\Users\ADMINI~1\AppData?\Local\Temp\{58ad0f87-1d83-1e4b-a7f9-51457acc4f11}\tap0901.cat'
flq: {SPFQNOTIFY_FILECOPIED}
flq: {SPFQNOTIFY_FILECOPIED - returned 0x00000005}
flq: {SPFQNOTIFY_FINISHCOPY}
flq: {SPFQNOTIFY_FINISHCOPY - returned 0x00000005}
flq: {SPFQNOTIFY_ENDCOPY}
flq: {SPFQNOTIFY_ENDCOPY - returned 0x00000005}
flq: {FILE_QUEUE_COMMIT_COPY_FILE exit OK}
flq: Source Media:
flq: Tagfile - [tap0901.sys]
flq: Description - [tap0901.sys]
flq: SourcePath? - [c:\program files\tap-windows\driver]
flq: SourceFile? - [tap0901.sys]
flq: Flags - 0x00000000
flq: Commit: skip NEEDMEDIA (non-interactive)
flq: {FILE_QUEUE_COMMIT_COPY_FILE}
flq: {FILE_QUEUE_UNWIND_BACKUP}
flq: C:\Users\ADMINI~1\AppData?\Local\Temp\{58ad0f87-1d83-1e4b-a7f9-51457acc4f11}\tap0901.sys
flq: {FILE_QUEUE_UNWIND_BACKUP exit OK}
flq: {SPFQNOTIFY_STARTCOPY}
flq: {SPFQNOTIFY_STARTCOPY - returned 0x00000001}
flq: Copying 'c:\program files\tap-windows\driver\tap0901.sys' to 'C:\Users\ADMINI~1\AppData?\Local\Temp\{58ad0f87-1d83-1e4b-a7f9-51457acc4f11}\tap0901.sys'.
flq: CopyFile?: 'c:\program files\tap-windows\driver\tap0901.sys' to 'C:\Users\ADMINI~1\AppData?\Local\Temp\{58ad0f87-1d83-1e4b-a7f9-51457acc4f11}\SETD970.tmp'
flq: {SPFQNOTIFY_PREPARECOPY}
flq: {SPFQNOTIFY_PREPARECOPY - returned 0x00000005}
flq: MoveFile?: 'C:\Users\ADMINI~1\AppData?\Local\Temp\{58ad0f87-1d83-1e4b-a7f9-51457acc4f11}\SETD970.tmp' to 'C:\Users\ADMINI~1\AppData?\Local\Temp\{58ad0f87-1d83-1e4b-a7f9-51457acc4f11}\tap0901.sys'
flq: {SPFQNOTIFY_FILECOPIED}
flq: {SPFQNOTIFY_FILECOPIED - returned 0x00000005}
flq: {SPFQNOTIFY_FINISHCOPY}
flq: {SPFQNOTIFY_FINISHCOPY - returned 0x00000005}
flq: {SPFQNOTIFY_ENDCOPY}
flq: {SPFQNOTIFY_ENDCOPY - returned 0x00000005}
flq: {FILE_QUEUE_COMMIT_COPY_FILE exit OK}
flq: {SPFQNOTIFY_ENDSUBQUEUE}
flq: {SPFQNOTIFY_ENDSUBQUEUE - returned 0x00000005}
flq: {FILE_QUEUE_COMMIT_COPY_SUBQUEUE exit OK}
flq: {SPFQNOTIFY_ENDQUEUE}
flq: {SPFQNOTIFY_ENDQUEUE - returned 0x00000005}
flq: {FILE_QUEUE_COMMIT exit OK} 14:44:30.091
sto: Copied driver package. Time = 344 ms
sto: {Copy Driver Package: exit(0x00000000)} 14:44:30.106
pol: {Driver package policy check} 14:44:30.153
pol: {Driver package policy check - exit(0x00000000)} 14:44:30.153
sto: {Stage Driver Package: C:\Users\ADMINI~1\AppData?\Local\Temp\{58ad0f87-1d83-1e4b-a7f9-51457acc4f11}\oemvista.inf} 14:44:30.153
inf: Opened INF: 'C:\Users\ADMINI~1\AppData?\Local\Temp\{58ad0f87-1d83-1e4b-a7f9-51457acc4f11}\oemvista.inf' ([strings])
inf: Opened INF: 'C:\Users\ADMINI~1\AppData?\Local\Temp\{58ad0f87-1d83-1e4b-a7f9-51457acc4f11}\oemvista.inf' ([strings])
inf: {Query Configurability: C:\Users\ADMINI~1\AppData?\Local\Temp\{58ad0f87-1d83-1e4b-a7f9-51457acc4f11}\oemvista.inf} 14:44:30.153
inf: Opened INF: 'C:\Users\ADMINI~1\AppData?\Local\Temp\{58ad0f87-1d83-1e4b-a7f9-51457acc4f11}\oemvista.inf' ([strings])
inf: Driver package 'oemvista.inf' is configurable.
inf: {Query Configurability: exit(0x00000000)} 14:44:30.153
sto: Copying driver package files:
sto: Source Path = C:\Users\ADMINI~1\AppData?\Local\Temp\{58ad0f87-1d83-1e4b-a7f9-51457acc4f11}
sto: Destination Path = C:\WINDOWS\System32\DriverStore?\Temp\{377e1c53-45b4-2441-8582-f5722336d31b}
flq: {FILE_QUEUE_COPY}
flq: CopyStyle? - 0x00000010
flq: SourceRootPath? - 'C:\Users\ADMINI~1\AppData?\Local\Temp\{58ad0f87-1d83-1e4b-a7f9-51457acc4f11}'
flq: SourceFilename? - 'oemvista.inf'
flq: TargetDirectory?- 'C:\WINDOWS\System32\DriverStore?\Temp\{377e1c53-45b4-2441-8582-f5722336d31b}'
flq: {FILE_QUEUE_COPY exit(0x00000000)}
flq: {FILE_QUEUE_COPY}
flq: CopyStyle? - 0x00000010
flq: SourceRootPath? - 'C:\Users\ADMINI~1\AppData?\Local\Temp\{58ad0f87-1d83-1e4b-a7f9-51457acc4f11}'
flq: SourceFilename? - 'tap0901.cat'
flq: TargetDirectory?- 'C:\WINDOWS\System32\DriverStore?\Temp\{377e1c53-45b4-2441-8582-f5722336d31b}'
flq: {FILE_QUEUE_COPY exit(0x00000000)}
flq: {FILE_QUEUE_COPY}
flq: CopyStyle? - 0x00000010
flq: SourceRootPath? - 'C:\Users\ADMINI~1\AppData?\Local\Temp\{58ad0f87-1d83-1e4b-a7f9-51457acc4f11}'
flq: SourceFilename? - 'tap0901.sys'
flq: TargetDirectory?- 'C:\WINDOWS\System32\DriverStore?\Temp\{377e1c53-45b4-2441-8582-f5722336d31b}'
flq: {FILE_QUEUE_COPY exit(0x00000000)}
flq: {FILE_QUEUE_COMMIT} 14:44:30.169
flq: {SPFQNOTIFY_STARTQUEUE}
flq: {SPFQNOTIFY_STARTQUEUE - returned 0x00000001}
flq: {FILE_QUEUE_COMMIT_COPY_SUBQUEUE}
flq: {SPFQNOTIFY_STARTSUBQUEUE}
flq: {SPFQNOTIFY_STARTSUBQUEUE - returned 0x00000001}
flq: Source Media:
flq: SourcePath? - [C:\Users\ADMINI~1\AppData\Local\Temp\{58ad0f87-1d83-1e4b-a7f9-51457acc4f11}]
flq: SourceFile? - [oemvista.inf]
flq: Flags - 0x00000000
flq: Commit: skip NEEDMEDIA (non-interactive)
flq: {FILE_QUEUE_COMMIT_COPY_FILE}
flq: {FILE_QUEUE_UNWIND_BACKUP}
flq: C:\WINDOWS\System32\DriverStore?\Temp\{377e1c53-45b4-2441-8582-f5722336d31b}\oemvista.inf
flq: {FILE_QUEUE_UNWIND_BACKUP exit OK}
flq: {SPFQNOTIFY_STARTCOPY}
flq: {SPFQNOTIFY_STARTCOPY - returned 0x00000001}
flq: Copying 'C:\Users\ADMINI~1\AppData?\Local\Temp\{58ad0f87-1d83-1e4b-a7f9-51457acc4f11}\oemvista.inf' to 'C:\WINDOWS\System32\DriverStore?\Temp\{377e1c53-45b4-2441-8582-f5722336d31b}\oemvista.inf'.
flq: CopyFile?: 'C:\Users\ADMINI~1\AppData?\Local\Temp\{58ad0f87-1d83-1e4b-a7f9-51457acc4f11}\oemvista.inf' to 'C:\WINDOWS\System32\DriverStore?\Temp\{377e1c53-45b4-2441-8582-f5722336d31b}\SETD9EB.tmp'
flq: {SPFQNOTIFY_PREPARECOPY}
flq: {SPFQNOTIFY_PREPARECOPY - returned 0x00000005}
flq: MoveFile?: 'C:\WINDOWS\System32\DriverStore?\Temp\{377e1c53-45b4-2441-8582-f5722336d31b}\SETD9EB.tmp' to 'C:\WINDOWS\System32\DriverStore?\Temp\{377e1c53-45b4-2441-8582-f5722336d31b}\oemvista.inf'
flq: {SPFQNOTIFY_FILECOPIED}
flq: {SPFQNOTIFY_FILECOPIED - returned 0x00000005}
flq: {SPFQNOTIFY_FINISHCOPY}
flq: {SPFQNOTIFY_FINISHCOPY - returned 0x00000005}
flq: {SPFQNOTIFY_ENDCOPY}
flq: {SPFQNOTIFY_ENDCOPY - returned 0x00000005}
flq: {FILE_QUEUE_COMMIT_COPY_FILE exit OK}
flq: {FILE_QUEUE_COMMIT_COPY_FILE}
flq: {FILE_QUEUE_UNWIND_BACKUP}
flq: C:\WINDOWS\System32\DriverStore?\Temp\{377e1c53-45b4-2441-8582-f5722336d31b}\tap0901.cat
flq: {FILE_QUEUE_UNWIND_BACKUP exit OK}
flq: {SPFQNOTIFY_STARTCOPY}
flq: {SPFQNOTIFY_STARTCOPY - returned 0x00000001}
flq: Copying 'C:\Users\ADMINI~1\AppData?\Local\Temp\{58ad0f87-1d83-1e4b-a7f9-51457acc4f11}\tap0901.cat' to 'C:\WINDOWS\System32\DriverStore?\Temp\{377e1c53-45b4-2441-8582-f5722336d31b}\tap0901.cat'.
flq: CopyFile?: 'C:\Users\ADMINI~1\AppData?\Local\Temp\{58ad0f87-1d83-1e4b-a7f9-51457acc4f11}\tap0901.cat' to 'C:\WINDOWS\System32\DriverStore?\Temp\{377e1c53-45b4-2441-8582-f5722336d31b}\SETD9FC.tmp'
flq: {SPFQNOTIFY_PREPARECOPY}
flq: {SPFQNOTIFY_PREPARECOPY - returned 0x00000005}
flq: MoveFile?: 'C:\WINDOWS\System32\DriverStore?\Temp\{377e1c53-45b4-2441-8582-f5722336d31b}\SETD9FC.tmp' to 'C:\WINDOWS\System32\DriverStore?\Temp\{377e1c53-45b4-2441-8582-f5722336d31b}\tap0901.cat'
flq: {SPFQNOTIFY_FILECOPIED}
flq: {SPFQNOTIFY_FILECOPIED - returned 0x00000005}
flq: {SPFQNOTIFY_FINISHCOPY}
flq: {SPFQNOTIFY_FINISHCOPY - returned 0x00000005}
flq: {SPFQNOTIFY_ENDCOPY}
flq: {SPFQNOTIFY_ENDCOPY - returned 0x00000005}
flq: {FILE_QUEUE_COMMIT_COPY_FILE exit OK}
flq: {FILE_QUEUE_COMMIT_COPY_FILE}
flq: {FILE_QUEUE_UNWIND_BACKUP}
flq: C:\WINDOWS\System32\DriverStore?\Temp\{377e1c53-45b4-2441-8582-f5722336d31b}\tap0901.sys
flq: {FILE_QUEUE_UNWIND_BACKUP exit OK}
flq: {SPFQNOTIFY_STARTCOPY}
flq: {SPFQNOTIFY_STARTCOPY - returned 0x00000001}
flq: Copying 'C:\Users\ADMINI~1\AppData?\Local\Temp\{58ad0f87-1d83-1e4b-a7f9-51457acc4f11}\tap0901.sys' to 'C:\WINDOWS\System32\DriverStore?\Temp\{377e1c53-45b4-2441-8582-f5722336d31b}\tap0901.sys'.
flq: CopyFile?: 'C:\Users\ADMINI~1\AppData?\Local\Temp\{58ad0f87-1d83-1e4b-a7f9-51457acc4f11}\tap0901.sys' to 'C:\WINDOWS\System32\DriverStore?\Temp\{377e1c53-45b4-2441-8582-f5722336d31b}\SETDA1C.tmp'
flq: {SPFQNOTIFY_PREPARECOPY}
flq: {SPFQNOTIFY_PREPARECOPY - returned 0x00000005}
flq: MoveFile?: 'C:\WINDOWS\System32\DriverStore?\Temp\{377e1c53-45b4-2441-8582-f5722336d31b}\SETDA1C.tmp' to 'C:\WINDOWS\System32\DriverStore?\Temp\{377e1c53-45b4-2441-8582-f5722336d31b}\tap0901.sys'
flq: {SPFQNOTIFY_FILECOPIED}
flq: {SPFQNOTIFY_FILECOPIED - returned 0x00000005}
flq: {SPFQNOTIFY_FINISHCOPY}
flq: {SPFQNOTIFY_FINISHCOPY - returned 0x00000005}
flq: {SPFQNOTIFY_ENDCOPY}
flq: {SPFQNOTIFY_ENDCOPY - returned 0x00000005}
flq: {FILE_QUEUE_COMMIT_COPY_FILE exit OK}
flq: {SPFQNOTIFY_ENDSUBQUEUE}
flq: {SPFQNOTIFY_ENDSUBQUEUE - returned 0x00000005}
flq: {FILE_QUEUE_COMMIT_COPY_SUBQUEUE exit OK}
flq: {SPFQNOTIFY_ENDQUEUE}
flq: {SPFQNOTIFY_ENDQUEUE - returned 0x00000005}
flq: {FILE_QUEUE_COMMIT exit OK} 14:44:30.216
sto: {DRIVERSTORE IMPORT VALIDATE} 14:44:30.216
inf: Opened INF: 'C:\WINDOWS\System32\DriverStore?\Temp\{377e1c53-45b4-2441-8582-f5722336d31b}\oemvista.inf' ([strings])
sig: {_VERIFY_FILE_SIGNATURE} 14:44:30.247
sig: Key = oemvista.inf
sig: FilePath? = C:\WINDOWS\System32\DriverStore?\Temp\{377e1c53-45b4-2441-8582-f5722336d31b}\oemvista.inf
sig: Catalog = C:\WINDOWS\System32\DriverStore?\Temp\{377e1c53-45b4-2441-8582-f5722336d31b}\tap0901.cat
! sig: Verifying file against specific (valid) catalog failed! (0x800b0109)
sig: {_VERIFY_FILE_SIGNATURE exit(0x800b0109)} 14:44:30.263
sig: {_VERIFY_FILE_SIGNATURE} 14:44:30.263
sig: Key = oemvista.inf
sig: FilePath? = C:\WINDOWS\System32\DriverStore?\Temp\{377e1c53-45b4-2441-8582-f5722336d31b}\oemvista.inf
sig: Catalog = C:\WINDOWS\System32\DriverStore?\Temp\{377e1c53-45b4-2441-8582-f5722336d31b}\tap0901.cat
sig: Success: File is signed in Authenticode(tm) catalog.
sig: {_VERIFY_FILE_SIGNATURE exit(0xe0000241)} 14:44:30.294
sig: Driver package is digitally signed by 'OpenVPN Technologies, Inc.' (). Signer Score = 0x0F000000
sig: Code Integrity State: Enforced
inf: Opened INF: 'C:\WINDOWS\System32\DriverStore?\Temp\{377e1c53-45b4-2441-8582-f5722336d31b}\oemvista.inf' ([strings])
sig: Validating driver package files against catalog 'tap0901.cat'.
sig: Verified file 'tap0901.sys'.
sig: Driver package is valid.
sto: {DRIVERSTORE IMPORT VALIDATE: exit(0x00000000)} 14:44:30.294
sig: Signer Score = 0x0F000000
sig: Signer Name = OpenVPN Technologies, Inc.
sto: {DRIVERSTORE IMPORT BEGIN} 14:44:30.294
bak: System restore not required for signed driver package.
sto: {DRIVERSTORE IMPORT BEGIN: exit(0x00000000)} 14:44:30.310
sto: Importing driver package files:
sto: Source Path = C:\WINDOWS\System32\DriverStore?\Temp\{377e1c53-45b4-2441-8582-f5722336d31b}
sto: Destination Path = C:\WINDOWS\System32\DriverStore?\FileRepository?\oemvista.inf_amd64_a572b7f20c402d28
cpy: {Copy Directory: C:\WINDOWS\System32\DriverStore?\Temp\{377e1c53-45b4-2441-8582-f5722336d31b}} 14:44:30.310
cpy: Target Path = C:\WINDOWS\System32\DriverStore?\FileRepository?\oemvista.inf_amd64_a572b7f20c402d28
cpy: Copied file 'oemvista.inf'.
cpy: Copied file 'tap0901.cat'.
cpy: Copied file 'tap0901.sys'.
cpy: {Copy Directory: exit(0x00000000)} 14:44:30.310
idb: {Register Driver Package: C:\WINDOWS\System32\DriverStore?\FileRepository?\oemvista.inf_amd64_a572b7f20c402d28\oemvista.inf} 14:44:30.310
inf: Opened INF: 'C:\WINDOWS\System32\DriverStore?\FileRepository?\oemvista.inf_amd64_a572b7f20c402d28\oemvista.inf' ([strings])
idb: Created driver package object 'oemvista.inf_amd64_a572b7f20c402d28' in DRIVERS database node.
idb: Created driver INF file object 'oem121.inf' in DRIVERS database node.
idb: Registered driver package 'oemvista.inf_amd64_a572b7f20c402d28' with 'oem121.inf'.
idb: {Register Driver Package: exit(0x00000000)} 14:44:30.310
idb: {Publish Driver Package: C:\WINDOWS\System32\DriverStore?\FileRepository?\oemvista.inf_amd64_a572b7f20c402d28\oemvista.inf} 14:44:30.310
idb: Opened driver package object 'oemvista.inf_amd64_a572b7f20c402d28' in DRIVERS database node.
idb: Opened driver INF file object 'oem121.inf' in DRIVERS database node.
idb: Activating driver package 'oemvista.inf_amd64_a572b7f20c402d28'.
cpy: Published 'oemvista.inf_amd64_a572b7f20c402d28\oemvista.inf' to 'oem121.inf'.
inf: Opened INF: 'C:\WINDOWS\System32\DriverStore?\FileRepository?\oemvista.inf_amd64_a572b7f20c402d28\oemvista.inf' ([strings])
idb: Indexed 3 device IDs for 'oemvista.inf_amd64_a572b7f20c402d28'.
sto: Flushed driver database node 'DRIVERS'. Time = 31 ms
sto: Flushed driver database node 'SYSTEM'. Time = 16 ms
idb: {Publish Driver Package: exit(0x00000000)} 14:44:30.372
sto: Setting catalog hint 'oem121.cat' on files
sto: Catalog hint set on file 'C:\WINDOWS\System32\DriverStore?\FileRepository?\oemvista.inf_amd64_a572b7f20c402d28\tap0901.sys'
sto: {DRIVERSTORE IMPORT END} 14:44:30.388
dvi: Flushing C:\WINDOWS\System32\DriverStore?\FileRepository?\oemvista.inf_amd64_a572b7f20c402d28\tap0901.sys to disk.
dvi: Flushing C:\WINDOWS\System32\DriverStore?\FileRepository?\oemvista.inf_amd64_a572b7f20c402d28\tap0901.cat to disk.
dvi: Flushing C:\WINDOWS\inf\oem121.inf to disk.
dvi: Flushing C:\WINDOWS\System32\DriverStore?\FileRepository?\oemvista.inf_amd64_a572b7f20c402d28\oemvista.inf to disk.
dvi: Flushed all driver package files to disk. Time = 78 ms
sig: Installed catalog 'tap0901.cat' as 'oem121.cat'.
inf: Opened INF: 'C:\WINDOWS\System32\DriverStore?\FileRepository?\oemvista.inf_amd64_a572b7f20c402d28\oemvista.inf' ([strings])
bak: No system restore point was set earlier.
sto: {DRIVERSTORE IMPORT END: exit(0x00000000)} 14:44:30.747
sto: {Stage Driver Package: exit(0x00000000)} 14:44:30.747
ndv: Doing device matching lookup
sto: {Setup Import Driver Package - exit (0x00000000)} 14:44:30.763
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 14:44:30.872
<<< [Exit status: FAILURE(0xe0000246)]
comment:54 follow-up: 55 Changed 7 years ago by
What happens if you try to install the tap driver indirectly, by installing openvpn (2.4_rc1)?
comment:55 Changed 7 years ago by
Replying to cron2:
What happens if you try to install the tap driver indirectly, by installing openvpn (2.4_rc1)?
The same thing happens; that's what I initially did, and it always fails installing tap driver.
comment:57 Changed 7 years ago by
So, it seems to install when I go into Safe mode (without networking; it didn't work with networking enabled), and shows up in the Device Manager. However, it does not show up in the list of adapters in both control panel > network and internet > network connections and command prompt.
command prompt:
openvpn --show-adapters Available TAP-WIN32 adapters[name, GUID]:
Tried installing tap driver at the command prompt:
tapinstall.exe install ../drver/OemVista.inf tap0901 tapinstall.exe failed.
Just in case this helps. I don't know that much to give an useful insight to this problem.
comment:58 follow-up: 59 Changed 7 years ago by
So. Is there anything special about your Win10 installations? Like, a rarely-seen security suite installed, special corporate VPN client, etc.?
It works for most Win10 users, so I find it very surprising it stubbornly refuses to work for you.
comment:59 Changed 7 years ago by
Replying to cron2:
So. Is there anything special about your Win10 installations? Like, a rarely-seen security suite installed, special corporate VPN client, etc.?
It works for most Win10 users, so I find it very surprising it stubbornly refuses to work for you.
I don't think so. I'll try to list things that might be related.
- upgraded from windows 8.1
- used to have Avira Antivirus, currently deleted
- softether VPN Client
- vmware
- Mudfish launcher (basically vpn for gaming - this uses the tap driver from openvpn, from which I initially got the problem of tap driver not installing)
That is all, as far as I can remember. Speaking of which, it used to work with all of those, but failed to install when I was trying to update (i.e. reinstall) the Mudfish launcher. I've tried installing the tap driver by itself without that, which unfortunately didn't work.
comment:60 Changed 7 years ago by
My installation is nonspecial as well.
- upgraded from win7
- TightVNC installed
- Kapersky never installed
- AVIRA Antivir (free version) installed, sometimes deactivated for testing TAP installer, no effect
- secure mode tested, no effect
I have a 2nd win10 system, same hardware, almost parallel installations and use. There, openvnp and TAP work perfectly.
comment:61 Changed 7 years ago by
I skimmed through all of this again now that the problems have reappeared.
In most cases the failure seems to be caused by a timeout in the post-install phase, e.g.
ndv: Waiting for device post-install to complete. 01:06:18.715 !!! ndv: Timed out waiting for device post-install to complete. 01:10:18.715
The timeout is always exactly four minutes, so something is blocking devcon.exe.
I have heard anecdotal evidence that in some cases Windows Update can block devcon.exe. If this the case, then stopping the Windows Update service should logically solve the problem. To test this launch Windows Powershell as an administrator.
First check if Windows Update service is running:
PS C:\Windows\system32> Get-Service wuauserv Status Name DisplayName ------ ---- ----------- Running wuauserv Windows Update
If it is, stop it:
PS C:\Windows\system32> Stop-Service wuauserv
Then verify it is stopped:
PS C:\Windows\system32> Get-Service wuauserv Status Name DisplayName ------ ---- ----------- Stopped wuauserv Windows Update
Now try to install tap-windows / openvpn again and see what happens. If installation now works, then Windows update was the culprit.
Once you're done with the tests, the Windows Update service can be restarted with
PS C:\Windows\system32> Start-Service wuauserv
comment:62 Changed 7 years ago by
So, I did check the wuauserv, and it was already stopped. for some reason, Get-Service, Stop-Service, and Start-Service all gave me:
'<something-Service>' is not recognized as an internal or external command, operable program or batch file.
On another note, I was suspecting my system was broken (maybe the registry) because it seemed that most people's ones were working, so I tried to run sfc /scannow, which didn't work - Windows Modules Installer wasn't in the list of services, while the TrustedInstaller?.exe did exist on C:\Windows\servicing directory (and running it didn't do anything). I guess this is the reason that it's not installing - upon trying to install the SoftEther? VPN again, it also failed to install its adapter. Based on the fact that everything was running fine before this arised, I'm guessing that recent windows update broke something on my computer.
Anyhow, at least for me, I figure the issue's not related to OpenVPN at all. Maybe I'll have to do a clean install of windows. Thank you all for looking into it though.
comment:63 Changed 7 years ago by
Get-Service is not a recognized command on my system. Instead, I used "sc query wuauserv", indicating that the service is stopped.
I checked system health with "Dism /Online /Cleanup-Image /RestoreHealth?", no errors were found. "sfc /scannow" does not help, the command recommends reboot, even after reboot.
No success installing TAP driver after uninstalling Avira Antivir.
The TAP issue persists, the system seems to be quite healthy. Any idea is acknowledged.
comment:64 Changed 7 years ago by
@mandu1021, @hermy10: you are you sure you launched a Windows _PowerShell_ session, not cmd.exe?
If Powershell is truly missing, then the Windows installation has been customized to some degree, as Powershell should be installed by default on Windows 7 and later, and possibly Vista.
comment:65 Changed 7 years ago by
@samuli: powershell is installed. sfc produces same message. I found a command for reinstalling the win10 apps, no success when installing Openvpn.
Now, I have a repair USB for win10, but I do not really know how to handle it.
comment:66 Changed 7 years ago by
Just found this ticket and sadly I've run into this issue numerous times. In my particular case at least, it's always been windows fault.
As hinted to by this Superuser Post:
The problem is with permissions of windows driver folders. It seems to trigger during windows update flights and appears to be random (so I'm guessing the windows update fails at some point when restoring drivers as part of upgrade process).
Using the "Take Ownership" shell extension and adding myself to drivers folder and force propagating the permission fixes the problem.
Take Ownership Shell Extension for Windows 10: https://www.tenforums.com/tutorials/3841-take-ownership-add-context-menu-windows-10-a.html
comment:67 Changed 7 years ago by
Following the links given by maverik, I applied "take ownership" to the folders "drivers" and "DriverStore?" in C:\windows\system32, no success.
In the meantime, I noted additional problems on my win10 system. The online update did not work, I was unable to install manually the newest updates, and I was unable to uninstall the latest installed update. There may or may not be a connection between the driver problem and the update problem. I decided to reset windows and keeping the own data, following the procedure suggested by Microsoft ("Wiederherstellungsoptionen").
In summary, the exercise was very very time-consuming but openvpn could be installed normally at the end.
Thanks to all for the various suggestions.
comment:68 Changed 7 years ago by
I have the same problem on Windows 10 64 bit. I don`t have any antivirus, firewall etc...Windows Defender is also swith off.
But I am still get this error - unable to install TAP driver. I have tried many version, I have tried manually install driver - nothing works.
comment:70 Changed 7 years ago by
Having the same symptoms, in my case it was due to pending connection bridge. It was not removed with the old version. After i have deleted it openVpn (tap driver) installs without errors.
comment:72 Changed 6 years ago by
Replying to hmsgcr:
No work Windows 10 Tap-Windows Adapter
Add ComponentId?: tap0901 not fix the problem
I ran into same issue and found that Checkpoint VPN client was causing the TAP Driver to not install correctly. Once I uninstalled the driver started to work correctly.
comment:73 Changed 6 years ago by
I experienced this same issue on Windows 10 x64, but I was able to resolve by closing all virtualization software.
I use Sandboxie and Virtualbox for virtualization. In addition to Virtualbox, I use VMBoxService to run a VM as a service. I stopped all Sandboxie apps, and shutdown all VMs and stopped the VMBoxService. I then proceeded to install OpenVPN and the install went through. My suggestion is to stop all applications and Virtual Machines before installing to see if it resolves the issue.
Additionally, if you have any software that utilizes a virtual nic, you may want to make sure it's not running as well. In my case, I was using a Loopback adapter in my VM. Not sure if that made a difference, but it may be valuable information for anyone when testing.
comment:74 Changed 6 years ago by
Replying to hmsgcr:
No work Windows 10 Tap-Windows Adapter
Add ComponentId?: tap0901 not fix the problem
This worked for me, the problem was the TAP Driver is unsigned and being rejected by Windows 10 integrity checking. To disable integrity checking / allow unsigned drivers to be installed:
open cmd prompt via Start, Windows System, Right click on Command Prompt, More, select Run as Administrator
Type the following in the dos window to turn off integrity checking and allow the TAP drivers to be installed:
bcdedit.exe /set nointegritychecks on
Now run the install of your software
After successful install of TAP Driver, turn integrity checking back on:
bcdedit.exe /set nointegritychecks off
If you run in a non admin mode you may get and error related to Unable to Open Data Store. Make sure you run CMD/DOS window as administrator.
comment:75 Changed 5 years ago by
I also had the same problem:
devcon.exe failed
after updating TAP and OpenVPN it was:
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=1460 tapinstall.exe failed.
I fixed it by uninstalling Check Point VPN, which was also installed on the same laptop. Everything works fine if Check Point is installed *AFTER* OpenVPN, but not if you update OpenVPN after Check Point installation.
comment:76 Changed 5 years ago by
Thank you very much.
The combination
bcdedit.exe /set nointegritychecks on
and unistall Check Point VPN client worked for me !!!!
comment:77 Changed 5 years ago by
New tap-windows6 release (9.23.2) for Windows 10 is available here:
Can you guys try installing that and see if it works? No special trickery should be necessary as it comes with Microsoft's own signature.
comment:78 Changed 4 years ago by
Update:
I just tested the link below on a Windows 10 instance with no luck.
- Attempted TAP-Replacement: https://build.openvpn.net/downloads/releases/tap-windows-9.23.2-I601-Win10.exe
Use Case:
I have running and OpenVPN crashes due to 'Unexpected Errors'.
My use case is for the AWS CPN Client setup.
The AWS docs indicate that the errors I am seeing are because TAP-Windows is not installed on my machine.
Troubleshooting:
I uninstalled my existing TAP-Windows V9 and installed the TAP-Windows v9.23.2 linked above and then restarted my machine. Upon restart, I tried to connect to the AWS VPN but the connection failed with the same error message:
DeDupeProcessDiedSignals: Unexpected errors caused OpenVPN to exit prematurely
Moving Forward:
I will continue to search the web and can update this post if I find a reliable solution.
Any advice on how to proceed would be much appreciated.
Thanks!
Solution:
This had nothing to do with OpenVPN, my path names for the cert & key files listed in my configurations just needed to be in quotes....XD
PS. I found the link below to be very helpful in understanding how all of these tools fit together:
comment:79 Changed 4 years ago by
I cant believe this is a 5 year old bug :D
I just installed openvpn client 2.4.9 on windows 10 and it hanged at installing tap driver.. I then had to disable all my adapters (yes i have many) except my main internet ethernet connection, reboot and reinstall for it to work!! I think this needs some urgent fixing..
comment:80 Changed 4 years ago by
@kopetepanda this is 5 years old because this is not a single bug and can't ever be fixed as such. This ticket is a mix of issues in external antivirus software, Windows and OpenVPN.
That said, we recently found out that if there is an old cross-signed (=Windows 7) tap-windows6 driver in the driver store then Windows has a tendency to prefer it over the (correct) attestation-signed (Windows 10) version. The only cure is to get rid of all tap-windows6 versions in the driver store before running the installer - just follow the usual clean up and start from scratch approach.
The OpenVPN 2.5 release which is around the corner will be distributed as an MSI installer. The tap-windows6 management will be much improved there.
comment:81 Changed 3 years ago by
I had the same problem, on 2 different Windows 10 computers. What worked for me:
1) Disabling all network adapters
2) Take ownership of the C:\Windows\system32\Drivers and DriverStore? folders using the https://www.tenforums.com/tutorials/3841-take-ownership-add-context-menu-windows-10-a.html shell extension as mentioned in comment 66 above
3) Booting Windows into state where installation of unsigned drivers is allowed. This became more strict as the time went and hence less easy to allow. What works when I am writing this comment is: Shift + Reboot pressing the button, then "Choose an option", "Troubleshoot", "Advanced options", "Start-up settings", "Restart". When system is starting it allows you to choose boot mode, press 7 or F7 (https://www.supportrix.com/kb/how-to-install-unsigned-drivers-in-windows-10/).
All of the steps above were necessary. It is weird that not all people have this problem when installing...
i have same problem.
windows 10 pro x64 (updated from windows 8.1).
openvpn-install-2.3.8-I601-x86_64.exe (also i tried openvpn-install-2.3.8-I001-x86_64.exe, openvpn-install-2.3.7-I003-x86_64.exe, openvpn-install-2.3.7-I603-x86_64.exe).
when I try to install openvpn, i have such error:
also i tried full uninstall openvpn (with tap), but it did not help.
when i run "Add a new TAP virtual ethernet adapter" (addtap.bat) i have such log: