cisco anyconnect secure mobility client virtual miniport adapter for windows x64

The solution to dealing with these problems in the long run is to prevent the Hyper-V Virtual Ethernet Adapter and the Cisco An圜onnnect Secure Mobility Client Virtal Miniport Adapter from using the Cisco An圜onnect Network Access Manager Filter Driver.

Unfortunately I didn’t take any screenshots of this process. This breaks the VPN connetion only seconds after being established, causing the VPN to enter a disconnect/reconnect loop instead of working steadily. However, after the VPN session is established, you can see that the Network Access Manager module has assigned the VPN IP-address (given to you from your ASA IP Pool) to your REAL wired or wireless network adapter. After connecting to the ASA running Remote Access VPN, authentication works as it should when I log in with my username and password. The problem with the VPN module is a bit similar to what happens with the Network Access Manager module problem. To temporarily restore the real network connectivity I could either connect the computer to a real wired network and select the wired connection profile or a wireless connection profile in the An圜onnect list of available networks. Up until Windows 10 version 1809, this Hyper-V Virtual Ethernet Adapter hasn’t been interfering with An圜onnect at all (in my experience) but now something has changed and to An圜onnect, this virtual ethernet adapter looks just like any real network adapter you have in your computer (like your wired Ethernet adapter or your wireless network adapter). I am not going to go into detail on what these features do but using these features requires a Hyper-V Virtual Ethernet adapter to be installed, which will be installed by the operating system automatically. The cause of the issue is that if you are running Windows 10 Enterprise (which most businesses are), you most likely have useful security features such as Credential Guard and Device Guard running. I ran into the issues on both An圜onnect 4.5 and 4.6 versions.

One issue in particular that I myself has run into is that newer versions of Windows 10 (starting with version 1809) tend to mess with two modules in the Cisco An圜onnect suite: the Network Access Manager (NAM) and the VPN module.

Changes in Windows 10 leads to a lot of time spent making sure all your other software runs without compatibility issues when the new Windows versions are getting tested before being pushed out to end users. While this problem occured months ago, I didn’t think of writing this blog post until now but better late than never, I guess.Īs Windows 10 moves forward with more and more updates every year the rest of us have to do what we can to keep up.

Cisco anyconnect secure mobility client virtual miniport adapter for windows x64