This workaround is working great up to WIndows 11 build 22557.
Then the workaround is not working anymore.
This workaround is not working on build 22557.
Any news? Or is Ivanti still sleeping?
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
Verified still broken in Version 22H2 Build 22572.201
I am running 22H2 Build 22572.201 too. And the fix does still work!
https://glenng.net/tmp/PulseFix/jnprva.zip extract and copy to C:\Windows\System32\drivers
But note, PulseSecure appears to replace this file somtimes, and Windows updates too.
And even this "fix" does not work if you have failed connection attempts already. You will need to restart your PC, and then, and I know it seems silly but my routine is this:
When Windows comes up, I shut down pulse. Copy the file to Drivers folder; Start Pulse, Copy the file again to Drivers folder, and I always have successful connections using this "method"
But it's a shame Pulse Secure have not made proper update available for Windows 11 yet. When can we expect that to happen? Or any information really... @zanyterp [email protected]
No, I am on a unsupported OS from our IT perspective and they will not open a ticket. For a company supporting Enterprise products I would expect Ivanti to be testing the upploing OS releases to not be caught of guard. Much better to do things with planing rather than reactionary.
So what is different about this driver, and why doesn't ivanti deploy pulse secure with it?
also this fix still working on windows dev build 22579