locked
Virtual Switch Manager Anomaly - failed while adding virtual Ethernet switch connections RRS feed

  • Question

  • "Error applying Virtual Switch Properties changes" - Failed while adding virtual Ethernet switch connects

    External Ethernet adapter 'NIC' is already bound to the Microsoft Virtual Switch protocol.

    However, the PowerShell command Get-VMSwitch does not enumerate the NIC. How can I remove the Virtual Switch binding to the NIC and start all over again to create a virtual external connection. Hyper-V is running under Windows 10 Build 14267.rs1_release.160213-0213. The last update disabled the network connectivity. I can access the VMs through Hyper-V manager but there is no external network connectivity.

    The suggested workarounds to use utilities that have been deprecated could not run owing to the fact that Windows Script Host failed. Also, some of registry hacks could not be applied. The NICs (there are two in the machine with identical issues) are present in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e972-e325-11ce-bfc1-08002be10318}\001 and \002 but I have zero knowledge on what to reset here. Any advice to get back on track will be appreciated.

    Thanks.

    Friday, February 26, 2016 1:53 AM

Answers

  • Hi Sir,

    >>"Error applying Virtual Switch Properties changes" - Failed while adding virtual Ethernet switch connects

    External Ethernet adapter 'NIC' is already bound to the Microsoft Virtual Switch protocol.

    According to the error ,it seems that "hyper-v virtual switch protocol "  has been bound to that physical NIC .

    I would suggest you to check if there is an existing external virtual switch which bounded on that physical NIC via running command (check property "NetAdapterInterfaceDescription"  ) :

     Get-VMSwitch -SwitchType External | fl *

    If there is no external Vswitch or these NICs is not the target NIC which you want to bind external Vswtich , please check NIC property for that target NIC (if yes , you may uncheck it and select correct protocols ) :

    >>Hyper-V is running under Windows 10 Build 14267.rs1_release.160213-0213. 

    In addition , this is a client hyper-v issue .

    For more issue with client hyper-v , please post it into this forum:

    https://social.technet.microsoft.com/Forums/windowsserver/en-US/home?forum=win10itprovirt&filter=alltypes&sort=lastpostdesc

    Best Regards,

    Elton


    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com .

    • Proposed as answer by Elton_Ji Thursday, March 3, 2016 3:10 PM
    • Marked as answer by Elton_Ji Monday, March 7, 2016 2:37 AM
    Monday, February 29, 2016 2:05 AM

All replies

  • Hi Sir,

    >>"Error applying Virtual Switch Properties changes" - Failed while adding virtual Ethernet switch connects

    External Ethernet adapter 'NIC' is already bound to the Microsoft Virtual Switch protocol.

    According to the error ,it seems that "hyper-v virtual switch protocol "  has been bound to that physical NIC .

    I would suggest you to check if there is an existing external virtual switch which bounded on that physical NIC via running command (check property "NetAdapterInterfaceDescription"  ) :

     Get-VMSwitch -SwitchType External | fl *

    If there is no external Vswitch or these NICs is not the target NIC which you want to bind external Vswtich , please check NIC property for that target NIC (if yes , you may uncheck it and select correct protocols ) :

    >>Hyper-V is running under Windows 10 Build 14267.rs1_release.160213-0213. 

    In addition , this is a client hyper-v issue .

    For more issue with client hyper-v , please post it into this forum:

    https://social.technet.microsoft.com/Forums/windowsserver/en-US/home?forum=win10itprovirt&filter=alltypes&sort=lastpostdesc

    Best Regards,

    Elton


    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com .

    • Proposed as answer by Elton_Ji Thursday, March 3, 2016 3:10 PM
    • Marked as answer by Elton_Ji Monday, March 7, 2016 2:37 AM
    Monday, February 29, 2016 2:05 AM
  • Hi Elton,

    Thank you for the solution. I was facing this issue on my Windows 2019 Server and solution provided by you fixed it.

    Thanks,

    Amol Jadhav

    Wednesday, September 4, 2019 12:57 PM