Windows 10: Removing the vEthernet default switch from network connections list

I have a Windows 10 Pro Workstation. I normally use VMware and I like it, but on a whim I enabled Hyper-V and I did try it. I didn't like the functionality, and I tried to use VMware but could not until I disabled Hyper-V. This process was not straightforward, and initially failed, but after deleting the Hyper-V VM folder, uninstalling, re-installing VMware and disabling the vEthernet default switch, Vmware now works again. But how do I remove the vEthernet default switch listing?? Linux seems easier with its use of config files; why is Windows 10 so convoluted and needlessly complicated??

:)

 

How to remove all the vEthernet (Default Switch) once and for all?





As in the screenshot above, I don't know why the vEthernet (Default Switch) on my Windows 10 laptop keeps reproducing itself and auto connecting to it everytime I shut down and switch on the laptop.

Worst is if I switch Wi-Fi networks, it auto connects to the vEthernet (Default Switch) even when i have pre-disabled it before

Please help me find out the root cause of this problem? E.g. :

1. Why this strange occurrence keeps happening (I suspect it is because I installed Docker?)
   
2. Why I can't seem to delete the vEthernet (Default Switch) from Network Connections
   
3. Why does it keep auto connecting to vEthernet (Default Switch) and how to permanently disable it?
   

 

vEthernet (Default Switch) keeps replicating itself

Every once in a while, the "vEthernet (Default Switch)" on my laptop replicates itself ( e.g. "vEthernet (Default Switch) 2","vEthernet (Default Switch) 3", etc) and sets this new vSwitch as the default. Does anyone know how to stop this (apart from removing
Hyper-V - which I need).

I use Hyper-V on my laptop to host a couple of Linux Dev VMs - these utilise the "vEthernet (Default Switch)" adapter that is enabled with Hyper-V. Now this works great to allow my VMs to be NATted out to get updates, or connect with local servers that I
may need other resources from (e.g. file servers). In order that I can access these VMs through 3rd party tools such as MObaxterm or PHPstorm I set an additional IP ( e.g. 192.168.56.1) on the vEthernet: I need a static (local) IP on the VMs, as I am doing
website development, so I use a 192.168.56 address on them. This allows to me to test and debug my web apps effectively.

However, when the vSwitch replicates itself, it does not have the local IP I have set on the old vSwitch and I cannot add it to on the new vSwitch, until I have removed it from the previous one . Its either that or remove all the replicated vSwitches in
Device Manager and reboot, so it can create a new "vEthernet (Default Switch)". All in all it is major irritating - especiually as our work policy is that I need a seperate account to perform admin activties on my computer - so this usually involves typing
in these credentials 3 or 4 times to fix it.

I would really like to find a solution to this - I have contemplated moving to VirtualBox, but that seems daft considering I already have Hyper-V availble to me.

I suspect it may be something to do with the fact that I am using a laptop and have two work environments. I have my office setup with its own port replicator and screens, and my home office with a similar setup. The replication appears to happen when I
move from one environment to the other - but it does not happen all the time - maybe every week or two.

 

Duplicate vEthernet Switch Adapters?

I have two instances of a vEthernet Switch Adapter after installing a VM in Hyper V. I only have the default switch installed in Hyper V. How do I remove the greyed out adapter? Right clicking does not allow me to delete anything