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.
Kari
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...
I don't know what you mean with default option, but a virtual switch named "Default Switch" is created just by installing the Hyper-V feature in Windows 1709.
Yes, but as long as you do not create any additional external switches, it affects host networking in no way. You are completely misunderstanding what has been said.
This is what I posted:
What I replied to member DrEmpiricism is an undisbutable fact. If you do not set up additional external switches, host NIC will not be "taken" over by Hyper-V, host networking being exactly as before without Hyper-V meddling in any way.
Kari
This is 100% true. Adding the Hyper-V role provisions the default switch to utilize your network card while enabling a virtual network for the system in its entirety. This is why true network parameters can be hard to attain remotely if the Hyper-V role is not taken into account.
Please learn Hyper-V.
I found this thread interesting and I share the OP's desire to at least edit configuration of the default switch, particularly because it is using the wireless adapter on my laptop which I rarely use. I understand it does give me the option to use wireless for some VM if I need to, but with the entire configuration grayed out I don't know now if I may need to edit these options.
On a related note I have no Virtual Switches in my Hyper-V Manager and still had two vSwitch network adapters listed in Windows adapter settings. Until today I could not delete them. I finally removed the NAT for Hyper-V using Powershell and finally removed the adapters through the device properties. Now I can start clean in Hyper-V.
I won't stop looking for some way to at least enable configuring options in the default switch, including being able to select the adapter.
Last edited by BillieB0B; 31 Mar 2018 at 02:32.
Nope, wrong. It affects the resolution of remote addresses when those remote addresses are actually local (i.e. 127.0.0.1 or 0.0.0.0). Check netstat—if you dare. I've already had issues with one application because of this.
You should really avoid speaking in absolutes and totalities—rarely are you correct when doing so.
If you could at least disable the switch, that'd be one thing—but you can't. You can't disable it and you can't delete it, even when there's no virtual machines running or being managed. Pure M$ BS.
Quote