08-17-2017 09:40 AM - edited 02-21-2020 09:24 PM
I have a user that just updated their anyconnect this week and when it was going thru the install it stopped 3/4 way thru. The error it showed was VPN adapter errror. I uninstalled the previous version and tried to reinstall and got the same error.
When looking at the setup log it looks like during the install there is an error 1460 with the device and then it installs a null driver and then it removes all the files. The unknown device is still there and every time retry to install it creates another unknow device such as Root\Net\0000, Root\Net\0001 and so on.
I've tried to update the drive on the unknow device and that doesn't work, and also trying to delete them doesn't work. The main thing I'm looking to do is get the anyconnect back up and running correctly, and then to remove the unknown devices. I'm thinking if I booted into safe mode I could remove the devices, but this is a remote user and I might not be able to do that until the next time he comes in to the office.
Here is the log.
>>> [Device Install (UpdateDriverForPlugAndPlayDevices) - VPNVA]
>>> Section start 2017/08/15 12:04:37.295
cmd: "C:\Program Files (x86)\Cisco\Cisco AnyConnect Secure Mobility Client\VACon64.exe" -install "C:\Program Files (x86)\Cisco\Cisco AnyConnect Secure Mobility Client\\vpnva-6.inf" VPNVA
ndv: INF path: C:\Program Files (x86)\Cisco\Cisco AnyConnect Secure Mobility Client\\vpnva-6.inf
ndv: Install flags: 0x00000001
ndv: {Update Device Driver - ROOT\NET\0007}
ndv: Search options: 0x00000080
ndv: Searching single INF 'C:\Program Files (x86)\Cisco\Cisco AnyConnect Secure Mobility Client\vpnva-6.inf'
dvi: {Build Driver List} 12:14:30.353
dvi: Searching for hardware ID(s):
dvi: vpnva
dvi:
dvi: Created Driver Node:
dvi: HardwareID - vpnva
dvi: InfName - c:\program files (x86)\cisco\cisco anyconnect secure mobility client\vpnva-6.inf
dvi: DevDesc - Cisco AnyConnect Secure Mobility Client Virtual Miniport Adapter for Windows x64
dvi: Section - Cisco.ndi.NTamd64
dvi: Rank - 0x00ff0000
dvi: Signer Score - WHQL
dvi: DrvDate - 02/26/2014
dvi: Version - 3.1.6019.0
dvi: {Build Driver List - exit(0x00000000)} 12:14:30.368
dvi: {DIF_SELECTBESTCOMPATDRV} 12:14:30.368
dvi: Default installer: Enter 12:14:30.368
dvi: {Select Best Driver}
dvi: Class GUID of device changed to: {4d36e972-e325-11ce-bfc1-08002be10318}.
dvi: Selected Driver:
dvi: Description - Cisco AnyConnect Secure Mobility Client Virtual Miniport Adapter for Windows x64
dvi: InfFile - c:\program files (x86)\cisco\cisco anyconnect secure mobility client\vpnva-6.inf
dvi: Section - Cisco.ndi.NTamd64
dvi: {Select Best Driver - exit(0x00000000)}
dvi: Default installer: Exit
dvi: {DIF_SELECTBESTCOMPATDRV - exit(0x00000000)} 12:14:30.368
ndv: Force Installing Driver:
ndv: Inf Name - vpnva-6.inf
ndv: Driver Date - 02/26/2014
ndv: Driver Version - 3.1.6019.0
ndv: Driver package 'C:\WINDOWS\System32\DriverStore\FileRepository\vpnva-6.inf_amd64_f4ee011be27e2804\vpnva-6.inf' is already imported.
sto: {Setup Import Driver Package: c:\program files (x86)\cisco\cisco anyconnect secure mobility client\vpnva-6.inf} 12:14:30.368
sto: Driver package already imported as 'oem75.inf'.
sto: {Setup Import Driver Package - exit (0x00000000)} 12:14:30.368
dvi: Searching for hardware ID(s):
dvi: vpnva
dvi:
dvi: Class GUID of device changed to: {4d36e972-e325-11ce-bfc1-08002be10318}.
dvi: {Plug and Play Service: Device Install for ROOT\NET\0007}
dvi: Driver INF Path: C:\WINDOWS\INF\oem75.inf
dvi: Driver Node Name: vpnva-6.inf:573bd3b1d858e0ac:Cisco.ndi.NTamd64:3.1.6019.0:vpnva,
dvi: Driver Store Path: C:\WINDOWS\System32\DriverStore\FileRepository\vpnva-6.inf_amd64_f4ee011be27e2804\vpnva-6.inf
dvi: Searching for hardware ID(s):
dvi: vpnva
dvi:
dvi: Class GUID of device changed to: {4d36e972-e325-11ce-bfc1-08002be10318}.
dvi: {Core Device Install} 12:14:30.493
dvi: {Install Device - ROOT\NET\0007} 12:14:30.493
dvi: Parent device: HTREE\ROOT\0
dvi: {Configure Device - ROOT\NET\0007} 12:14:30.509
dvi: Parent device: HTREE\ROOT\0
sto: {Configure Driver Package: C:\WINDOWS\System32\DriverStore\FileRepository\vpnva-6.inf_amd64_f4ee011be27e2804\vpnva-6.inf}
sto: Source Filter = vpnva
inf: Class GUID = {4d36e972-e325-11ce-bfc1-08002be10318}
inf: Class Options = Configurable
inf: {Configure Driver: Cisco AnyConnect Secure Mobility Client Virtual Miniport Adapter for Windows x64}
inf: Section Name = Cisco.ndi.NTamd64
inf: {Add Service: vpnva}
inf: Start Type = 3
inf: Service Type = 1
inf: Error Control = 1
inf: Image Path = \SystemRoot\System32\drivers\vpnva64-6.sys
inf: Display Name = Cisco AnyConnect Secure Mobility Client Virtual Miniport Adapter for Windows x64
inf: Group = NDIS
inf: Updated service 'vpnva'.
inf: {Add Service: exit(0x00000000)}
inf: Hardware Id = vpnva
inf: {Configure Driver Configuration: Cisco.ndi.NTamd64}
inf: Service Name = vpnva
inf: Config Flags = 0x00000000
inf: {Configure Driver Configuration: exit(0x00000000)}
inf: {Configure Driver: exit(0x00000000)}
flq: Copying 'C:\WINDOWS\System32\DriverStore\FileRepository\vpnva-6.inf_amd64_f4ee011be27e2804\vpnva64-6.sys' to 'C:\WINDOWS\System32\drivers\vpnva64-6.sys'.
cpy: Existing file 'C:\WINDOWS\System32\drivers\vpnva64-6.sys' remains unchanged.
sto: {Configure Driver Package: exit(0x00000000)}
dvi: Install Device: Configuring device (oem75.inf:vpnva,Cisco.ndi.NTamd64). 12:14:30.587
dvi: Install Device: Configuring device completed. 12:14:30.587
dvi: Install Device: Starting device. 12:14:30.587
dvi: Install Device: Starting device completed. 12:14:30.618
dvi: {Configure Device - exit(0x00000000)} 12:14:30.618
dvi: {Install Device - exit(0x00000000)} 12:14:30.650
dvi: {Core Device Install - exit(0x00000000)} 12:14:30.650
dvi: Waiting for device post-install to complete. 12:14:30.650
!!! dvi: Timed out waiting for device post-install to complete. 12:18:30.651
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\0007}
! dvi: Installing NULL driver!
dvi: {DIF_ALLOW_INSTALL} 12:18:30.776
dvi: Default installer: Enter 12:18:30.776
dvi: Default installer: Exit
dvi: {DIF_ALLOW_INSTALL - exit(0xe000020e)} 12:18:30.776
dvi: {DIF_REGISTER_COINSTALLERS} 12:18:30.776
dvi: Default installer: Enter 12:18:30.776
dvi: Default installer: Exit
dvi: {DIF_REGISTER_COINSTALLERS - exit(0x00000000)} 12:18:30.776
dvi: {DIF_INSTALLDEVICE} 12:18:30.776
dvi: Default installer: Enter 12:18:30.776
! dvi: Installing NULL driver!
dvi: Install Null Driver: Removing device sub-tree. 12:18:30.776
dvi: Install Null Driver: Removing device sub-tree completed. 12:18:30.776
dvi: Install Null Driver: Restarting device. 12:18:30.791
dvi: Install Null Driver: Restarting device completed. 12:18:30.791
dvi: Install Device: Configuring device class. 12:18:30.791
dvi: Install Device: Configuring device class completed. 12:18:30.791
dvi: Install Device: Starting device. 12:18:30.791
dvi: Install Device: Starting device completed. 12:18:30.807
dvi: Default installer: Exit
dvi: {DIF_INSTALLDEVICE - exit(0x00000000)} 12:18:30.807
ump: {Plug and Play Service: Device Install exit(00000000)}
ndv: {Update Device Driver - exit(000005b4)}
!!! ndv: Failed to install device instance 'ROOT\NET\0007'. Error = 0x000005b4
<<< Section end 2017/08/15 12:18:30.807
<<< [Exit status: FAILURE(0x000005b4)]
08-17-2017 10:19 AM
Hi,
This error is a generic code for an MSI action failure. In this case, the Virtual Adapter installer has failed.
Check whether this registry key is present or not:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce.
In addition, you can try one of these actions in order to resolve the issue:
Execute this command in order to perform a quiet installation of AnyConnect:
Scan your registry for AnyConnect related bogus keys and remove them.
Microsoft has released a fix for this in the following update:
https://support.microsoft.com/en-us/help/4015217/windows-10-update-kb4015217
If this does not help try disabling the Anti-Virus software on the PC and then try installing the Anyconnect.
Also try to use MS tool to uninstall AnyConnect (support.microsoft.com/en-us/help/17588/fix-problems-that-block-programs-from-being-installed-or-removed) and then install AnyConnect again.
Regards,
Aditya
Please rate helpful and mark correct answers
03-30-2018 10:53 AM
Is there already a possible to install it on Windows 10 1709. I get the same issue installing the adapter:
>>> [Device Install (UpdateDriverForPlugAndPlayDevices) - VPNVA] >>> Section start 2018/03/30 19:32:05.258 cmd: "C:\Program Files (x86)\Cisco\Cisco AnyConnect Secure Mobility Client\VACon64.exe" -install "C:\Program Files (x86)\Cisco\Cisco AnyConnect Secure Mobility Client\\vpnva-6.inf" VPNVA ndv: INF path: C:\Program Files (x86)\Cisco\Cisco AnyConnect Secure Mobility Client\\vpnva-6.inf ndv: Install flags: 0x00000001 ndv: {Update Device Driver - ROOT\NET\0000} ndv: Search options: 0x00000080 ndv: Searching single INF 'C:\Program Files (x86)\Cisco\Cisco AnyConnect Secure Mobility Client\vpnva-6.inf' dvi: {Build Driver List} 19:32:05.267 dvi: Searching for hardware ID(s): dvi: vpnva dvi: ? dvi: Created Driver Node: dvi: HardwareID - vpnva dvi: InfName - c:\program files (x86)\cisco\cisco anyconnect secure mobility client\vpnva-6.inf dvi: DevDesc - Cisco AnyConnect Secure Mobility Client Virtual Miniport Adapter for Windows x64 dvi: Section - Cisco.ndi.NTamd64 dvi: Rank - 0x00ff0000 dvi: Signer Score - WHQL dvi: DrvDate - 02/26/2014 dvi: Version - 3.1.6019.0 dvi: {Build Driver List - exit(0x00000000)} 19:32:05.277 dvi: {DIF_SELECTBESTCOMPATDRV} 19:32:05.277 dvi: Default installer: Enter 19:32:05.278 dvi: {Select Best Driver} dvi: Class GUID of device changed to: {4d36e972-e325-11ce-bfc1-08002be10318}. dvi: Selected Driver: dvi: Description - Cisco AnyConnect Secure Mobility Client Virtual Miniport Adapter for Windows x64 dvi: InfFile - c:\program files (x86)\cisco\cisco anyconnect secure mobility client\vpnva-6.inf dvi: Section - Cisco.ndi.NTamd64 dvi: {Select Best Driver - exit(0x00000000)} dvi: Default installer: Exit dvi: {DIF_SELECTBESTCOMPATDRV - exit(0x00000000)} 19:32:05.282 ndv: Force Installing Driver: ndv: Inf Name - vpnva-6.inf ndv: Driver Date - 02/26/2014 ndv: Driver Version - 3.1.6019.0 ndv: Driver package 'C:\WINDOWS\System32\DriverStore\FileRepository\vpnva-6.inf_amd64_f4ee011be27e2804\vpnva-6.inf' is already imported. sto: {Setup Import Driver Package: c:\program files (x86)\cisco\cisco anyconnect secure mobility client\vpnva-6.inf} 19:32:05.287 sto: Driver package already imported as 'oem30.inf'. sto: {Setup Import Driver Package - exit (0x00000000)} 19:32:05.290 dvi: Searching for hardware ID(s): dvi: vpnva dvi: ? dvi: Class GUID of device changed to: {4d36e972-e325-11ce-bfc1-08002be10318}. dvi: {Plug and Play Service: Device Install for ROOT\NET\0000} dvi: Driver INF Path: C:\WINDOWS\INF\oem30.inf dvi: Driver Node Name: vpnva-6.inf:573bd3b1d858e0ac:Cisco.ndi.NTamd64:3.1.6019.0:vpnva, dvi: Driver Store Path: C:\WINDOWS\System32\DriverStore\FileRepository\vpnva-6.inf_amd64_f4ee011be27e2804\vpnva-6.inf dvi: Searching for hardware ID(s): dvi: vpnva dvi: ? dvi: Class GUID of device changed to: {4d36e972-e325-11ce-bfc1-08002be10318}. dvi: {Core Device Install} 19:32:05.346 dvi: {Install Device - ROOT\NET\0000} 19:32:05.348 dvi: Device Status: 0x01802001, Problem: 0x0 (0x00000000) dvi: Parent device: HTREE\ROOT\0 dvi: {Configure Device - ROOT\NET\0000} 19:32:05.352 dvi: Device Status: 0x01802001, Problem: 0x0 (0x00000000) dvi: Parent device: HTREE\ROOT\0 sto: {Configure Driver Package: C:\WINDOWS\System32\DriverStore\FileRepository\vpnva-6.inf_amd64_f4ee011be27e2804\vpnva-6.inf} sto: Source Filter = vpnva inf: Class GUID = {4d36e972-e325-11ce-bfc1-08002be10318} inf: Class Options = Configurable inf: {Configure Driver: Cisco AnyConnect Secure Mobility Client Virtual Miniport Adapter for Windows x64} inf: Section Name = Cisco.ndi.NTamd64 inf: {Add Service: vpnva} inf: Start Type = 3 inf: Service Type = 1 inf: Error Control = 1 inf: Image Path = \SystemRoot\System32\drivers\vpnva64-6.sys inf: Display Name = Cisco AnyConnect Secure Mobility Client Virtual Miniport Adapter for Windows x64 inf: Group = NDIS inf: Updated service 'vpnva'. inf: {Add Service: exit(0x00000000)} inf: Hardware Id = vpnva inf: {Configure Driver Configuration: Cisco.ndi.NTamd64} inf: Service Name = vpnva inf: Config Flags = 0x00000000 inf: {Configure Driver Configuration: exit(0x00000000)} inf: {Configure Driver: exit(0x00000000)} flq: Copying 'C:\WINDOWS\System32\DriverStore\FileRepository\vpnva-6.inf_amd64_f4ee011be27e2804\vpnva64-6.sys' to 'C:\WINDOWS\System32\drivers\vpnva64-6.sys'. cpy: Existing file 'C:\WINDOWS\System32\drivers\vpnva64-6.sys' remains unchanged. sto: {Configure Driver Package: exit(0x00000000)} dvi: Install Device: Configuring device (oem30.inf:vpnva,Cisco.ndi.NTamd64). 19:32:05.384 dvi: Install Device: Configuring device completed. 19:32:05.387 dvi: Device Status: 0x01802001, Problem: 0x0 (0x00000000) dvi: Install Device: Starting device 'ROOT\NET\0000'. 19:32:05.388 dvi: Install Device: Starting device completed. 19:32:05.395 ! dvi: Device pending start: Device has problem: 0x38 (CM_PROB_NEED_CLASS_CONFIG), problem status: 0x00000000. dvi: {Configure Device - exit(0x00000000)} 19:32:05.397 dvi: Device Status: 0x01802401, Problem: 0x38 dvi: {Install Device - exit(0x00000000)} 19:32:05.407 dvi: {Core Device Install - exit(0x00000000)} 19:32:05.407 dvi: Waiting for device post-install to complete. 19:32:05.409 !!! dvi: Timed out waiting for device post-install to complete. 19:36:05.410 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} ! dvi: Installing NULL driver! dvi: {DIF_ALLOW_INSTALL} 19:36:05.654 dvi: Default installer: Enter 19:36:05.655 dvi: Default installer: Exit dvi: {DIF_ALLOW_INSTALL - exit(0xe000020e)} 19:36:05.656 dvi: {DIF_REGISTER_COINSTALLERS} 19:36:05.656 dvi: Default installer: Enter 19:36:05.657 dvi: Default installer: Exit dvi: {DIF_REGISTER_COINSTALLERS - exit(0x00000000)} 19:36:05.658 dvi: {DIF_INSTALLDEVICE} 19:36:05.658 dvi: Default installer: Enter 19:36:05.659 ! dvi: Installing NULL driver! dvi: Install Null Driver: Removing device sub-tree. 19:36:05.665 dvi: Install Null Driver: Removing device sub-tree completed. 19:36:05.666 dvi: Install Null Driver: Restarting device. 19:36:05.674 dvi: Install Null Driver: Restarting device completed. 19:36:05.675 dvi: Install Device: Configuring device class. 19:36:05.675 dvi: Install Device: Configuring device class completed. 19:36:05.676 dvi: Device Status: 0x01802401, Problem: 0x1c (0x00000000) dvi: Install Device: Starting device 'ROOT\NET\0000'. 19:36:05.678 dvi: Install Device: Starting device completed. 19:36:05.679 dvi: Default installer: Exit dvi: {DIF_INSTALLDEVICE - exit(0x00000000)} 19:36:05.680 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 2018/03/30 19:36:05.685 <<< [Exit status: FAILURE(0x000005b4)]
03-30-2018 11:44 AM
Hi,
Looks like you are running into CSCvb59209. This is a Microsoft defect with how the NAM filter driver is upgraded/uninstalled/installed. Microsoft has released a tool to fix machines that encounter this issue. In order to obtain the tool you will need to open a TAC SR and they can provide the tool.
Thanks,
Steve S.
03-30-2018 11:47 AM
I should also mention that the 4.6 release that is posted on CCO will prevent this issue from occurring in the future.
Thanks,
Steve S.
03-31-2018 07:17 AM
Thank you for this post. The issue occured due to the use of Checkpoint Endpoint Security. I updated it to version 80.81. After this anyconnect could be installed correctly. Poorly Checkpoint doesn't support automatic updates. Thank you for your help!
03-30-2019 10:10 AM
I had recently the same problem.
dvi: {DIF_INSTALLDEVICE} 02:30:31.521
dvi: Default installer: Enter 02:30:31.521
! dvi: Installing NULL driver!
dvi: Install Null Driver: Removing device sub-tree. 02:30:31.537
dvi: Install Null Driver: Removing device sub-tree completed. 02:30:31.662
dvi: Install Null Driver: Restarting device. 02:30:31.677
dvi: Install Null Driver: Restarting device completed. 02:30:31.708
dvi: Install Device: Configuring device class. 02:30:31.708
dvi: Install Device: Configuring device class completed. 02:30:31.708
dvi: Device Status: 0x01802401, Problem: 0x1c (0x00000000)
dvi: Install Device: Starting device 'ROOT\NET\0002'. 02:30:31.708
dvi: Install Device: Starting device completed. 02:30:31.755
dvi: Default installer: Exit
dvi: {DIF_INSTALLDEVICE - exit(0x00000000)} 02:30:31.755
ump: {Plug and Play Service: Device Install exit(00000000)}
ndv: {Update Device Driver - exit(000005b4)}
!!! ndv: Failed to install device instance 'ROOT\NET\0002'. Error = 0x000005b4
<<< Section end 2019/03/30 02:30:31.771
<<< [Exit status: FAILURE(0x000005b4)]
I tried all suggestions but the only one that worked for me was to review my firewall, I read at some threads that sometimes have problems with Checkpoint VPN products installed on your machine, I didnt have any vpn installed with that products but my firewall is from checkpoint so I followed next steeps:
Good luck
Edgar I Vergara Reveles.
08-22-2017 01:10 AM
Check the installation part of this document:
Moh,
08-25-2017 01:21 PM
Hello,
The "Timed out waiting for post install to complete" error message in the setupapi.dev log is indicitive of what Microsoft fixed with the KB listed by Aditya. Keep in mind that this KB must be installed prior to upgrading the client. Once an upgrade is attempted without the KB installed it will leave the PC in a bad state and most likely a re-image will be needed. We have also confirmed that CheckPoint Disk Encryption versions prior to 81.1.0.6520 will also cause this same error message.
Steve S.
04-03-2020 11:24 AM - edited 04-03-2020 11:28 AM
I had this same issue where anyconnect failed an upgrade from 4.6 to 4.8. After the failure no version would install.
I did not have checkpoint or other AV that would affect this. In the end my issue was with Cisco Network Access Manager filter driver. Uninstalling NAM was not enough. I needed to force remove a regkey.
If you are having the same issue even after removing NM, Check for this key HKEY_CLASSES_ROOT\CLSID\{9e871141-0120-4c3e-aba2-8f99335b69c1}. If it exists, remove it.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide