Windows Sandbox creates a vEthernet for every physical and virtual NIC

Question

As the topic title says, Windows 2004 created a virtual interface for every physical NIC, after you enable the Windows Sandbox. It didn't show this behavior on the 1909 build.
It becomes a mess if you have more than 2 NICs. Also if you have Hyper-V virtual interfaces, it also clones those. Example: You have a virtual interface called "Internal NAT", it will make a new interface called "vEthernet ( Internal NAT ). Also happens with virtual VPN interfaces.
The following link demonstrates the problem happening with more people.

https://social.microsoft.com/Forums/en-US/d443bc7f-4cf4-4a8a-9ae3-4fd359c37849/windows-sandbox-on-win10-2004-now-creates-vethernet-interface-for-every-physical-nic?forum=win10itprovirt

Answer 1

Hi,
I tested in my lab and it seems this issue can only be reproduced on the latest Windows 10 version 2004. Unfortunately I found no software update solution to it yet. Not sure if it's by design. You may have to roll back to 1909 to avoid this issue.

You could check the updates information here
https://support.microsoft.com/en-us/help/4555932

Best Regards,
Ian

Answer 2

Seems they changed some things on the network part with Hyper-V. I figured I can not get promiscuous mode to work with Win10 2004 build - it used to work with an older version of Windows 10.

Answer 3

Has anyone found a way (perhaps a registry hack) that forces these interfaces to remain hidden from both the GUI and the ipconfig utility??? This is very annoying when trying to troubleshoot network issues.