Windows 10: Hyper-V. Cannot delete "Default Switch" after Fall Creators Update.

Hello,

after update to Fall Creators Update i cannot delete vEthernet (Default Switch) in Hype-V. When deleted from connections in control pannel it is created again after reboot. If disabled it stays after reboot but new connection with #2 is created. When clicking delete in Hyper-V Manager -> Virtual Switch Manager it does not do anything. Anybody has Hyper-V installed here and could confirm if the issue is the case also in his computer? If anyone found solution how to permanently delete that connection please share the knowledge.

My VMs are all offline and i dont need additional conenctions in my system. Any help appreciated. Thank you!

Regards.

:)

 

Since Windows 10 Fall Creators Update (1709) - Constant High CPU Usage from System, ICS, Firewall, CoreMessaging and Filter Motor

This also worked for me. I noticed that the Internet Connection Sharing service was stuck with the status "Starting...". I switched it to Manual and rebooted and the CPU usage is back to normal. Luckily I don't need ICS. Some people are saying the issue
relates to Hyper-V but in my case Hyper-V cannot have been part of the problem since it was already disabled.

 

MIracast to television via Roku device. Image perfect, however the only sound produced is static.

I had a similar issue after 1709 which was related to having Hyper-V installed and the default switch. After 1709 Hyper-V installs a default switch, if the default switch is associated to your wireless nic i found that miracast stops working all together,
regardless of device (roku, samsung tv, sony tv) Unfortunately the only way i have found to get this going is to uninstall Hyper-V. With sound if you load say a youtube video and start playing it, you can enable miracast after the video starts playing the
sound works flawlessly, no volune at 5 with hiss in the background. They are the only workarounds that seem to work.

 

Previously you had to mess around using virtual switch manager to create a connection to network. Now you just select default switch if you like.

This option is essential for quick creating a new hyper-v session.

It is only used in existing sessions if you explicitly add it to a particular VM session.

Deleting it will not provide any additional security, or prevent other users creating a virtual switch.

Deleting things without understanding their functionality is surefire way to break things!

 

When default switch is deleted the VMs start alright so for me there is no need to keep that switch in the system as i want them all offiline. There is also remove button for the switch in Hyper-V Manager but it simply does not work. I don't think is crucial to keep default switch when you don't need any network access for your VMs.

If someone will find solution how to permanently delete default Hyper-V switch please share the knowledge. Thank you.

 

Default switch cannot be deleted. If its existence disturbs you, you might want to remove Hyper-V from your system and use another virtualisation program instead.

Quote from Hyper-V virtual machine gallery and networking improvements | Virtualization Blog:

 

Out of interest, I changed my network switch to "default switch" in one of my VMs and connected using vmconnect from hyper-v, and it worked fine. Only odd thing was if you hovered mouse pointer over the network symbol in taskbar, the popup was blank.

Then I closed down vmconnect session leaving vm running, and tried to connect using an RDP session. I reverted VM to the switch I had originally setup, and rdp connected as usual.

This may be a consequence of it not being setup with default switch originally - I will have to test that.

 

Default switch is using NAT, making networking and remoting if not impossible but at least quite difficult. If you want to allow network access to other physical or virtual computers on your network, you should use a normal external switch created by yourself. Using default switch (NAT) is only recommended if the VM only needs Internet access but don't have to be accessible for computers on your local network or to access them.

 

Thanks - was just curious really.

 

The only way I could make my VMs accessible to other devices on my local network was to create a new additional external switch bound to a second network card. I unticked the option "Allow management operating system to share this network adapter" so my desktop wouldn't try to use it itself. I was then able to connect to my VMs via http/https/ssh (or whatever) from any of the other PCs on my physical LAN.

Hope this helps.

 

This is not necessary, and is just over complicated.

You just set up C drive in VM as a private shared drive, with full permissions for "everyone", setting up password as required from network and sharing centre (I turn off password personally). You use an external switch, not "default switch". I use this to share drives with Host when using Home as a VM which does not support RDP as a server so cannot be used in enhanced mode.

This works fine for windows to windows share, but more effort is needed for android to windows shares.

 

Once the Hyper-V role is installed on the system, it takes your network card and assigns it to the virtual switch, then creates a virtual network adapter for the end-user.

It's quite an abysmal default setup, especially if you have only one network adapter, but from what I've read on the developer forums, they are looking to make it optional.

 

Absolutely not true, completely wrong and invalid information.

Setting up Hyper-V does not touch / change any network settings. Creating an external network switch is totally optional. No virtual network adapters will be created when Hyper-V is enabled.

Please check your facts before posting.

 

That's good to know. However, in my setup I'm using Hyper-V to run an F5 LTM/ASM which need to be able to create VIPs that are accessible on my LAN to other devices. My approach above is the only way I could do it. Prior to the creators update I didn't need to do this.

 

A few posts earlier you posted, that with Hyper-V there comes a virtual default switch/ network adapter which cannot be deleted.
How can you say now, that it's not.

Obviously it is created and it cannot be deleted, otherwise I would not be here.

I hope the post from "DrEmpiricism" reflects the future with:
"...but from what I've read on the developer forums, they are looking to make it optional."

I can setup an internal NAT if I need one, but I don't need this default switch (and I want it removed).
More network adapters mean e.g. more spam using ipconfig or another connection in the network sharing center with unidentified network connection...