Creating a new virtual switch after one has gone haywire

Today I went to tinker around with Network Profiles on Windows 10. I made some changes going from Public to Private and a few changes here and there.

After resetting my PC, I realised that some of the VM's (Ubuntu and Windows Server 2016) all using same virtual network adapter that were running could not longer resolve DNS names like

Upon diagnosing the situation, I got an error message saying Windows could not automatically detect this network's proxy settings

Several attempts were made to remedy the situation such as reseting the network adapters, configuring sharing, reseting routers but all to no avail.

In the end, I just created a net virtual switch on hyper-v and assigned it to my VM's running on Hyper-V.

comments powered by Disqus