Hyper-V does not allow my VM to the internet

Page 2 of 3 FirstFirst 123 LastLast

  1. Posts : 17,661
    Windows 10 Pro
       #11

    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 Computer


  2. Posts : 15
    win 10 build 10130
    Thread Starter
       #12

    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 Computer


  3. Posts : 3,502
    Win_8.1-Pro, Win_10.1607-Pro, Mint_17.3
       #13

    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 Computer


  4. Posts : 15
    win 10 build 10130
    Thread Starter
       #14

    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 Computer


  5. Posts : 17,661
    Windows 10 Pro
       #15

    Johnfranzen said:
    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.

    Slartybart said:
    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):
      Hyper-V does not allow my VM to the internet-2015-06-23_00h42_06.png
    • 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 Computer


  6. Posts : 3,502
    Win_8.1-Pro, Win_10.1607-Pro, Mint_17.3
       #16

    Kari said:
    .....
    Slartybart said:
    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:
    Johnfranzen said:
    .....
    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 Computer


  7. Posts : 17,661
    Windows 10 Pro
       #17

    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 Computer


  8. Posts : 3,502
    Win_8.1-Pro, Win_10.1607-Pro, Mint_17.3
       #18

    Kari said:
    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 Computer


  9. Posts : 15
    win 10 build 10130
    Thread Starter
       #19

    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 Hyper-V does not allow my VM to the internet-virtual-switch-after-re-install.jpg   Hyper-V does not allow my VM to the internet-wi-fi-added-back.jpg  
      My Computer


  10. Posts : 15
    win 10 build 10130
    Thread Starter
       #20

    Just a thought:
    ~
    Attached Thumbnails Attached Thumbnails Hyper-V does not allow my VM to the internet-adapters-after-trying-virtual-switch.jpg  
      My Computer


 

  Related Discussions
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 11:02.
Find Us




Windows 10 Forums