VPN connection problem after Windows 11 Pro 24H2 update

This worked like a charm to me! After enabling the issue is gone! Thanks a lot...

[POTENTIAL LOCAL WORKAROUND (for me)]

I've got similar issue with my company's notebook's VPNs.

All problems which come out of it seem to boil down into lack of proper suffixing of DNS requests with my company domain. FQDN requests always pass, abbreviated ones - sometimes, sometimes not.
In short - I've 'added' company's domain as dns suffix into my local wifi connection IP settings - it solved this issue.

So, in "View Network Connections" I have my local Wi-Fi connection, plus few additional connections for windows VPNs. Of course all VPN connection shortcuts in their IPV4 settings have DNS suffixes for my company domain.
I'm assuming that the dns suffix sould get added with a 'connection specific' (VPN) network connection - once such VPN is activated. But obviously this setting (adding 'connection specific dns suffixes') is not respected by Windows 11 24H2. It seems like in this windows 11 configuration ONLY THE primary network connection DNS suffixes are respected.
I've manually added (enforced) my company domain name into my 'private' WiFi connection as additional suffix.

I know it would make bogus searches when I'm not connected to my company, but hey... At least it works. I hope it doesn't introduce any security issues. In 99% of cases I'm connected to internet on my company notebook.

Maybe it helps someone out there.

If I install an earlier version of NetExtender, it will connect just fine. Something in the latest 10.3.1 is causing the issue.

Same issue with company Checkpoint VPN. Internet connection would be fine until I connected to VPN then lost all connectivity to the internet. Rolled back the update, went back to 23H2 and all is well.

Using MS Built-in VPN Client here and still all 24H2 users are routinely experiencing VPN connection issues and slow backend RRAS responsiveness. I posted a similar discussions elsewhere and am seeing many of the same complaints here. Incredibly frustrating.