[email protected] wrote:@aleiby Ok. Please review the setupapi.dev.log under C:\WINDOWS\INF folder and check the events printed there for JNPRVA startup.
BTW, do you have any other VPN client installed?
No other VPN client installed.
There is a lot of JNPRVA activity in the log since I had tried uninstalling and reinstalling a couple times.
The last Device Install entry:
>>> [Device Install (DiShowUpdateDevice) - {FE36527A-8C07-4854-8AF7-BF40E7DF52F7}\JNPRVA\0001] >>> Section start 2021/10/30 11:26:36.834 cmd: "C:\WINDOWS\system32\mmc.exe" C:\WINDOWS\system32\devmgmt.msc dvi: {DIF_UPDATEDRIVER_UI} 11:26:36.836 dvi: Default installer: Enter 11:26:36.837 dvi: Default installer: Exit dvi: {DIF_UPDATEDRIVER_UI - exit(0xe000020e)} 11:26:36.839 ndv: {Update Driver Software Wizard - {FE36527A-8C07-4854-8AF7-BF40E7DF52F7}\JNPRVA\0001} ! ndv: Searching Windows Update has been disabled for the Update Wizard. ! ndv: Policy has been set to prevent searching Windows Update for drivers. ndv: Search options: 0x00000003 ndv: Searching currently installed INF dvi: {Build Driver List} 11:26:38.069 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_b96098c9161408ef\jnprva.inf dvi: DevDesc - Juniper Networks Virtual Adapter dvi: Section - JnprVa.ndi dvi: Rank - 0x00ff0000 dvi: Signer Score - WHQL dvi: DrvDate - 05/24/2021 dvi: Version - 9.1.12.9087 dvi: {Build Driver List - exit(0x00000000)} 11:26:38.093 ndv: Searching default INF path dvi: {Build Driver List} 11:26:38.095 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_b96098c9161408ef\jnprva.inf dvi: DevDesc - Juniper Networks Virtual Adapter dvi: Section - JnprVa.ndi dvi: Rank - 0x00ff0000 dvi: Signer Score - WHQL dvi: DrvDate - 05/24/2021 dvi: Version - 9.1.12.9087 dvi: {Build Driver List - exit(0x00000000)} 11:26:38.154 dvi: {DIF_SELECTBESTCOMPATDRV} 11:26:38.155 dvi: Default installer: Enter 11:26:38.157 dvi: {Select Best Driver} dvi: Class GUID of device changed to: {4d36e972-e325-11ce-bfc1-08002be10318}. dvi: {DIF_DESTROYPRIVATEDATA} 11:26:38.160 dvi: Default installer: Enter 11:26:38.161 dvi: Default installer: Exit dvi: {DIF_DESTROYPRIVATEDATA - exit(0xe000020e)} 11:26:38.163 dvi: Selected Driver: dvi: Description - Juniper Networks Virtual Adapter dvi: InfFile - c:\windows\system32\driverstore\filerepository\jnprva.inf_amd64_b96098c9161408ef\jnprva.inf dvi: Section - JnprVa.ndi dvi: {Select Best Driver - exit(0x00000000)} dvi: Default installer: Exit dvi: {DIF_SELECTBESTCOMPATDRV - exit(0x00000000)} 11:26:38.171 ndv: {Update Driver Software Wizard exit(000004c7)} <<< Section end 2021/10/30 11:26:40.240 <<< [Exit status: FAILURE(0x000004c7)]
Note the Exit status FAILURE there at the end.
This is then followed by several network binding disabled entries like these:
>>> [Set network binding disabled - jnprns->NonPnpNetworkInterface\{548EFC27-C9D4-4E4D-B2C8-95928C5EE6A7}] >>> Section start 2021/10/30 11:31:06.254 cmd: "C:\Program Files (x86)\Common Files\Pulse Secure\JUNS\PulseSecureService.exe" <<< Section end 2021/10/30 11:31:06.255 <<< [Exit status: SUCCESS] >>> [Set network binding disabled - jnprns->{FE36527A-8C07-4854-8AF7-BF40E7DF52F7}\JNPRVA\0001] >>> Section start 2021/10/30 11:31:06.295 cmd: "C:\Program Files (x86)\Common Files\Pulse Secure\JUNS\PulseSecureService.exe" <<< Section end 2021/10/30 11:31:06.300 <<< [Exit status: SUCCESS]
I didn't see anything that mentioned "startup".
@aleiby Thanks for sharing the log excerpts.
[Device Install (DiShowUpdateDevice) - {FE36527A-8C07-4854-8AF7-BF40E7DF52F7}\JNPRVA\0001]
I believe this is a driver update event through Windows Update which will fail as we can install JNPRVA only through MSI package. Normally, we will see Hardware Initiated (DevicePlugandPlayDriver) install, hence am not sure why the Device Install is attempted through Windows Update.
This could be something caused by the Windows Update, is it possible to file a support ticket with us through your IT helpdesk?
(I'm downloading Windows 11 ISO now for attempting this in my lab as this super interesting...)
Here is the last Hardware Initiated logging:
>>> [Setup online Device Install (Hardware initiated) - {FE36527A-8C07-4854-8AF7-BF40E7DF52F7}\JNPRVA\0001] >>> Section start 2021/10/30 11:26:06.017 ump: Install needed due to device having problem code CM_PROB_NOT_CONFIGURED utl: {Select Drivers - {FE36527A-8C07-4854-8AF7-BF40E7DF52F7}\JNPRVA\0001} 11:26:06.025 utl: Driver Node: utl: Status - Selected utl: Driver INF - oem8.inf (C:\WINDOWS\System32\DriverStore\FileRepository\jnprva.inf_amd64_b96098c9161408ef\jnprva.inf) utl: Class GUID - {4d36e972-e325-11ce-bfc1-08002be10318} utl: Driver Version - 05/24/2021,9.1.12.9087 utl: Configuration - {FE36527A-8C07-4854-8AF7-BF40E7DF52F7}\JNPRVA utl: Driver Rank - 00FF0000 utl: Signer Score - WHQL (0D000005) utl: {Select Drivers - exit(0x00000000} 11:26:06.036 dvi: {Core Device Install} 11:26:06.037 dvi: {Configure Device - {FE36527A-8C07-4854-8AF7-BF40E7DF52F7}\JNPRVA\0001} 11:26:06.039 dvi: Device Status: 0x41802400 [0x01 - 0xc0000493] dvi: Parent Device: ROOT\JNPRVAMGR\0000 sto: {Configure Driver Package: C:\WINDOWS\System32\DriverStore\FileRepository\jnprva.inf_amd64_b96098c9161408ef\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: Reactivating service 'jnprva' pended for deletion. 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: {FILE_QUEUE_COMMIT} 11:26:06.075 flq: Copying 'C:\WINDOWS\System32\DriverStore\FileRepository\jnprva.inf_amd64_b96098c9161408ef\jnprva.sys' to 'C:\WINDOWS\System32\drivers\jnprva.sys'. flq: {FILE_QUEUE_COMMIT - exit(0x00000000)} 11:26:06.082 dvi: Existing files modified, may need to restart related services. sto: {Configure Driver Package: exit(0x00000bc3)} dvi: Restart required for any devices using this driver. dvi: Install Device: Configuring device. 11:26:06.087 dvi: Configuration: oem8.inf:{FE36527A-8C07-4854-8AF7-BF40E7DF52F7}\JNPRVA,* dvi: Install Device: Configuring device completed. 11:26:06.092 dvi: Device Status: 0x41802000 dvi: {Restarting Devices} 11:26:06.094 dvi: Start: {FE36527A-8C07-4854-8AF7-BF40E7DF52F7}\JNPRVA\0001 ! dvi: Device '{FE36527A-8C07-4854-8AF7-BF40E7DF52F7}\JNPRVA\0001' pending start: Device has problem: 0x38 (CM_PROB_NEED_CLASS_CONFIG), problem status: 0x00000000. dvi: {Restarting Devices exit} 11:26:06.115 dvi: {Configure Device - exit(0x00000000)} 11:26:06.117 dvi: {Core Device Install - exit(0x00000000)} 11:26:06.118 dvi: Waiting for device post-install to complete. 11:26:06.121 dvi: Device post-install completed. 11:26:06.225 ! dvi: Device Status: 0x41802400 [0x0a - 0xc0000001] <<< Section end 2021/10/30 11:26:06.229 <<< [Exit status: SUCCESS]
I have forwarded this thead to my IT dept. Thanks!
Thank you for sharing the hardware initiated part, Device status shows 0x41802400 - DN_HAS_PROBLEM (0x00000400)
! dvi: Device Status: 0x41802400 [0x0a - 0xc0000001]
Whereas, the working installation should has Device Status: 0x0180200a - which means loaded and started.
Fyi, I have since tried installing the latest motherboard chipset drivers, disabled both Wi-Fi and Bluetooth in the BIOS, upgraded to the latest BIOS version, and again reinstalled the Pulse client. None of these have made any difference. I also tested w/ hardware virtualization disabled since that got reset when I upgraded the BIOS. I am running an Asus ROG Strix X570-I.
@aleiby What AV do you have installed? Is it possible to disable or uninstall the AV and repair/reinstall the PDC installation and then reinstall the AV back?
Just Windows 11's built in AV. Disabled and reinstalled Pulse. Issue remains.
Hi!
I have reviewed the entire conversation, and have the same exact issue (0xC00000E5) until code 1205 after timeout, output from commands and logs appear the same too.
I have already tried to completely reset my entire networking adatpers and stacks with all I had. No external AV just the one from built in to Windows 11. Re-install Pulse Secure etc.
Windows OS Version: 10.0.22489 Build 22489
This issue started last week after a recent patch update from Microsoft.
I have also tried to enable "Juniper network service" on my WLAN adapter which I am using to establish my connections through VPN. This has not helped either.
This problem is sincenerly affecting my abiltiy to work and I am hoping you have any information which could help me resolve this before I re-install my PC with Windows 10.
Thanks and BR,
GlennG
I suspect this is an issue that will need to be fixed on Microsoft's side. I created an issue on their Feedback hub when first encountering this here in case you want to vote it up: https://aka.ms/AAeqo3b
Thanks.
JFYI, I did a restore, using windows restore and rolled back to Windows OS Version: 10.0.22483 Build 22483.
After that I uninstalled Pulse and all components using install/remove programs and then removed all reg-keys I could find related to Pulse. Also removed all app-data and program-data, program-files etc I could find related to Pulse and rebooted.
Once windows was up again, I re-installed Pulse using the latest available version of pulse secure, and configured my VPN profile... But the connection is still failing in the same way as before the rollback.
I get to "Securing connection" - and then the virtual juniper adapter fails!
Here's some captures events:
------------------------------------------------------------------
Device {FE36527A-8C07-4854-8AF7-BF40E7DF52F7}\JNPRVA\0001 had a problem starting.
Driver Name: oem30.inf
Class Guid: {4d36e972-e325-11ce-bfc1-08002be10318}
Service: jnprva
Lower Filters:
Upper Filters:
Problem: 0x0
Problem Status: 0xC00000E5
------------------------------------------------------------------
Device {FE36527A-8C07-4854-8AF7-BF40E7DF52F7}\JNPRVA\0001 was configured.
Driver Name: oem30.inf
Class Guid: {4d36e972-e325-11ce-bfc1-08002be10318}
Driver Date: 12/31/2020
Driver Version: 9.1.11.6235
Driver Provider: Juniper Networks
Driver Section: JnprVa.ndi
Driver Rank: 0xFF0000
Matching Device Id: {FE36527A-8C07-4854-8AF7-BF40E7DF52F7}\JNPRVA
Outranked Drivers:
Device Updated: false
------------------------------------------------------------------
Device settings for {FE36527A-8C07-4854-8AF7-BF40E7DF52F7}\JNPRVA\0001 were not migrated from previous OS installation due to partial or ambiguous device match.
Last Device Instance Id: SW\{eeab7790-c514-11d1-b42b-00805fc1270e}\asyncmac
Class Guid: {4d36e972-e325-11ce-bfc1-08002be10318}
Location Path:
Migration Rank: 0xF000FFFFFFFFF122
Present: false
Status: 0xC0000719
BR,
GlennG