cancel
Showing results for 
Search instead for 
Did you mean: 

Unable to configure virtual adapter after reinstalling Pulse

Occasional Contributor

Unable to configure virtual adapter after reinstalling Pulse

We use pulse for our remote access VPN.  We allow our users to change their VPN configs.  

However, this user also needed Pulse to connect to a client's network, and they installed a profile that prevented us from editing VPN configs, so it only listed their VPN tunnels instead of ours.  Since we couldn't change it, we ended up reinstalling Pulse Secure.

 

Now, after the reinstall, we get a 1205 error (failed to setup virtual adapter).  We followed troubleshooting online, such as making sure the driver was listed in Device Manager and fully functional (it was), have reinstalled pulse 2 times.

 

What other steps can we take to get this error gone?

 

 

The client is using Windows 10 and Pulse Secure 5.3.7.

10 REPLIES 10
Moderator
Moderator

Re: Unable to configure virtual adapter after reinstalling Pulse

Please uninstall Antivirus, other VPN clients (if any) and attempt to repair the Pulse client installation. Reboot the machine after repair and check the behaviour.
Occasional Contributor

Re: Unable to configure virtual adapter after reinstalling Pulse

We have Symantec installed but can't uninstall it because of security policy.   There are no other VPN clients installed, and Symantec didn't interfere before we reinstalled.

 

 

Searching through logs, I found this failure in setupapi.dev.log

 

>>>  [Device Install (Hardware initiated) - {FE36527A-8C07-4854-8AF7-BF40E7DF52F7}\JNPRVA\0001]
>>>  Section start 2019/05/13 10:54:37.027
     dvi: {Build Driver List} 10:54:37.079
     dvi:      Searching for hardware ID(s):
     dvi:           {fe36527a-8c07-4854-8af7-bf40e7df52f7}\jnprva
     dvi:      Created Driver Node:
     dvi:           HardwareID   - {FE36527A-8C07-4854-8AF7-BF40E7DF52F7}\JNPRVA
     dvi:           InfName      - C:\Windows\System32\DriverStore\FileRepository\jnprva.inf_amd64_80b297ba301623ad\jnprva.inf
     dvi:           DevDesc      - Juniper Networks Virtual Adapter
     dvi:           Section      - JnprVa.Ndi
     dvi:           Rank         - 0x00ff0000
     dvi:           Signer Score - WHQL
     dvi:           DrvDate      - 10/18/2012
     dvi:           Version      - 5.40.0.27939
     dvi: {Build Driver List - exit(0x00000000)} 10:54:37.106
     dvi: {DIF_SELECTBESTCOMPATDRV} 10:54:37.106
     dvi:      Default installer: Enter 10:54:37.106
     dvi:           {Select Best Driver}
     dvi:                Class GUID of device changed to: {4d36e972-e325-11ce-bfc1-08002be10318}.
     dvi:                Selected:
     dvi:                     Description - [Juniper Networks Virtual Adapter]
     dvi:                     InfFile     - [c:\windows\system32\driverstore\filerepository\jnprva.inf_amd64_80b297ba301623ad\jnprva.inf]
     dvi:                     Section     - [JnprVa.Ndi]
     dvi:           {Select Best Driver - exit(0x00000000)}
     dvi:      Default installer: Exit
     dvi: {DIF_SELECTBESTCOMPATDRV - exit(0x00000000)} 10:54:37.106
     ndv: {Core Device Install} 10:54:37.106
     ndv:      {Install Device - {FE36527A-8C07-4854-8AF7-BF40E7DF52F7}\JNPRVA\0001} 10:54:37.106
     ndv:           Parent device: ROOT\JNPRVAMGR\0000
     ndv:           {Configure Device - {FE36527A-8C07-4854-8AF7-BF40E7DF52F7}\JNPRVA\0001} 10:54:37.122
     ndv:                Parent device: ROOT\JNPRVAMGR\0000
     sto:                {Configure Driver Package: C:\Windows\System32\DriverStore\FileRepository\jnprva.inf_amd64_80b297ba301623ad\jnprva.inf}
     sto:                     Source Filter  = {fe36527a-8c07-4854-8af7-bf40e7df52f7}\jnprva
     inf:                     Class GUID     = {4d36e972-e325-11ce-bfc1-08002be10318}
     inf:                     Class Options  = Configurable
     inf:                     {Configure Driver: Juniper Networks Virtual Adapter}
     inf:                          Section Name = JnprVa.Ndi
     inf:                          {Add Service: jnprva}
     inf:                               Start Type    = 3
     inf:                               Service Type  = 1
     inf:                               Error Control = 1
     inf:                               Image Path    = \SystemRoot\System32\drivers\jnprva.sys
     inf:                               Display Name  = Juniper Networks Virtual Adapter Service
     inf:                               Group         = NDIS
     inf:                               Updated service 'jnprva'.
     inf:                          {Add Service: exit(0x00000000)}
     inf:                          Hardware Id  = {FE36527A-8C07-4854-8AF7-BF40E7DF52F7}\JNPRVA
     inf:                          {Configure Driver Configuration: JnprVa.Ndi}
     inf:                               Service Name  = jnprva
     inf:                               Config Flags  = 0x00000000
     inf:                          {Configure Driver Configuration: exit(0x00000000)}
     inf:                     {Configure Driver: exit(0x00000000)}
     flq:                     Copying 'C:\Windows\System32\DriverStore\FileRepository\jnprva.inf_amd64_80b297ba301623ad\jnprva.sys' to 'C:\Windows\System32\drivers\jnprva.sys'.
     cpy:                     Existing file 'C:\Windows\System32\drivers\jnprva.sys' remains unchanged.
     sto:                {Configure Driver Package: exit(0x00000000)}
     dvi:                Install Device: Configuring device (oem35.inf:{fe36527a-8c07-4854-8af7-bf40e7df52f7}\jnprva,JnprVa.Ndi). 10:54:37.150
     dvi:                Install Device: Configuring device completed. 10:54:37.165
     dvi:                Install Device: Starting device. 10:54:37.165
     dvi:                Install Device: Starting device completed. 10:54:47.237
     ndv:           {Configure Device - exit(0x00000000)} 10:54:47.237
     ndv:      {Install Device - exit(0x00000000)} 10:54:47.261
     ndv: {Core Device Install - exit(0x00000000)} 10:54:47.263
     ndv: Waiting for device post-install to complete. 10:54:47.265
