topic Re: Virtual Adapter was not setup correctly due to a delay (WIN10) in GlobalProtect Discussions

Virtual Adapter was not setup correctly due to a delay (WIN10)

labodemoza — Fri, 24 Mar 2023 17:33:00 GMT

I'm using GlobalProtect Ver 5.2.12-26, on my windows 10 laptop and it has worked just fine for last month, but recently I continue to get the "Virtual Adapter was not setup correctly due to a delay". I've completely uninstalled/reinstalled a number of times with no success. I did notice in the following setup file logs: Driverinfo, Serviceinfo, and Processinfo it states "ERROR: Description = Invalid namespace"

Does anybody know what this means and how to resolve it? The closest online documentation I found is the following:

We also use WMI queries to populate files like DriverInfo.txt, ServiceInfo.txt and ProcessInfo.txt. Check these files in the GP logs for the following error which indicates failure of the WMI queries:

ERROR:

Description = Invalid class

NOTE: It does show the PANGPS was installed successfully:

Verify if PanGP virtual adapter is installed correctly using the following log from setupapi.dev.log:

dvi: Waiting for NetSetupSvc to finish installing ROOT\PANGPD\0000
dvi: Install finished for ROOT\PANGPD\0000

Any help would be appreciated

Re: Virtual Adapter was not setup correctly due to a delay (WIN10)

SeanPMcAdam — Fri, 01 Mar 2024 19:54:24 GMT

I haven't had a chance to test yet, but a coworker found these results that I'm curious to see if they might work:

Palo Alto | LIVEcommunity: The virtual adapter was not set up correctly due to a delay. GlobalProtect will try again soon.
- Winmgmt /resetrepository
Microsoft | Community: cannot access the windows management instrumentation software

Method 1: You may follow these steps and check if the issue persists.

1. Press windows key + X key both together on the keyboard.

2. Select Command Prompt (Admin)

3. Run the following command one at a time and press enter to execute

• cd /d %windir%\system32\wbem

• for %i in (*.dll) do regsvr32 -s %i

• for %i in (*.exe) do %i /regserver

4. Close all windows and reboot the computer and now try opening the system information

Method 2: If the issue still persists try rebuilding WMI repository and check if the issue persists.

1. Press windows key + X key both together on the keyboard.
2. Select Command Prompt (Admin)

3. Type the command ‘net stop winmgmt’ and press Enter.

4. Leave the command prompt open and click Start and type system32 -> Open the folder system32 from the result pane.

5. From the system32 folder open Wbem and look for the folder Repository

6. Right click on Repository and click rename.

7. Change the folder name from Repository to Repository.old

8. Switch back to command prompt and type net start winmgmt and hit enter to execute

9. Close all the windows and reboot the computer and now try opening the system information.

Re: Virtual Adapter was not setup correctly due to a delay (WIN10)

diisaa — Thu, 21 Mar 2024 11:00:58 GMT

I have written a blog on how to solve this problem and how to avoid troubleshooting it manually:
https://www.endpointarc.com/2024/03/20/automating-wmi-namespace-issues-detection-and-remediation-for-network-adapters/

Re: Virtual Adapter was not setup correctly due to a delay (WIN10)

SeanPMcAdam — Thu, 21 Mar 2024 15:37:26 GMT

Thanks for sharing! Definitely going to run through that & see about putting a check like that in place.

Re: Virtual Adapter was not setup correctly due to a delay (WIN10)

Mdaver1_PS — Thu, 01 Aug 2024 20:03:15 GMT

HI Ditor Sahiti,

Thank you very much! Your script solved my issue.

I simply run your script ( I am local admin) .

After some Windows update, the GlobalProtect client on my laptop could not connect. The error message read: "globalprotect virtual adapter was not set up correctly due to a delay".

Your script created this logs while it was fixing my issue:

======== WMIRemediation.log ============

08/01/2024 12:48:41 - Error occurred: Invalid class in network adapters.
08/01/2024 12:48:41 - WMI class appears to be missing. Attempting to fix...
08/01/2024 12:48:41 - Stopping ConfigManager service if it exists
08/01/2024 12:48:41 - Temporarily disabling Windows Management Instrumentation service
08/01/2024 12:48:41 - Stopping Windows Management Instrumentation service
08/01/2024 12:48:41 - Running commands to re-register WMI components
08/01/2024 12:50:09 - Setting Windows Management Instrumentation service back to Automatic
08/01/2024 12:50:09 - Starting Windows Management Instrumentation service
08/01/2024 12:50:09 - Executed mofcomp on 'ExtendedStatus.mof'
08/01/2024 12:50:10 - Running ConfigMgr Evaluation
08/01/2024 12:50:12 - Remediation process completed
08/01/2024 12:50:12 - Error still present: Invalid class in network adapters. Running additional fix.
08/01/2024 12:50:12 - Remediation process completed

Re: Virtual Adapter was not setup correctly due to a delay (WIN10)

Alexander Schrader — Wed, 29 Jan 2025 07:34:07 GMT

Issue Root cause: Windows sometimes tries to enable the GP virtual adapter earlier than any underlying network interface right after resuming from a power event, this causes the CM_PROB_NEED_RESTART flag set to the GP virtual adapter and GP will fail the tunnel the next time when it tries to connect since it thinks the reboot is required.

logs analyzed:
------------------

PAN GPS:
----------------

(P6712-T22240)Error(6954): 01/27/25 12:49:37:942 NetworkDiscoverThread: failed to discover external network.
(P6712-T22240)Debug(6960): 01/27/25 12:49:37:942 local system error, set error as The virtual adapter was not set up correctly due to a delay. GlobalProtect will try again soon. If the issue persists, try restarting your system.
(P6712-T22240)Debug(8057): 01/27/25 12:49:37:942 --Set state to Disconnected

Resolution:
-----------------

The fix for this has already been reported under GPC-20592 and the target fix versions are given below:

Fix Version/s: 6.3.3, 6.2.6-h1, 6.2.6-h2

For reference: https://docs.paloaltonetworks.com/globalprotect/6-2/globalprotect-app-release-notes/globalprotect-addressed-issues