Windows 10: Hyper-V does not allow my VM to the internet

There's no bug in Virtual Switches, at least none I know of. There's one in PowerShell, the Set-Executionpolicy Unrestricted command or cmdlet as they are called in PowerShell is not working which makes running some scripts impossible.

You simply have a situation where the switches are no longer connected to physical NICs on host and the host is not using a switch to connect to network but is instead connected directly over the physical NIC making it impossible for virtual machines to connect to the Internet.

This is usually caused by user him/herself.

Creating the bridge at the moment manually is most probably not going to do any good in this case. The fact that the OP tells about the issues with Virtual Switch Manager supports that assumption.



Warning Please notice that the below scenario worked on a test setup where the fault was purposely caused. I can not guarantee this works for you, and am wholeheartedly recommending you to export your virtual machines, backup your personal files and reinstall Windows 10.

OK, here's something that might or might not work. Please remember that the worst case scenario when trying this is a reinstall. To prepare for that, I would start by exporting my Hyper-V virtual machines to an external location (right click the vm in Hyper-V Manager, select Export).

Notice that some other geeks might give you some other advice, some might tell you you don't have to reboot as often as I tell you or do all the steps, but I am just saying that I created an issue like yours on purpose on a test rig and got Hyper-V Virtual Switches working again doing exactly as told below.

• Close Hyper-V Manager and all virtual machines
• Remove your WiFi adapter from bridge (right click it, select Remove from bridge)
• Open Registry Editor, browse to following key:
  Code: HKLM\SYSTEM\ControlSet001\Control\Network\{4D36E972-E325-11CE-BFC1-08002BE10318}[/quote]
• Now check the entries starting with {3xxx until you find your present external virtual switch. The Data in your case shoul be vSwitch (Fir):
  
  
  
• When found delete the key (right click the key itself on left pane, the key name starting with {3xxx and select Delete)
• Do the same for your internal switch vSwitch (Fir Internal). Find the key and delete it
• Reboot
• Back to registry editor, browse to following key and delete it:
  Code: HKLM\SYSTEM\CurrentControlSet\Services\VMSMP\Parameters\SwitchList[/quote]
• Reboot
• Disable Hyper-V from Programs and Features >Turn Windows Features On or Off
• Reboot
• Open Device Manager > Network Adapters, right click and select Uninstall for each and every Hyper-V network adapter
• Reboot
• Enable Hyper-V from Programs and Features >Turn Windows Features On or Off
• Reboot, Hyper-V will automatically find your virtual machines

Now try the Virtual Switch Manager, you should be able to re-create the virtual switches.

 

Creating the bridge at the moment manually is most probably not going to do any good in this case. The fact that the OP tells about the issues with Virtual Switch Manager supports that assumption.
.....

• Close Hyper-V Manager and all virtual machines
• Remove your WiFi adapter from bridge (right click it, select Remove from bridge)
• .....

Now try the Virtual Switch Manager, you should be able to re-create the virtual switches. I don't know where you got the idea about manually creating the bridge, all I said was remove the bridge. That is what your first step does after ensuring the VM is shut down.

Johnfranzen's reply to my suggestion was:

I don't know if remove bridge is an available option on the action bar. Anyway, we were headed in the same direction, you took the time to map out the registry entries. Since you had already begun testing a scenario, it would have been rude for me to offer anything more than the one suggestion. I know how threads can get sidetracked.

Good luck Johnfranzen, you're in good hands with Kari.

 

Slartybart, I got the manual bridge editing logically from your suggestion to remove it. Removing the bridge created by Hyper Virtual Switch Manager does not make anything good, it does not allow the vm to connect to network. Only logical reason to do it would be to re-create it, and in the OP's case that had to be made manually because he had already told that the Virtual Switch Manager which is normally used to create the switches and bridges they need does not work.

Logics. That's where I got it. Of course it has to be removed in order to repair the switches, but as a standalone procedure it does nothing, so it needs to be re-created and edited manually if the Virtual Switch Manager does not work.

 

Then our definition of logic must be different. The suggestion to remove the bridge was to see if the Virtual Switch Manager (VSM) would work afterwards. My experience is that if part of the Virtual Switch is hosed, then the VSM fails. Correcting the partial bridge definition often corrects the VSM failure issue.

I see where you might have been confused ... I should have said: This might be why Virtual Switch Manager is failing.

Back to the thread topic ...

 

I got everything removed per directions. (note I had to remove the Wi-Fi at the device manager level). When I tried to reset the hyper-v it would not take - until I removed the wireless adapter. Then Hyper V came back. When I got it started it found my VMs just fine. But when I clicked on Virtual switch:
~
it killed the service and did not allow me to add an external virtual switch.

Now the Wi-Fi adapter is back:
~

if it is of interest when I disable or re-enable Hyper-V the reboot is quite a bit of work. I'm wondering if I should run the 10130 from an iso (this upgrade happened by itself).

I appreciate all the time and effort you've taken here.

 

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)

 

Is this after re-installing Windows?

 

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" *Wink 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

 

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?