I think I know why this is happening and Pulse Secure is about to have a major problem in about a month when the new version of Windows 11 releases. In the PulseClient.log I can see that they are trying to find there adapater that gets created when you connect. In the newer builds Juniper Networks Virtual Adapter is never found. But IF I go to powershell I can see it listed so it gets created. Note it also is not shown in the network control panel. From the logs I am assuming that they are using GetAdaptersInfo api call for this info. May be just a bad log message but if correct they are using a massively old depricated api see https://docs.microsoft.com/en-us/windows/win32/api/iphlpapi/nf-iphlpapi-getadaptersinfo. I have been trying to look at these interfaces to see how MS decides which ones to report but have not had any luck. My hope is that a simple registry hack may make this work. I am supper disapointed that Ivanti isn't all over this.
... View more
