How To Fix Hyper V Error External Ethernet Adapter Is Already Bound To The Microsoft Virtual Switch

How To Fix Hyper V Error External Ethernet Adapter Is Already Bound To The Microsoft Virtual Switch ethernet adapter is already bound to the microsoft virtual switch protocol When I was reinstalling one of my home lab server with Server 2012 (overdue for months now…) I can across the following error when I tried to configure my virtual switch. external ethernet adapter is already bound to the microsoft virtual switch protocol After a quick google search I came across a MS support article which described this error to a T. You need to download the NVSPBind tool seperately from the MSDN website here. After opening the command prompt (in elavated administrator) I ran this command: nvspbind /u “Friendly NIC Name” When this was finished I was able to configure the virtual switch to connect to my external NIC. One thought on “ethernet adapter is already bound to the microsoft virtual switch protocol” The nuclear option that works with Windows Core is using netcfg to wipe out all your networking settings and re-initialize the network card drivers. DANGER! THIS WILL DELETE ALL YOUR NETWORKING SETTINGS! netcfg -d That seems to work better than nvspbind.exe or various other PowerShell commands when I really screw up my Hyper-V VMSwitch or LBFOTeam networking settings. Microsoft do not recommend you use DC&in a virtual environment because of time skew. If I was you I would setup yourself a small lab with HyperV in it so you can play about with the options, setting and learn...