Page 3 of 3 FirstFirst 123
  1.    23 Jun 2015 #21
    Join Date : Oct 2013
    A Finnish expat in Germany
    Posts : 13,123
    Windows 10 Pro

    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.
      My ComputerSystem Spec
  2.    23 Jun 2015 #22
    Join Date : Jun 2015
    Posts : 15
    win 10 build 10130
    Thread Starter

    I think you are right - I don't see any other options.

    Thanks again for all your effort.

    John
      My ComputerSystem Spec
  3.    24 Jun 2015 #23
    Join Date : Jun 2015
    Posts : 15
    win 10 build 10130
    Thread Starter

    i have the vitrual switch back but .....


    Quote Originally Posted by Johnfranzen View Post
    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.
      My ComputerSystem Spec
  4.    24 Jun 2015 #24
    Join Date : Jun 2015
    Posts : 15
    win 10 build 10130
    Thread Starter

    looks like the images did get uploaded - here they are (I hope)Click image for larger version. 

Name:	vethernet switch 2.jpg 
Views:	195 
Size:	76.4 KB 
ID:	22367Click image for larger version. 

Name:	vethernet switch 1.jpg 
Views:	193 
Size:	39.1 KB 
ID:	22366Click image for larger version. 

Name:	missing bridge.jpg 
Views:	193 
Size:	54.1 KB 
ID:	22365Click image for larger version. 

Name:	inssufficent recources.jpg 
Views:	11 
Size:	112.6 KB 
ID:	22364
      My ComputerSystem Spec
  5.    24 Jun 2015 #25
    Join Date : Oct 2013
    A Finnish expat in Germany
    Posts : 13,123
    Windows 10 Pro

    Is this after re-installing Windows?
      My ComputerSystem Spec
  6.    24 Jun 2015 #26
    Join Date : Jun 2015
    Posts : 15
    win 10 build 10130
    Thread Starter

    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]
      My ComputerSystem Spec
  7.    24 Jun 2015 #27
    Join Date : Oct 2013
    A Finnish expat in Germany
    Posts : 13,123
    Windows 10 Pro

    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.
      My ComputerSystem Spec
  8.    24 Jun 2015 #28
    Join Date : Jun 2015
    Posts : 15
    win 10 build 10130
    Thread Starter

    Ok - i'll look for the screen shots
      My ComputerSystem Spec
  9.    24 Jun 2015 #29
    Join Date : Oct 2013
    A Finnish expat in Germany
    Posts : 13,123
    Windows 10 Pro

    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:

    Click image for larger version. 

Name:	2015-06-25_00h47_08.png 
Views:	201 
Size:	49.1 KB 
ID:	22371

    I create a new external switch to allow my virtual machines to connect to the network and to Internet:

    Click image for larger version. 

Name:	2015-06-25_00h50_55.png 
Views:	18 
Size:	41.2 KB 
ID:	22372

    I name the switch as I wish, select the correct network adapter (in this example case now the wired Ethernet adapter), and click Apply:

    Click image for larger version. 

Name:	2015-06-25_00h52_21.png 
Views:	15 
Size:	61.9 KB 
ID:	22373

    The virtual switch has been created (#1):

    Click image for larger version. 

Name:	2015-06-25_00h54_37.png 
Views:	203 
Size:	46.2 KB 
ID:	22374

    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:

    Click image for larger version. 

Name:	2015-06-25_01h10_22.png 
Views:	20 
Size:	35.3 KB 
ID:	22375

    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):

    Click image for larger version. 

Name:	15816d1359693033t-hyper-v-virtual-switch-manager-virtual_switch_17.png 
Views:	23 
Size:	228.9 KB 
ID:	22369

    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
      My ComputerSystem Spec
  10.    04 Jul 2016 #30
    Join Date : Jun 2016
    Posts : 3
    Win10Pro

    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?
      My ComputerSystem Spec

 
Page 3 of 3 FirstFirst 123


Similar Threads
Thread Forum
Solved Hyper Links
Having trouble with Outlook 2013 and Edge. Outlook will not open hyper links. This problem used to be solved by setting IE as default browser. How is this done with Edge? Solved the problem using the Microsoft Fix It program.
Browsers and Email
Solved Hyper-V
Hi, As anyone tried Hyper-V yet, as isn't it suppose to be an emulator so we can play old games like Silver etc...
Gaming
Solved Audio in hyper-v
So how do I get my headset which is usb to work in hyper-v?
Virtualization
Hyper-V & Win10 #2
Is there a way to create a Desktop shortcut to the Hyper-V Windows 10 Client so when I double click it I launch Windows 10 under Hyper-V? I've seen suggestions for Powershell and VB scripts, none of which I could get to work.
Installation and Upgrade
Solved Hyper-V & Win10
I decided to install Win10 in a Virtual Machine and settled on Hyper-V. I'm using the setup now to create this thread. There were a few hurdles to get over. 1) Hyper-V needed to be added to my Win8 install Program & Features-> Turn on Windows...
Installation and Upgrade
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 07:20.
Find Us
Twitter Facebook Google+ Ten Forums iOS App Ten Forums Android App



Windows 10 Forums