Win10 hyper-v cannot connect to internet. Vm can only ping router!

Hi Gorgonio, welcome to the Ten Forums.

Hyper-V is easy and straight forward to set up when done correctly. You enable the Hyper-V feature, create an external virtual switch, install a guest OS selecting the external switch as connection and you are done.

There's no need to set static IP addresses. Of course you can use a static IP if that's what you prefer but Hyper-V virtual machines work just fine with DHCP and dynamic IP addresses.

There is never need to manually create a network bridge. If you create an external switch using the host's wireless NIC, Hyper-V automatically creates a network bridge. With wired host NIC (Ethernet), the bridge is never needed nor should it be made.

Seems that your setup is totally screwed, I recommend to either restore a System Image or do a System Restore to the point before before you set up Hyper-V and start from scratch. You can try to remove all your network switches using the Hyper-V Virtual Switch Manager and manually removing all network bridges, then reboot and try creating the switches again, but I doubt this will work.

Tutorial: Hyper-V virtualization - Setup and Use in Windows 10 - Windows 10 Forums

Kari

BartZorn said:

I have never created a bridge manually. When I try to bridge my wireless and my ethernet together, I get the following error: see attachment. Not very helpful. I know it is not a supported configuration, but it is just as a demonstration.

First: The Bridge needed for the wireless external switch is not supposed to bridge the Ethernet and wireless adapters! You have the concept a bit wrong.

This extract from a tutorial Hyper-V Virtual Switch Manager on our sister site the Eight Forums:

You might have also noticed that although the virtual switch vEthernet is connected to (is using) host’s WLAN NIC it is however showing an Ethernet LAN symbol (connector of a LAN cable) and presented under LAN connections. This has a simple explanation: all Hyper-V network connections are Ethernet (LAN) connections; Hyper-V does not support WiFi so even when a virtual switch is connected to a wireless NIC, Hyper-V presents it as Ethernet connection to the virtual machine i.e. the virtual NIC on vm “thinks” it is connected with an Ethernet cable.

This also means that when we are using an external virtual switch connected to a WLAN NIC, we need an extra network bridge on the host. The virtual NIC connects to a virtual switch, virtual switch in its turn connects to a host network bridge which creates (as its name says) a bridge between our virtual Ethernet connection and host WLAN NIC’s connection to the router:

(Note: NIC = Network Interface Controller, the network adapter. WLAN NIC = wireless adapter.)

Hyper-V does not have any emulated virtual hardware for a wireless connection. Therefore it handles even an external wireless switch as a wired Ethernet connection. The host needs a bridge between the wireless switch and the real physical WLAN NIC; it kind of "translates" the wired network traffic coming from vm to the wireless host NIC. This bridge will be automatically created when a wireless external switch is created, there's no need to do it manually.

To start with, please tell if the wireless external switch is still present in your system although not shown in Virtual Switch manager. You can check it in PowerShell with following command (or rather cmdlet as they are called in PowerShell):

Code:

Get-VMSwitch

It shows all present virtual switches:

Post the same screenshot as shown above as an example, we'll start from that.

Kari

BartZorn said:

The Get-VMSwitch gives me the following:

OK so the wireless switch is totally gone.

A workaround if you are unable to create an external switch with the wireless adapter is to create an internal switch, set the vm to use it, and share the host wireless connection with that internal switch.

See this post for more information about the workaround: Hyper-V virtualization - Setup and Use in Windows 10 - Page 28 - Windows 10 Forums