Forum Discussion
Hyper-V Default switch IP address range change. Ver 1809 Build 17763.1
i agree default switch should be optional, not everyone want to use the quick VM creation of Hyper-V.
HotCakeX Here I had another chance on completely unrelated PC (different hardware, different location, different networking settings and environment, different users, not in domain, etc.) Same set of initial errors.
Trying to create external switch in GUI:
"Error applying Virtual Switch Properties changes
Adding ports to the switch 'External Switch' failed
The operation was passed a parameter that was not valid."
Trying via PowerShell command ("New-VMSwitch -Name "External VirtualSwitch" -NetAdapterName "Killer e2200 GbE NIC" -AllowManagementOS $True"):
"New-VMSwitch : Failed while adding virtual Ethernet switch connections.
External Ethernet adapter 'Killer e2200 Gigabit Ethernet Controller #2' is already bound to the Microsoft Virtual Switch protocol."
So I tried "easy" solution first, and in NIC Properties unchecked option:
"Hyper-V Extensible Virtual Switch"
(And rebooted PC)
Luckily, on this PC when I tried to create external switch in GUI after reboot everything went ok. Didn't have to use the "nuke" option this time.
But still, quite annoying. And (at least in my case) on PCs that I regularly use I have all of them throwing this or that error. I love MS, but sometimes I hate it as well...
Cheers!
- I think the best thing that should be done is to send feedbacks using any way, preferably Feedback hub, then share it with others who have the same problem to upvote it so that Microsoft will change that behavior on their end in future Windows 10 releases.
HotCakeX
Very informative thread for this newb. Like many, I'd consider the behavior of the default switch a bug and not an enhancement.
1) Installed automatically (not optional).
2) Can't be removed.3) Can't be modified.
4) No persistent state except unconfigured.
5) Defaults to "Public" on a Domain machine and reconfiguration of state doesn't stick.
VBox and VMWare user attempting to learn Hyper-V and decipher the lack of logic in the above configuration.
Because it's "Public" or doesn't allow the option of a network type selection the Default Switch kills PowerShell WinRM and MS Admin Center on my domain, even when all VMs are using a second manually configured external switch and there is nothing using it - it's still in the registry in the default default configuration after reboot and PowerShell DSC is useless with the Default Switch registering.
I've read the arguments that it's "for amateurs" etc and there to make networking easy. My experience is exactly the opposite, that it's inexplicably configured to keep professionals from accomplishing their work. It breaks workflows that would otherwise be successful and that is a substantive meaning of a 'bug' in the software.
I've temporarily gone back to VMWare, which works flawlessly managing my virtual lab because default switch just doesn't work in my situation.
If someone can, please help me find workarounds to the 5 points above I'd greatly appreciate both your time and the knowledge. Very frustrating to have a simple configuration be this difficult to get working.
FYI - problems listed above are on 1909.
Thanks- Sneeze what?
- Well I have the best AV, Kaspersky Internet security, with bunch of virtual switches including the default switch, everything is working perfectly.
you should contact your AV website and tell them this problem of yours.
my suggestion is to use an AV that is the best and doesn't have these problems.
https://www.youtube.com/channel/UCKGe7fZ_S788Jaspxg-_5Sg
https://www.youtube.com/watch?v=UDkllzL1gqo Using anything will not make Default Switch to disappear. It confuses my AV even when no virtual machines are running.
- Hi,
Try using External virtual adapter instead of the default switch if you can 🙂 I have another silly problem with this default switch. Since it changes its parameters all the time, my antivirus every time thinks it is a new network, and asks me what to do with it. It causes distractions, but the worst part is that it blocks all network on boot until I answer, causing network disks to not mount, which causes unrelated apps to not load properly and so on.
I am trying to figure it out with AV support, but I doubt they will resolve it soon, so I will have to use less optimal antivirus on my PC.
- Thanks for the useful info, btw i also got the Killer e2200 GbE NIC
anyway, yeah Hyper-V has it's own issues. I recently got bored and switched to VMware workstation pro 15.5 (latest ver) and I had so many problems configuring it.
I had to turn off Windows defender application guard, Windows Sandbox, Core isolation in Windows defender and literally lots of compromise in order to only install it.
after that I had problem with Windows 10 Enterprise x64 IoT version when i tried installing VMware tools on it, i was getting error that prevented me to install it.
so i eventually uninstalled it, turned on all of those security features again and continued using Hyper-V. i know it's not perfect but the alternative is a lot worse, at least for me.
I just hope Microsoft hear us and apply the changes we are asking to the way Hyper-V handles virtual network adapters.
