How To Fix Error Applying External Switch Adapter In Hyper v

How To Fix Error Applying External Switch Adapter In Hyper v | how to fix external ethernet adapter is already bound to microsoft virtual switch protocol

External Ethernet Adapter is already bound to the microsoft virtual switch protocol
When trying to create a virtual switch from the Virtual Network Manager, you receive an error message while applying the new virtual network changes. The error message states: "Setup switch failed. Cannot bind to name of network adapter because it is already bound to another virtual network."
We already talked about IP networking in Hyper-V and the procedure used to configure virtual network switches. Sometimes, it does not work due to the issues with the network adapter and host. One of the challenges end-users are facing is with the creation of external switch in Hyper-V client hosted on Windows 10.
The Windows 10 users are literally getting issues with the network adapter and host for the Hyper-V virtual switch network. Some users are experiencing error applying virtual switch properties changes with Hyper-V. So, Windows 10 users aren’t able to create an external switch in Hyper-V client. The error message says “Failed while adding virtual Ethernet switch connections.” along with a bunch of error codes. If you’re also one of the victims then check this troubleshooting guide.

According to some of the affected users, whenever they trying to create a virtual switch over the external network on the ethernet port, they get an error message that the “ethernet port bind failed (access denied). A process has requested access to an object but has not been granted those access rights. (0xC0000022).” Now, the interesting part is that users can still create an internal or private virtual network but not the external for PXE boot.
Fix: Error applying Virtual Switch Properties changes – Hyper-V

Regards
Quazi Mahmudul Huq
Senior Faculty
IT System Admin
MCT, MCP, MCSA, MCSE, RHCSA, RHCE
RHCSV, CCNA, CCNP, MTCNA, MTCRE

[alexzhu]

In my case the problem was the Virtualbox virtual adapter also connected to the same physical network adapter (Wi-Fi card).
Uninstaling Virtualbox also uninstalled its virtual adapter and I was able to create external virtual switch in Hyper-V manager.
(Waiting for Virtualbox guys to release the fix for Windows 11 and Hyper-V and forced to use Hyper-V meanwhile).

[koloarnaud]

The best solution that i found
Thanks to you

[santiagogilcuartas]

What should I do if I need two external switches for two different networks so that each virtual machine has a different network?

[wahbanger]

Hi, I get a different error saying "Adding ports to ExternalVWAN failed". Any idea on how to resolve this error? Thanks

[erickarrieta]

Muchas gracias, excelente solución !!

[Sureshgrace]

Sir.. still problem not resolved.. please help

[not_a_good_idea]

is it possible to create multiple external switch?

[hobsonbeeman]

Probably good information, but accent was tough to understand and took away from being able to follow what was being said