Windows 10: Network issues after removing bridged connection through hyper-v

I successfully bridged my internet connection in hyper-v with a linux mint virtual machine. i then decided to remove the bridged connection. upon doing so i lost all connectivity on my host machine windows 10 pro 64bit. I restarted the host machine and still no network connection. i reset network settings and it seemed to work but every so often i lost internet connection. i decided to do a system recovery fresh factory default install and it seemed to do the trick. but every now and again not as bad as before i still lose internet connection.




:)

 

Hyper-V Network Adapter Bridge Mode?


I'm running successfully running Android BlueStacks in a Hyper-V machine and have network connectivity through the host adapter. However, one Android app I run does not fully function because it believes the device is not on the same subnet as the actual host machine. Someone on another forum indicated that the host adapter needed to be in bridge mode, thus ensuring that the virtual machine is on the exact subnet as the host and other device attached to the router. They suggest using something busybox for the VM and set the network adapter to bridge mode, but I really don't want to add that to my machine.

So the question is: does Hyper-V provide a bridge mode setting for the (virtual) network adapter?

 

windows 10 failed to remove network bridge completely

I am using Hyper-V on Windows 10.

Two days ago, I added a virtual switch at first using wireless network adapter with connection type of internal network, and then added a bridge between the virtual switch and actual wireless net adapter. It's certain that my virtual machine can't connect to
the outside because of the internal network type of the switch. After I was aware of the fault I wanted to change the connection type of the virtual switch to external network but failed. And then I had a urgent matter and closed the computer. After I reopened
the computer, I entered the UI {control panel}\{network and internet}\{network connection} and selected the network bridge and intended to remove it via its context menu. After accepted the remove instruction the computer lost response for a long time (over
15 minutes) and I had to shutdown the computer hardly.

After restarted the system I removed the virtual switch from Hyper-V manager and just wanted to add a new one with connection type of external network. But I received a message as follows:

Fail to bind Ethernet port {here is a GUID}: requested resource is in use.

Can't bind the virtual switch to WLAN adapter because the network bridge is in use. You are allowed to config at most one virtual switch to connect to WLAN adapter.

(The above messages are originally shown in Chinese. I am regretful that the above messages might lack of accuracy because of my poor translation skill)

And now I can't add virtual switch and my virtual machine consequently can't access outside network via WiFi.

I guess that the unsuccessful removing operation(the one caused system halted) of the network bridge had removed the bridge from the UI but in the background just somewhere, the network bridge exists still and occupies the port resource.

I had tried to disable Hyper-V and re-enable Hyper-V from {Enable Windows features on or off}, and it cut no ice with the problem.

 

Hyper-V networking

Windows 10 Pro, Build 10586.71. Hyper-V installed. All was working well, and then I got a chipset update from Dell. Installed the update and rebooted computer. After that networking was not working correctly, windows showed limited connectivity. I looked
a little to roll back the driver update, but Windows did not show a new Nic card driver and the chipsets I looked at also did not show a current date. The Dell Command update program does not provide a way to uninstall updates.

I tried to access hyper-v switch manager but it returns an error that "an error occurred while trying to retrieve a list of virtual switches". Also tried using the powershell cmdlet but got a general error.

I accessed the networking center and deleted the Hyper V adapter, then edited my LAN card's config disabling the two Hyper V protocols and enabling the rest. This let me get back on-line with my computer. I have tried uninstalling the Hyper V feature,
reboot, reinstall - but I am still unable to access the switch manager. I then removed the feature again, re-named the C:\ProgramData\Microsoft\Windows\Hyper-V directory, rebooted, added the feature again. This time (obviously) none of my VM's show up but
I'm still unable to access the switch manager.

There is no critical data in my Hyper V, I use it for testing, re-creating issues, learning, etc. Is there a way for Windows 10 (or something designed for server 2012 that will apply) that I can use to fully reset the Hyper v networking, or fully rest all
of hyper v so I can get it working again? I do use the workstation heavily, it's my work computer so it would be very difficult to impossible to reinstall the OS.

Thoughts and suggestions appreciated.