New
#21
I've had issues with the default switch since Windows 8.0. The problem comes and goes.
I don't know, but the Default Switch in Windows 10 is a bit different and automatically installed when Hyper-V role is added. I've earlier let Visual Studio create my VM network and there has always been glitches.
There's something wrong with the creation-deletion-recreation process of Switches that breaks everything. This issue does not occur always, just sometimes.
Edit: Actually, now when I really start to think about it, the same issue occur with some other devices. Somehow Windows does not clean up devices properly during removal and I think this is the main issue.
Example: I have a printer. I upgrade Windows, and next time I boot I have 2 printers. I upgrade again and then I have 3..etc...
While the use of the Default Switch is not essential and I can create a virtual switch, what is a problem is that the Hyper-V Manager Virtual Switch Manger tries to create the Default Switch every time the Virtual Switch Manger is launched or the Settings for a VM as accessed resulting in delays of 5-10 seconds before action can be taken. Really annoying.
And frankly I would like to have the use of the Default Switch if possible. so I would to resolve this if possible, since it has worked fine in 1803 for several months until the 1809 upgrade occurred.
Also clean installation is quite complicated due to company deployment configurations, etc.
Still seeking resolution so I appreciate the feedback and suggestions.
Kari, regarding you latest recommendations... no success.
1. Checked Device Manager-Network Adapters and no Hyper-V virtual switches existed.
2. Turned OFF Hyper-V feature and rebooted.
3. Checked Device Manager-Network Adapters and no Hyper-V virtual switches existed.
4. Turned ON Hyper-V feature and rebooted.
5. Checked Device Manager-Network Adapters and no Hyper-V virtual switches existed.
6. Launched Hyper-Manger and selected Virtual Switch Manager. No Default Switch exists. Observed Default Switch appearing in Network Connections and Device Manager-Network Adapters a few times but only for a few seconds each time.
Sadly no improvement.
Thanks for the attempts... perhaps you will hear something... or some else will chime in with an idea. So far everything you've suggested was a logical approach.
Like you I'm thinking there is lingering "junk", perhaps in the in the registry.
I found where the network adapters are listed in the registry on my system. There are no Hyper-V virtual adapters that should not be there. I created one and removed it and there were no left over bits from these or from any previous actions...
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e972-e325-11ce-bfc1-08002be10318}adapter"
Just wanted to say thanks to those that provided suggestions, etc. I've never been able to resolve the issue with the inability of Hyper-V manager being unable to create the Default Switch. Windows Repair procedure did not resolve the issue and I'm afraid a new install is not feasible due to company challenges so don't know if that would work.
I've moved to Virtual Box product and it's getting the job done, just not as easily.
Cheers!
I've been affected by this problem with Windows 10 Pro v1909. I want to add this post to backup what jareinertson was saying re: "I see the Default Switch appear for a few seconds, typically multiple times". I can reliably reproduce this with an elevated Powershell loop that repeatedly runs "Get-VMSwitchExtension -VMSwitchName ('Default Switch')" while viewing "Control Panel\All Control Panel Items\Network Connections". I'll see the "vEthernet (Default Switch)" flicking in and out of existence continuously.
This problem is very annoying and I've now spent about 6 hours trying to debug it. It seems that the only option is a reinstall of Windows unless you catch it early enough to rollback the update that caused it. I'm about to give up and go back to VirtualBox. I'd prefer not to as Hyper-V gives me better disk I/O.