Please do not take this wrong but I really recommend you to do a clean install with the 10130 ISO burned to a DVD or Flash drive. If your virtual machines cannot be replaced with new ones, I mean if they contain some valuable data, export them first, then reinstall Windows, then import the virtual machines to Hyper-V.
I think you are right - I don't see any other options.
Thanks again for all your effort.
John
I created a switch - and got no errors until I tried to connect my virtual machine then I got
~
I now have the realteck, a realteck wirless (connected to my lan network) and a new Vethernet
seen here
~
~
I also tried connecting to the wireless (like I had before the upgrade to 10130) after I removed the first switch. That got me an error "the requested resources is in use" and "the virtual switch cannot be bound to the WiFi adapter because the network bridge is already in use. I don't see a bridge in my Network Connections or in the Device Manager
I made a .pdf that has all the steps I took I can send you.
looks like the images did get uploaded - here they are (I hope)
Yes - after the re-install I had the virtual switch active again. I fear I may have removed a network adpter I should not have. I used to have a Microsoft Network Adapter Multiplexor Driver. It is no longer listed in Device Manager - just the realtek, the realtek wireless and a Microsoft Wi-Fi direct virtual adapter [and a checkpoint virtual network adapter for a different process that connects me to my home office servers]
You are doing something fundamentally wrong, I have a hunch what it could be, let's see now. I make some screenshots and post here the correct way to do this, might take half an hour.
Ok - i'll look for the screen shots
This is how it's done, screenshots from a fresh, clean install of Build 10130 just now. Virtual switch created but not a single virtual machine yet on this PC.
First, after the installation and even before adding the Hyper-V features, check that your network adapters are correctly installed and working. In my case this is where I start, Ethernet (#1 in screenshot) and WiFi (#2) adapters working and connected:I create a new external switch to allow my virtual machines to connect to the network and to Internet:
I name the switch as I wish, select the correct network adapter (in this example case now the wired Ethernet adapter), and click Apply:
The virtual switch has been created (#1):
Of course the host must also use this virtual switch to connect to network, that's why the Network and Sharing Center on host is from now on showing that I am connected with the virtual switch. This screenshot from the host:
I have absolutely no reason whatsoever to go to Ethernet adapter's properties in order to install or uninstall any of the components, I have absolutely no reason whatsoever to go to Ethernet adapter's properties to enable or disable a feature. Windows in general and in this case the Hyper-V Virtual Switch Manager in particular know what they are doing; if your network adapter is working prior to creating a virtual switch using it, you need to keep out from the adapter properties accepting the defaults and let your host stay connected using the virtual switch!
Only difference when creating a virtual switch with your wireless adapter is the bridge; the Hyper-V virtual machines by default only connect to network using a wired connection, they do not recognize a wireless connection. This is why when you create a virtual switch with a wireless adapter it needs to be added to a bridge, which in its turn "lies"to the virtual machine that it is a wired connection (screenshot from a tutorial at our sister site the Eight Forums):
Windows and Hyper-V Virtual Switch Manager will do the job for you and create the bridge automatically with correct settings.
Again:
- Do not manually edit the properties of the wireless adapter!
- Do not manually edit the properties of the virtual switch!
- Do not remove the bridge!
I suspect that in your case you have either manually edited the network adapter properties after creating the virtual switches, or you have been somewhat confused and not understood that after creating an external switch also your host will connect and needs to connect to network using the external virtual switch in order for your virtual machines to be able to connect. This confusion might have lead you to delete something you have thought to be unnecessary.
If the earlier instructions do not work, it's one more reinstall for you. Then, before starting to set up the virtual switches, have a cup of coffee and read this Virtual Switch tutorial carefully and slowly through: Hyper-V Virtual Switch Manager
Kari
First a thank you to all in this thread, its a great read and instruction. I'm hoping this thread is not so old no-one will read it because I have a very similar but not wholly different problem.
I'm using a 2016 Win 10 Pro upgrade build (10586). I'm not afraid of the registry hive as I've done lots of tuning over the years so the corrective actions remove process was straight forward but I'm not sure that's my problem.
I've setup Hyper-V initially setting up the VM-network before installing the VM guest OS. I realized the Win10 host was using a physically named RealTek named driver rather than the family driver so I attempted to switch my VM network driver to match the host (which was still working) and it didn't (your reference to the physical vs the virtual NIC i believe). I switched back to the virtual RealTek family adapter choice. I noticed host networking bumped and was now using the virtual NIC and browsing returned to normal for the host. I'm still having trouble with the VM networking though.
I'm in a lucky place because my VM is principally a DB server and the db's are not on the VM space itself (they're on a passthrough-the-host shared connected SAN {yes I realize what its doing is not "best"}). If I need to I can destroy and rebuild the VM but I'm hoping not to have to do this. I can provide screen shots of what's working and not but by powershell and configuration it looks like it should be working.
Help?
Quote
