topic Re: The virtual adapter was not set up correctly due to a delay. GlobalProtect will try again soon. in GlobalProtect Discussions

The virtual adapter was not set up correctly due to a delay. GlobalProtect will try again soon.

MohammedAsik — Thu, 28 Jan 2021 07:48:06 GMT

Hi Team

After upgraded the Global protect from 4.1.9 to 5.1.8. Few of the Gp clients not connected. If I repair the Global protect its working fine.

So checked the PANGP event logs and found the below error

Tunnel is down due to disconnection.
01/28/2021 11:21:33.772 [Error]: Failed to get default route entry

01/28/2021 11:21:33.772 [Info ]: Tunnel is down due to disconnection.
01/28/2021 11:21:34.354 [Error]: The virtual adapter was not set up correctly due to a delay. GlobalProtect will try again soon. If the issue persists, please restart your system.

Please help us to fix the issue. Why its showing error after upgrade the GP to 5.1.8 version

Regards

Mohammed Asik

Re: The virtual adapter was not set up correctly due to a delay. GlobalProtect will try again soon.

mcloudteo — Tue, 16 Mar 2021 06:54:55 GMT

Any solution?

Re: The virtual adapter was not set up correctly due to a delay. GlobalProtect will try again soon.

bartlettj — Mon, 22 Mar 2021 12:01:31 GMT

What was the solution?

Re: The virtual adapter was not set up correctly due to a delay. GlobalProtect will try again soon.

Dekkar — Sun, 28 Mar 2021 23:43:45 GMT

Had this problem also. Uninstall/reinstall fixed it for a few weeks, but I just had one laptop have the same issue again. Machine is W10 20H2 client is 5.2.4-21

Re: The virtual adapter was not set up correctly due to a delay. GlobalProtect will try again soon.

aljadot — Wed, 31 Mar 2021 15:07:08 GMT

Does anybody knows what to do with that?

Re: The virtual adapter was not set up correctly due to a delay. GlobalProtect will try again soon.

Akhil_B — Tue, 13 Apr 2021 15:25:46 GMT

I have the same issue, Did you get any solution? @MohammedAsik

Re: The virtual adapter was not set up correctly due to a delay. GlobalProtect will try again soon.

Akhil_B — Mon, 19 Apr 2021 14:02:32 GMT

@MohammedAsik @aljadot @Dekkar @bartlettj @mcloudteo

I found a workaround/fix to this problem.

Resolution:

1) Make sure it is not the problem with the drivers, for this check your device manager and uninstall the Virtual adapter by checking the uninstall the driver software as well and then uninstall and reinstall the GP client. If this does not fix the issue, follo these steps.

- Disable WMI services : run - services.msc - Windows Management Instrumentation(WMI) - stop the service.
- Delete the files under C:\Windows\System32\wbem\Repository
- Open regedit
  Go to HKEY_LOCAL_MACHINE > Software and HKEY_CURRENT_USER > Software. Delete the Palo Alto Networks folder.
- Delete the same if the same folder is present in any other user under HKEY_USERS.
- Un-install GlobalProtect from Windows 'program and features'.
- Make sure that the virtual adapter in not present in the Network adapter settings.
- Reboot the machine.
- Reinstall GlobalProtect with admin privileges.
- Confirm that WMI service is running.
This should resolve the issue.

Re: The virtual adapter was not set up correctly due to a delay. GlobalProtect will try again soon.

PiankaMariusz — Thu, 22 Jul 2021 11:43:23 GMT

Dear PAN Engineers, Customers, seeking for help on error:

"The virtual adapter was not set up correctly due to a delay. GlobalProtect will try again soon"

We have encountered random computers who have suddenly stopped connecting to global protect.

Reinstalling Global Protect doesn't fix the issue, none of the steps discussed here fix it.

The discovery was made that Windows 10 21H1 update affects WMI

The best diagnostics you can do is enter into start-->run-->msinfo32 or msinfo32 into cmd prompt.

If you see errors that WMI was moved or inaccessible you can try Microsoft Article:

https://answers.microsoft.com/en-us/windows/forum/all/cannot-access-the-windows-management/75284a7d-8b8a-491b-afab-15fe465b4b53

What fixed my issue was

Winmgmt /resetrepository

msinfo32 functionality restored ( I can see data )

Global Protect connects without an issue.

Please note, WMI service was always running.

Re: The virtual adapter was not set up correctly due to a delay. GlobalProtect will try again soon.

MuhamedBasic — Thu, 07 Oct 2021 10:27:41 GMT

Thanks!

Re: The virtual adapter was not set up correctly due to a delay. GlobalProtect will try again soon.

Dan_Morin — Tue, 30 Nov 2021 20:58:43 GMT

Using the Winmgmt /resetrepository worked for me, and I wasn't seeing any errors when launching the msinfo32
I believe the WinMgmt command stops the service for you, as initially I had an error that there were dependencies to the service.
When I stopped the service, which informed me there were two Dell services dependent on it, then I could successfully run the command.

