The 'problem' with the AnyConnect virtual adapter is, that it is disabled until you established a vpn tunnel. I guess that WinPcap is unable to see the adapter as it was disabled when the WinPcap NPF service was started, at least some tests let me assume this. So here is what you can try: establish a VPN tunnel

Install Cisco AnyConnect Secure Mobility Client on a Download the Cisco AnyConnect VPN Client here. Most users will select the AnyConnect Pre … Install & Fix Cisco VPN Client on Windows 10 (32 & 64 Bit When attempting to connect to a VPN gateway (router or firewall) using the Cisco VPN Client on Windows 10, it will fail to connect because of the following reason: Reason 442: Failed to Enable Virtual Adapter.

If you search for "Cisco VPN Windows 10" in Google you can find unofficial fixes but I would recommend taking caution in using them (they may pose security risks). Personally, I would suggest trying to use ShrewSoft VPN client in place of Cisco VPN client until Cisco comes up with an official fix. Hope this helps!

Simple: just set up your Hyper-V virtual machines to use the host’s VPN client and connection. To start with, create an Internal Switch in the Hyper-V Virtual Switch Manager: See Part Three of my Hyper-V tutorial on Ten Forums for detailed instructions on creating virtual switches. Now, on the host, connect to a VPN. Install Cisco VPN In Windows 10 + Fix Error 442 In Windows Jan 25, 2017 INSTALL and FIX CISCO VPN CLIENT ON WINDOWS 10 / FIX

EventViewer will report inability to change the interface name for virtual adapter. Conditions: If installed after 3rd party personal firewall/AV product, AnyConnect will fail to connect. Workaround: Disable all the features of personal firewall/AV, make a small change on AnyConnect virtual adapter and connect. Further problem description

Mar 04, 2012 Cisco AnyConnect VPN Issues - McAfee Support Community EventViewer will report inability to change the interface name for virtual adapter. Conditions: If installed after 3rd party personal firewall/AV product, AnyConnect will fail to connect. Workaround: Disable all the features of personal firewall/AV, make a small change on AnyConnect virtual adapter and connect. Further problem description Can a Hyper-V VM use the host's VPN?