!!!  ndv: Timed out waiting for device post-install to complete. 10:58:47.285
<<<  Section end 2019/05/13 10:58:47.400
<<<  [Exit status: FAILURE(0x000005b4)]

 

 

Moderator
Moderator

Re: Unable to configure virtual adapter after reinstalling Pulse

@mwhite I am seeing a driver time-out error from the setupapi logs.

 

     ndv: Waiting for device post-install to complete. 10:54:47.265
!!!  ndv: Timed out waiting for device post-install to complete. 10:58:47.285

Please follow the below steps and update the thread:


# Network Drivers:

1. Open Run command.

2. Type ncpa.cpl

3. Right click on any adapter like Physical NIC.

4. Click on Properties >> Take a screenshot of all the loaded drivers.

 

 

Occasional Contributor

Re: Unable to configure virtual adapter after reinstalling Pulse

Moderator
Moderator

Re: Unable to configure virtual adapter after reinstalling Pulse

Thank you for attaching the screenshot link.

1. What's status of Base Filtering Engine (BFE) under services.msc?

2. Have you set the MaxNumFilters registry value to 14.

3..Most importantly, are you able to see Juniper virtual !!Adapter manager!! and Juniper Virtual !!Adapter!! listed as network adapters under the device manager? Change view settings or show the hidden devices (view >> show hidden devices)

4. Please execute the following command in cmd and share the results (drivers.txt on C:\ drive).

pnputil /enum-drivers >> C:\drivers.txt
Occasional Contributor

Re: Unable to configure virtual adapter after reinstalling Pulse

1. BFE is on and running

2.  DWORD value already exists and is set to 14 (decimal).

3.  Yes we see both of them and there's no warning

4.  drivers.txt: https://pastebin.com/5JRZzP6b

Moderator

Re: Unable to configure virtual adapter after reinstalling Pulse

are you able to manually delete the adapter (.sys) file and registry values?
i would recommend opening a case with our support team for further investigation.
Occasional Contributor

Re: Unable to configure virtual adapter after reinstalling Pulse

Where would those files and registry values be located?

 

Also I edited my above reply to include drivers.txt: https://pastebin.com/5JRZzP6b

Moderator
Moderator

Re: Unable to configure virtual adapter after reinstalling Pulse

Thank you for providing the drivers list. It seems that Checkpoint VPN client's driver is running on the machine.

Driver Instances:

Published Name: oem43.inf
Original Name: netvna.inf
Provider Name: Check Point
Class Name: Network adapters
Class GUID: {4d36e972-e325-11ce-bfc1-08002be10318}
Driver Version: 11/14/2007 1.1.0.0
Signer Name: Microsoft Windows Hardware Compatibility Publisher

Published Name: oem38.inf
Original Name: vsdatant.inf
Provider Name: Check Point Software Technologies Ltd.
Class Name: Network Service
Class GUID: {4d36e974-e325-11ce-bfc1-08002be10318}
Driver Version: 05/19/2010 8.0.804.0
Signer Name: Microsoft Windows Hardware Compatibility Publisher

Is Checkpoint VPN client installed? If yes, please uninstall and try to connect using Pulse Client.