I hadn't checked if the WMI or Dell services had restarted, so hopefully nether of these were causing the GP failure.

Re: The virtual adapter was not set up correctly due to a delay. GlobalProtect will try again soon.

Russland — Tue, 12 Jul 2022 06:05:53 GMT

Sadly it didn't work for me. When I use it:

winmgmt /resetrepository
Fehler beim Zurücksetzen des WMI-Repositorys
Fehlercode: 0x8007007E

So I get an error. I tried it in user and administrator context.

Re: The virtual adapter was not set up correctly due to a delay. GlobalProtect will try again soon.

bilal_guclu — Fri, 06 Jan 2023 12:08:02 GMT

Hello guys,

I have same problem but on MacOS. I dont find anything this issue. Has anyone had a similar problem on macOS and found a solution?We have been using version 5.2.11 for a long time in GP.

Re: The virtual adapter was not set up correctly due to a delay. GlobalProtect will try again soon.

Nate_Cartwright — Thu, 12 Jan 2023 20:03:50 GMT

FYI, if resetting the WMI Repository doesn't work, and an sfc and dism repair doesn't work, disabling the Dell Data Vault services (they depend on WMI as well), and running this script and rebooting worked for us:

FIXWMI.CMD
------------------------

@echo on
cd /d c:\temp
if not exist %windir%\system32\wbem goto TryInstall
cd /d %windir%\system32\wbem
net stop winmgmt
winmgmt /kill
if exist Rep_bak rd Rep_bak /s /q
rename Repository Rep_bak
for %%i in (*.dll) do RegSvr32 -s %%i
for %%i in (*.exe) do call :FixSrv %%i
for %%i in (*.mof,*.mfl) do Mofcomp %%i
net start winmgmt
goto End

:FixSrv
if /I (%1) == (wbemcntl.exe) goto SkipSrv
if /I (%1) == (wbemtest.exe) goto SkipSrv
if /I (%1) == (mofcomp.exe) goto SkipSrv
%1 /RegServer

:SkipSrv
goto End

:TryInstall
if not exist wmicore.exe goto End
wmicore /s
net start winmgmt
:End

Re: The virtual adapter was not set up correctly due to a delay. GlobalProtect will try again soon.

Eric_Barger — Wed, 08 Mar 2023 16:16:46 GMT

My servicedesk team ran this batch file to resolve this. So far it has worked on all PCs. We are running GP 6.0.4-c26

C:\Windows\System32\Wbem. @echo off sc config winmgmt start= disabled net stop winmgmt /y %systemdrive% cd %windir%\system32\wbem for /f %%s in ('dir /b *.dll') do regsvr32 /s %%s wmiprvse /regserver winmgmt /regserver sc config winmgmt start= auto net start winmgmt for /f %%s in ('dir /s /b *.mof *.mfl') do mofcomp %%s

Re: The virtual adapter was not set up correctly due to a delay. GlobalProtect will try again soon.

AaronAxvig — Wed, 17 Apr 2024 13:23:11 GMT

Running this script and rebooting resolved the issue on a few PCs for me lately.

Re: The virtual adapter was not set up correctly due to a delay. GlobalProtect will try again soon.

JCSMITH85 — Tue, 16 Jul 2024 20:22:39 GMT

We just solved this on my machine by creating a batch script out of the following.

net stop winmgmt /y

%SYSTEMDRIVE%

CD %windir%\system32\wbem

rd /S /Q repository

net start winmgmt

for /f %%s in ('dir /b /s *.dll') do regsvr32 /s %%s

for /f %%s in ('dir /b *.mof') do mofcomp %%s

Run that, restart, and there you go.

Re: The virtual adapter was not set up correctly due to a delay. GlobalProtect will try again soon.

rejamer — Fri, 19 Jul 2024 20:58:12 GMT

This worked when all else failed - Thanks!

Re: The virtual adapter was not set up correctly due to a delay. GlobalProtect will try again soon.

Sanjith-Nimshad — Thu, 25 Jul 2024 10:05:31 GMT

How do you run this batch file? I have a user experiencing the same issue on 6.1.4.

Re: The virtual adapter was not set up correctly due to a delay. GlobalProtect will try again soon.

Alexander Schrader — Wed, 29 Jan 2025 07:33:12 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

Re: The virtual adapter was not set up correctly due to a delay. GlobalProtect will try again soon.

DanielS.Romero — Wed, 11 Jun 2025 15:38:14 GMT

Hello Livecommunity!

I ran this cmd commands with admins privileges and then GP version 6.0.7 connects succesfully:

net stop pangps
winmgmt /resetrepository
sc config winmgmt start=disabled
net stop winmgmt /y
cd C:\Windows\System32\wbem\
rename repository repository.gp ----> (It could doesn't exist, try the next command)
sc config winmgmt start=auto
net start winmgmt
for /f %s in ('dir /b *.mof') do mofcomp %s
for /f %s in ('dir /b en-us\*.mfl') do mofcomp en-us\%s
net start pangps

This issue is known with the ID GPC-20592

Hope this information could be useful!!

Best Regards,