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

cereberus · 27 Sep 2018

lx07 said:

It seems you are correct and you now have me doubting my sanity. I was certain I read that external switch was changed to share bandwidth between host and guest a few releases ago so neither host or guest got more than their fair share.

Having spent several hours looking I can't find this document any more. I don't like to think I dreamt it all up but as I can't back it up I must assume I was wrong.

I wasn't trying to spread false information - I did truly think it was the case.

One of the advantages I find growing old is that I clearly remember things 20 years ago but not more recently.

Now what was I saying - Oh yes - "One of the advantages I find growing old is that I clearly remember things 20 years ago but not more recently".

Kari · 27 Sep 2018

lx07 said:

I wasn't trying to spread false information - I did truly think it was the case.

No problems. it's just that same bandwidth sharing happens with host and VM using Default Switch, removing option to create your own external switches would not resolve / better anything. In addition, it would completely kill option to use remote desktop to connect to VM.

At the moment, I can create an external switch and make VM to use it, both host and VM having Internet connection and host or other machines on same network being able to remote to the VM. While external switch exists, network transfers from / to both host and VM are not working. If I want to copy anything over network, I need to disconnect remote desktop session, switch VM to use Default switch and delete external switch, then after the transfer, recreate external switch, set VM to use it and reconnect remote desktop connection.

Not logical, a clear bug. This bug started in build 17711.

Kari

tzat · 12 Jul 2020

the only solution is this:

I found a definitive solution. My solution works, even with Hyper-V enabled. Many of us don't want to disable Hyper-V security, and nothing else here worked for me on Windows 10 2004, everything is replaced on reboot, even netbios settings which increase attack surface, and its a pain to configure potentially hundreds of adapters every single time. Even automating with Nvspbind all settings revert on reboot. One way to disable these adapters literally ONCE AND FOR ALL is to disable DNScache aka Dns Client service and use a third-party DNS service such as Acrylic , or SimpleDNSCrypt. Be sure to comb through Acrylics configuration with a fine toothed comb because initially your default DNS provider will automatically be set to google or cloudflare. Then point acrylic to your router IP, or preferred DNS server, and set all your adapters DNS settings to 127.0.0.1.

You must disable DNSCache with regedit, here:

Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Dnscache

Set start to 4, and reboot.

The only minor caveat is you may see a single adapter constantly and briefly appearing and disappearing under Control Panel\Network and Internet\Network Connections and your device manager window will constantly refresh each time it attempts to install adapters. This problem appears to have went away for me after I enabled DNSCache (which was already disabled before I initially started using Hyper-V), then disabled it again. Another caveat is that initially loading the windows store you will get an error, unless you have previously opened the store with DNScache enabled. After that the store will work indefinitely unless you reset it. Not a big price to pay given how annoying this is, this actually works.

ignore the picture below, cant seem to remove it.