Hyper-V virtualization - Setup and Use in Windows 10  

Page 26 of 47 FirstFirst ... 16242526272836 ... LastLast

  1. Posts : 16,325
    W10Prox64
       #250

    Kari said:
    That's the most common mistake made when users post about lost connection on vm, the reason I put this in a Note box in the tutorial (end of Part Three):

    Note   Note
    When Hyper-V is enabled and one or more external virtual switches created, your host system uses these switches instead of host physical network adapters to connect to the network. This is as it should be, do not remove or disable the virtual switches!


    One more question or rather a request before going to possible solutions: We need to check if a virtual switch is still in the system although not mentioned in your Virttual Switch Manager. Please run the cmdlet Get-VMSwitch in PowerShell and either post the screenshot of the results or tell exactly what virtual switches it found, switch types and adapters they are connected to. Example from my machine in screenshot.
    Nothing, zilch, zip, nada, zed, big fat ZERO

    You have to make that much bigger, in RED and all kinds of stars around it for people like me who don't read......
      My Computer


  2. Posts : 17,661
    Windows 10 Pro
    Thread Starter
       #251

    OK. I think you'd be better off with a clean install but if you have patience you could try this:


    1. In Hyper-V Virtual Switch Manager, remove all switches. I mean all of them!
    2. In Network Connections, remove all adapters labeled as vEthernet (any name). Right click all remaining (physical) adapters, if they are bridged remove from the bridge
    3. Reboot, connect with Ethernet
    4. In Hyper-V Virtual Switch Manager, create a new external switch connecting it to the Ethernet adapter
    5. Open your Windows 7 vm settings (you still have it?), change the Network Adapter to the external switch you just created
    6. Start your Windows 7 vm, It should now have network connection

    If this works, we can try re-create your wireless external switch.

    This is how the adapter properties on your host should look when the virtual switches have been created correctly. First, the host physical NIC properties, everything else is unselected, only the Hyper-V Extensible Switch being selected:
    Hyper-V virtualization - Setup and Use in Windows 10-2016_01_19_23_36_311.png

    Then the vEthernet adapter, the virtual switch connected to the above NIC. Everything else selected except the Hyper-V Extensible Switch and MS Network Adapter Multiplexor Protocol :
    Hyper-V virtualization - Setup and Use in Windows 10-2016_01_19_23_38_531.png

    Seen in Device Manager, each virtual switch should be mentioned in Network adapters:
    Hyper-V virtualization - Setup and Use in Windows 10-2016_01_19_23_41_502.png

    In my case the three switches seen in Device Manager are the same three shown in PowerShell with Get-VMSwitch:
    Hyper-V virtualization - Setup and Use in Windows 10-2016_01_19_23_43_573.png


    We continue when you have either decided to reinstall or gone through the steps I listed above :)

    Kari
      My Computer


  3. Posts : 16,325
    W10Prox64
       #252

    step #1 gives me an error:

    Hyper-V virtualization - Setup and Use in Windows 10-del-switches-error.png


    Edit:
    Step #2 also gives no option to delete


    Hyper-V virtualization - Setup and Use in Windows 10-del-netwrk-conns.png

    I'm pretty sure I'll be able to accomplish step #3....


    Edit#2 - I deleted them in Device Manager...still will not delete from Hyper-V. Going for a reboot now.
      My Computer


  4. Posts : 17,661
    Windows 10 Pro
    Thread Starter
       #253

    OK. You might want to disable / remove the Hyper-V feature in Programs and Features > Turn Windows features on or off, reboot and enable / add it again, then try again.

    If that does not work my recommendation is to reinstall, this time not removing essential virtual devices in Device Manager
      My Computer


  5. Posts : 16,325
    W10Prox64
       #254

    Kari said:
    OK. You might want to disable / remove the Hyper-V feature in Programs and Features > Turn Windows features on or off, reboot and enable / add it again, then try again.

    If that does not work my recommendation is to reinstall, this time not removing essential virtual devices in Device Manager
    Reinstall? Reinstall what? My entire computer?
      My Computer


  6. Posts : 17,661
    Windows 10 Pro
    Thread Starter
       #255

    simrick said:
    Reinstall? Reinstall what? My entire computer?
    The fact that Virtual Switch Manager lists some switches which cannot be removed but PowerShell does not see them tells that your Hyper-V might be screwed enough for reinstall being the best if not only way to fix it.

    Restoring to a point before you manually removed the switch from Device manager is an option, too.

    Try first the disable / reboot / enable Hyper-V trick.
      My Computer


  7. Posts : 16,325
    W10Prox64
       #256

    Kari said:
    The fact that Virtual Switch Manager lists some switches but PowerShell does not see them tells that your Hyper-V might be screwed enough for reinstall being the best if not only way to fix it.

    Restoring to a point before you manually removed the switch from Device manager is an option, too.

    Try first the disable / reboot / enable Hyper-V trick.
    I got rid of them. They are gone....on to next steps (scrolling up...)
      My Computer


  8. Posts : 16,325
    W10Prox64
       #257

    >>Reboot, connect with Ethernet<<

    I am connecting with wifi, okay?

    Edit: I guess not...

    Hyper-V virtualization - Setup and Use in Windows 10-create-switch-error.png
      My Computer


  9. Posts : 17,661
    Windows 10 Pro
    Thread Starter
       #258

    OK, I thought that you still had a possibility to use Ethernet. Try with WiFi, then, create a virtual switch. If it gives the error message again do the disable feature / reboot / enable feature cycle and try again.
      My Computer


  10. Posts : 16,325
    W10Prox64
       #259

    Kari said:
    OK, I thought that you still had a possibility to use Ethernet. Try with WiFi, then, create a virtual switch. If it gives the error message again do the disable feature / reboot / enable feature cycle and try again.
    One question: Will I be able to just import my W7 VM after that?
      My Computer


 

Tutorial Categories

Hyper-V virtualization - Setup and Use in Windows 10 Tutorial Index Network & Sharing Instalation and Upgrade Browsers and Email General Tips Gaming Customization Apps and Features Virtualization BSOD System Security User Accounts Hardware and Drivers Updates and Activation Backup and Restore Performance and Maintenance Mixed Reality Phone


  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 17:46.
Find Us




Windows 10 Forums