I updated to Win10 2004 (Build 19041.208 as of this writing) and I've noticed that on my system with Hyper-V installed, I now have an auto-created vEthernet interface for every physical Ethernet interface on my system, including interfaces with no connectivity. Each one is named "vEthernet (Physical interface name)". This is occurring despite that fact that only virtual switch I have on my host system is the Default Switch.
All of these vEthernet interfaces have auto-assigned 172.x.x.x IP addresses. These vEthernet interfaces cannot be deleted in Network Connections (option is grayed out) and if I use Device Manager to uninstall the actual Hyper-V Virtual Ethernet adapter device associated with these interfaces, they reappear on reboot.
Strangely, when I installed Win10 2004 in a guest VM with 3 virtual NICs and installed Hyper-V within that VM (after enabling nested virtualization), I was NOT able to reproduce this behavior. The guest VM's Hyper-V environment did not create 3 new vEthernet interfaces, even after multiple reboots.
Is anybody else seeing this? Does anybody have any idea why this is occurring or what the purpose of these vEthernet interfaces is? Previously I only ever had one vEthernet interface for the Default Switch, and then I would get one more for each Internal or External virtual switch I created. This is how another Hyper-V host system I have that's still running Win10 1809 is working right now. I have no idea why Hyper-V now feels the need to give me one per physical interface, each with a 172 IP address.