Using win 10 pro licensed version. Hyper V is enabled but when try to create virtual switch it is showing "Ethernet port bind failed element not found" i am using laptop and trying to use wifi adapter for the VSwitch.

Hi @Arijit Naha First of all it is recommended to reinstall the network device drivers with latest version from the manufacturer, as they may be corrupted or outdated. For this: Download the latest drivers Remove the device from Device Manager Detect hardware changes and use the specific downloaded drivers to configure the detected hardware. If this doesn't fix the issue, try the next: -Open Network Sharing Center -Click ‘Change Adapter Settings’ in the left-hand menu -Create the new External Switch in Hyper-V Manager. Or, you can also use New-VMSwitch PowerShell cmdlet. Both methods work. -While the “Applying” dialog is spinning away, or the PowerShell Progress “dialog”, switch over to the network adapters dialog you have open in Control Panel.-Disable your network adapter -Reenable your network adapter Hope this helps with your query, -- --If the reply is helpful, please Upvote and Accept as answer-

This still doesn't work for me. I get the same error when I do it thru Hyper-V manager or powershell. I am on windows 11 pro.

Well this work for me, it created 2 Extra devices not sure if that is correct. The Network Bridge and vEthernet (WLAN-Brdige)

Hyper V not able to add new virtual switch

Accepted answer

Limitless Technology 43,941 Reputation points

2022-02-25T16:30:31.717+00:00
Hi @Arijit Naha

First of all it is recommended to reinstall the network device drivers with latest version from the manufacturer, as they may be corrupted or outdated. For this:

Download the latest drivers

Remove the device from Device Manager

Detect hardware changes and use the specific downloaded drivers to configure the detected hardware.

If this doesn't fix the issue, try the next:
-Open Network Sharing Center
-Click ‘Change Adapter Settings’ in the left-hand menu
-Create the new External Switch in Hyper-V Manager. Or, you can also use New-VMSwitch PowerShell cmdlet. Both methods work.
-While the “Applying” dialog is spinning away, or the PowerShell Progress “dialog”, switch over to the network adapters dialog you have open in Control Panel.-Disable your network adapter
-Reenable your network adapter

Hope this helps with your query,

--
--If the reply is helpful, please Upvote and Accept as answer-
Please sign in to rate this answer.

7 people found this answer helpful.
Arijit Naha 26 Reputation points

2022-02-28T07:58:08.393+00:00

2nd method fixed the issue. I am still not sure the reason of the issue.

KD 1 Reputation point

2022-10-07T04:28:25.287+00:00

2nd method also worked for me.

As an added bonus I find it hilarious. I expected to end up with duplicated pokemon like on the gameboy color.

Nelson Tovar Solorzano 1 Reputation point

2022-10-11T18:19:26.93+00:00

Worked for me too. (2nd method).

Ninad 6 Reputation points

2023-01-07T21:07:34.297+00:00

Hi ArijitNaha,

For me too the second method worked. I think what happens is the Virtual Switch Manager ( VSM ) first grabs the host network adapter's GUID. Then restarts that adapter. However, after the restart the host network adapter's GUID is changed. Now the virtual switch manager can't find old GUID.

When the VSM begins creating the switch the host network adapter must be already in disabled state. When it is enabled, the VSM grabs the new GUID and the process is through.

Hope this helps. Thank you!

-Ninad

Eric Siron 1,251 Reputation points MVP

2023-01-20T21:20:44.7933333+00:00

The "fix" is to unbind the virtual switch protocol (it used to be vmsp, probably still is), uninstall vmsp, install vmsp, and then setup the switch again. I had instructions on how to do this up until about Windows Server 2012 R2 but it was always a pain. This is an old post that I never saw or I would have dug them out. Uninstalling the adapter from device manager has the side effect of removing all bindings. The system gets an opportunity to start fresh when recreating the virtual switch after that. Sometimes the protocol still needs to be removed and reinstalled, but when the Device Manager approach works, it's a lot easier.

ack 0 Reputation points

2023-03-12T19:06:04.3266667+00:00

After doing the second method I get the same error however after I check network and sharing I find a network bridge with the same settings but it does not let me use the switch in Hyper-V.

Gopi 0 Reputation points

2023-03-14T13:12:23.2133333+00:00

This worked for me..

Radoslav Bahchedzhiev 0 Reputation points

2024-02-15T10:57:18.18+00:00

Helpful! I had to "Disable this network device" and "Enable this network device" on mine Wi-Fi "Intel(R) Dual Band Wireless-AC 3165" during the Hyper-V Virtual Switch creation process when it is creating it at the very end. Enabling and disabling is made over the Wi-Fi adapter in the ncpa.cpl - control panel item.
Sign in to comment

Hyper V not able to add new virtual switch

2 additional answers