AWS client VPN v.5.0.1 not working on Windows 11 machine

Hello.

Are there any errors output when checking the log files listed in the document below?
https://docs.aws.amazon.com/vpn/latest/clientvpn-user/windows-troubleshooting.html

Definitely worth looking at the logs in order to check this further. However, please find the following checks that you can perform whilst awaiting for logs

• Please try selecting the proper TAP adapter when the CVPN tries to connect

 - Have seen this issue wherein the netsh is not able to rename the adapter in CVPN v5
 - This check would mean that the netsh is not able to rename the adapter on user system
 - Meaning this is specific to client

• Please try checking the windows update on on client's system

-  When Windows 11 23H2 is updated to 24H2, AWS client VPN will no longer function. When the user attempts to connect, it creates a new TAP-adapter, you can view this in device manager.
- Currently there is Microsoft post that refers to update causing issues with OpenVPN based connection :
https://answers.microsoft.com/en-us/windows/forum/all/vpn-connection-problem-after-windows-11-pro-24h2/c50c1413-11eb-4627-afab-750aa6fbb05e
- Proposed solution: Revert back to 23H2

- To revert back to the last Microsoft 23H2 patch within 10 days, open your Windows Settings, navigate to "System > Recovery," and select "Go back" - this option should be available if you're within the 10-day rollback window; simply follow the on-screen instructions to return to the previous version of Windows without losing your personal files, but be aware that recently installed apps and driver changes might be removed.

I would be more keen to check whether any of the following would be helpful. Thanks in advance.

This also started happening in my organisation for a particular Dell model (Latitude 5550) where

• Windows version is 10.0.26100
• VPN client version 5.0.0 or newer The latest AWS VPN client works fine on other laptops on same version of Windows. The devices affected are running the client version 4.1.0 which works fine. I'll try to get some logs and check if there are errors for the TAP network adapter. When I looked into the issue I definitely noticed the creation of lots of network adapters when the client was trying to connect. Does anyone know if there is a fix being prepared for this issue?

Looks like the root cause could be that cvpn couldn't rename the TAP adapter and keep installing new adapter until the system runs out of drivers and netsh fails. Was there any update on the machine or was there any specific update that would keep the netsh try to get into loop by re-creating TAP adapters. Can you test the same by re-naming the adapter manually and try to connect ?

We had this issue as well and were able to solve it. We were using our VPN with SAML too which seemed to exacerbate the issue. The VPN we had is configured to use UDP protocol on port 443 only, The client needs outbound traffic UDP 443. Some routers tend to drop UDP outbound packets, since https should mostly be TCP, so I created a VPN that supports TCP on 443 outbound and the and everything worked.