I upgraded to Windows 10 x64 professionnal last week.
I found it smart to also update my VNP application 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 installer failed...
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 :
Code: Select all
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 indefinitely wait for 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 in this.
It's more than probably related to the bug-Trac # 592
Thanks for a quick support with this as I'm clearly stuck (...and people are getting massively on win10 these days, if it's somehow related...)
Micro$oft ..