“Generic failure” when creating virtual switch in Hyper-V Manager












5















I have installed Hyper-V from Windows Features but when i open Hyper-V Manager and try to create a Virtual Switch i get this error (NONAME is the computer name):



(screenshot)



I read over the internet for solution but I don't find anything that solve my problem. I have checked at the Ethernet properties option "Hyper-V Extensible Virtual Switch" but error still show up. Also I tried to uninstall and install again the Hyper-V Manager but also nothing happened.I have Windows 10 Pro and is clean installation. Any ideas what to do?










share|improve this question

























  • Please edit your question to indicate the specific version and edition of Windows you are using.

    – a CVn
    Oct 4 '15 at 13:03











  • From the title bar, I deduce this is about Windows 10. Please fix it if this is wrong. Also, is it a clean installation or an upgraded installation? Was Hyper-V installed before upgrading?

    – Daniel B
    Oct 4 '15 at 13:05











  • I have Windows 10 Pro and is clean installation

    – Tack
    Oct 4 '15 at 13:11
















5















I have installed Hyper-V from Windows Features but when i open Hyper-V Manager and try to create a Virtual Switch i get this error (NONAME is the computer name):



(screenshot)



I read over the internet for solution but I don't find anything that solve my problem. I have checked at the Ethernet properties option "Hyper-V Extensible Virtual Switch" but error still show up. Also I tried to uninstall and install again the Hyper-V Manager but also nothing happened.I have Windows 10 Pro and is clean installation. Any ideas what to do?










share|improve this question

























  • Please edit your question to indicate the specific version and edition of Windows you are using.

    – a CVn
    Oct 4 '15 at 13:03











  • From the title bar, I deduce this is about Windows 10. Please fix it if this is wrong. Also, is it a clean installation or an upgraded installation? Was Hyper-V installed before upgrading?

    – Daniel B
    Oct 4 '15 at 13:05











  • I have Windows 10 Pro and is clean installation

    – Tack
    Oct 4 '15 at 13:11














5












5








5


2






I have installed Hyper-V from Windows Features but when i open Hyper-V Manager and try to create a Virtual Switch i get this error (NONAME is the computer name):



(screenshot)



I read over the internet for solution but I don't find anything that solve my problem. I have checked at the Ethernet properties option "Hyper-V Extensible Virtual Switch" but error still show up. Also I tried to uninstall and install again the Hyper-V Manager but also nothing happened.I have Windows 10 Pro and is clean installation. Any ideas what to do?










share|improve this question
















I have installed Hyper-V from Windows Features but when i open Hyper-V Manager and try to create a Virtual Switch i get this error (NONAME is the computer name):



(screenshot)



I read over the internet for solution but I don't find anything that solve my problem. I have checked at the Ethernet properties option "Hyper-V Extensible Virtual Switch" but error still show up. Also I tried to uninstall and install again the Hyper-V Manager but also nothing happened.I have Windows 10 Pro and is clean installation. Any ideas what to do?







windows-10 hyper-v






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Oct 4 '15 at 13:13







Tack

















asked Oct 4 '15 at 13:00









TackTack

2814




2814













  • Please edit your question to indicate the specific version and edition of Windows you are using.

    – a CVn
    Oct 4 '15 at 13:03











  • From the title bar, I deduce this is about Windows 10. Please fix it if this is wrong. Also, is it a clean installation or an upgraded installation? Was Hyper-V installed before upgrading?

    – Daniel B
    Oct 4 '15 at 13:05











  • I have Windows 10 Pro and is clean installation

    – Tack
    Oct 4 '15 at 13:11



















  • Please edit your question to indicate the specific version and edition of Windows you are using.

    – a CVn
    Oct 4 '15 at 13:03











  • From the title bar, I deduce this is about Windows 10. Please fix it if this is wrong. Also, is it a clean installation or an upgraded installation? Was Hyper-V installed before upgrading?

    – Daniel B
    Oct 4 '15 at 13:05











  • I have Windows 10 Pro and is clean installation

    – Tack
    Oct 4 '15 at 13:11

















Please edit your question to indicate the specific version and edition of Windows you are using.

– a CVn
Oct 4 '15 at 13:03





Please edit your question to indicate the specific version and edition of Windows you are using.

