Page 2 of 3 FirstFirst 123 LastLast
  1.    22 Jun 2015 #11
    Join Date : Oct 2013
    A Finnish expat in Germany
    Posts : 12,638
    Windows 10 Pro

    OK, your host is not using the virtual switch, instead connecting to the network directly using the host NIC, therefore your virtual machines have no chance to connect, they simply do not find connection.

    You told you have issues with the Virtual Switch Manager meaning we cannot use it to remove and recreate your switches, PowerShell has a bug in Build 10130 which makes it impossible to change the PS script execution policy so that's ruled out.

    I am testing something on a test machine, I do not want to tell you a theory before I have tested it first. Might take an hour or so.
      My ComputerSystem Spec
  2.    22 Jun 2015 #12
    Join Date : Jun 2015
    Posts : 15
    win 10 build 10130
    Thread Starter

    Wow, thanks for the extra effort. I've been hoping Microsoft would come out with a bug fix to make the Virtual Switch work again. But so far...................

    Out of curiosity I thought I'd try Virtual Box. It installed but will not run. So I removed the folders (did not get to program and features).
      My ComputerSystem Spec
  3.    22 Jun 2015 #13
    Join Date : Oct 2013
    Penns Forrest
    Posts : 3,506
    Win_8.1-Pro, Win_10.1607-Pro, Mint_17.3

    It looks to me as though you have Wi-Fi bridged to Realtek RTL8188CE Wireless LAN
    I don't see the other parts of the bridge. This might be why Virtual Switch is failing.

    It might just be a matter of removing the bridge from Wi-Fi, but see what Kari comes back with after he tests.
      My ComputerSystem Spec
  4.    22 Jun 2015 #14
    Join Date : Jun 2015
    Posts : 15
    win 10 build 10130
    Thread Starter

    how to


    thanks for the observation.

    if that is the case, how to I remove the bridge? none of the four connections can be removed, just disabled. Have you noticed that you cannot right click on one of these items - doing so closed the dialog. I have to left click and then click on the choices that appear on a bar above the list. Strange behavior that started with 10130.
      My ComputerSystem Spec
  5.    22 Jun 2015 #15
    Join Date : Oct 2013
    A Finnish expat in Germany
    Posts : 12,638
    Windows 10 Pro

    Quote Originally Posted by Johnfranzen View Post
    Wow, thanks for the extra effort. I've been hoping Microsoft would come out with a bug fix to make the Virtual Switch work again. But so far...................
    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.

    Quote Originally Posted by Slartybart View Post
    It looks to me as though you have Wi-Fi bridged to Realtek RTL8188CE Wireless LAN
    I don't see the other parts of the bridge. This might be why Virtual Switch is failing.

    It might just be a matter of removing the bridge from Wi-Fi, but see what Kari comes back with after he tests.
    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   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}
    • Now check the entries starting with {3xxx until you find your present external virtual switch. The Data in your case shoul be vSwitch (Fir):
      Click image for larger version. 

Name:	2015-06-23_00h42_06.png 
Views:	15 
Size:	66.7 KB 
ID:	22234
    • 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
    • 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.

    Kari
      My ComputerSystem Spec
  6.    22 Jun 2015 #16
    Join Date : Oct 2013
    Penns Forrest
    Posts : 3,506
    Win_8.1-Pro, Win_10.1607-Pro, Mint_17.3

    Quote Originally Posted by Kari View Post
    .....
    Quote Originally Posted by Slartybart View Post
    It looks to me as though you have Wi-Fi bridged to Realtek RTL8188CE Wireless LAN
    I don't see the other parts of the bridge. This might be why Virtual Switch is failing.

    It might just be a matter of removing the bridge from Wi-Fi, but see what Kari comes back with after he tests.
    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:
    Quote Originally Posted by Johnfranzen View Post
    .....
    Have you noticed that you cannot right click on one of these items - doing so closed the dialog. I have to left click and then click on the choices that appear on a bar above the list. Strange behavior that started with 10130.
    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.
      My ComputerSystem Spec
  7.    23 Jun 2015 #17
    Join Date : Oct 2013
    A Finnish expat in Germany
    Posts : 12,638
    Windows 10 Pro

    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.
      My ComputerSystem Spec
  8.    23 Jun 2015 #18
    Join Date : Oct 2013
    Penns Forrest
    Posts : 3,506
    Win_8.1-Pro, Win_10.1607-Pro, Mint_17.3

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

    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.
    Attached Thumbnails Attached Thumbnails virtual switch after re-install.jpg   wi fi added back.jpg  
      My ComputerSystem Spec
  10.    23 Jun 2015 #20
    Join Date : Jun 2015
    Posts : 15
    win 10 build 10130
    Thread Starter

    Just a thought:
    ~
    Attached Thumbnails Attached Thumbnails adapters after trying virtual switch.jpg  
      My ComputerSystem Spec

 
Page 2 of 3 FirstFirst 123 LastLast


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 10:29.
Find Us
Twitter Facebook Google+ Ten Forums iOS App Ten Forums Android App



Windows 10 Forums