– a CVn
Oct 4 '15 at 13:03













From the title bar, I deduce this is about Windows 10. Please fix it if this is wrong. Also, is it a clean installation or an upgraded installation? Was Hyper-V installed before upgrading?

– Daniel B
Oct 4 '15 at 13:05





From the title bar, I deduce this is about Windows 10. Please fix it if this is wrong. Also, is it a clean installation or an upgraded installation? Was Hyper-V installed before upgrading?

– Daniel B
Oct 4 '15 at 13:05













I have Windows 10 Pro and is clean installation

– Tack
Oct 4 '15 at 13:11





I have Windows 10 Pro and is clean installation

– Tack
Oct 4 '15 at 13:11










2 Answers
2






active

oldest

votes


















3














In ran into the same symptoms after a Windows 10 update, and re-installing the network adapter didn't help. However executing the following command in a PowerShell console fixed it:



New-VMSwitch VMSwitch -NetAdapterName Ethernet



This seemed to repair the network switch configuration so after this the Virtual Switch Manager started successfully and I was able to use it to remove and create virtual switches at will.






share|improve this answer

































    1














    Try to uninstall the network adapter from the device manager, and install it again.



    In most cases, after that, Hyper-V can create the virtual switch.






    share|improve this answer






















      protected by Pimp Juice IT Jan 23 at 23:24



      Thank you for your interest in this question.
      Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).



      Would you like to answer one of these unanswered questions instead?














      2 Answers
      2






      active

      oldest

      votes








      2 Answers
      2






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes









      3














      In ran into the same symptoms after a Windows 10 update, and re-installing the network adapter didn't help. However executing the following command in a PowerShell console fixed it:



      New-VMSwitch VMSwitch -NetAdapterName Ethernet



      This seemed to repair the network switch configuration so after this the Virtual Switch Manager started successfully and I was able to use it to remove and create virtual switches at will.






      share|improve this answer






























        3














        In ran into the same symptoms after a Windows 10 update, and re-installing the network adapter didn't help. However executing the following command in a PowerShell console fixed it:



        New-VMSwitch VMSwitch -NetAdapterName Ethernet



        This seemed to repair the network switch configuration so after this the Virtual Switch Manager started successfully and I was able to use it to remove and create virtual switches at will.






        share|improve this answer




























          3












          3








          3







          In ran into the same symptoms after a Windows 10 update, and re-installing the network adapter didn't help. However executing the following command in a PowerShell console fixed it:



          New-VMSwitch VMSwitch -NetAdapterName Ethernet



          This seemed to repair the network switch configuration so after this the Virtual Switch Manager started successfully and I was able to use it to remove and create virtual switches at will.






          share|improve this answer















          In ran into the same symptoms after a Windows 10 update, and re-installing the network adapter didn't help. However executing the following command in a PowerShell console fixed it:



          New-VMSwitch VMSwitch -NetAdapterName Ethernet



          This seemed to repair the network switch configuration so after this the Virtual Switch Manager started successfully and I was able to use it to remove and create virtual switches at will.







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Dec 30 '16 at 0:42

























          answered Dec 30 '16 at 0:20









          divegadivega

          1314




          1314

























              1














              Try to uninstall the network adapter from the device manager, and install it again.



              In most cases, after that, Hyper-V can create the virtual switch.






              share|improve this answer




























                1














                Try to uninstall the network adapter from the device manager, and install it again.



                In most cases, after that, Hyper-V can create the virtual switch.






                share|improve this answer


























                  1












                  1








                  1







                  Try to uninstall the network adapter from the device manager, and install it again.



                  In most cases, after that, Hyper-V can create the virtual switch.






                  share|improve this answer













                  Try to uninstall the network adapter from the device manager, and install it again.



                  In most cases, after that, Hyper-V can create the virtual switch.







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Mar 16 '16 at 20:13









                  Robson RochaRobson Rocha

                  563159




                  563159

















                      protected by Pimp Juice IT Jan 23 at 23:24



                      Thank you for your interest in this question.
                      Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).



                      Would you like to answer one of these unanswered questions instead?



                      Popular posts from this blog

                      Probability when a professor distributes a quiz and homework assignment to a class of n students.

                      Aardman Animations

                      Are they similar matrix