How to create Switch Embedded Team for Virtual Network Switch

Question

I want to add a virtual switch for my Hyper-V I am hosting. This virtual switch unfortunately doesn't work for my current setup:

• NIC Teaming activated, LACP Bond for "Ethernet" and "Ethernet 2" with a dynamic load balancing.
  Trying to add the virtual switch to this bond outputs the following (translated from german):
  """Error applying virtual switch properties
  Error adding connections for the virtual Ethernet switch.

An LBFO team cannot be attached to a virtual Hyper-V switch. If teaming is required, use "New-VMSwitch" to create a Switch Embedded Team (SET). For more information, see: https://go.microsoft.com/fwlink/?linkid=2185083 """

I checked out the link, cleaned the network configs with

netcfg -d

and got to work setting everything up.

My commands were as follows:

New-VMSwitch`` ``-Name`` ``$SwitchName`` ``-NetAdapterName`` ``$NIC1Name``,``$NIC2Name`` ``-EnableEmbeddedTeaming`` ``$true`` ``-AllowManagementOS`` ``$true`` ``-Confirm``:``$false

Set-VMSwitchTeam`` ``-Name`` ``$SwitchName`` ``-TeamingMode`` SwitchIndependent``-LoadBalancingAlgorithm`` Dynamic

New-NetIPAddress`` ``-InterfaceAlias`` ``$vEthernetName`` ``-IPAddress`` ``$IPAddress`` ``-PrefixLength`` ``$PrefixLength`` ``-DefaultGateway`` ``$Gateway

Set-DnsClientServerAddress`` ``-InterfaceAlias`` ``$vEthernetName`` ``-ServerAddresses`` ``$DNS1``,``$DNS2

Unfortunately, not even a restart of my server after this setup managed to establish a connection.

I also tried the Set-VMSwitchTeam with -Teamingmode LACP, but that yielded an error along the lines of:
"""The value LACP can not be convertet do VMSwitchTeamingMode.""" (I don't know the exact wording anymore)

Does anyone know how to fix this? I need my host and my VM to have a stable internet connection and I don't care how I can get there.

Cheers!
Fabian

Answer 1

Hello Fabian Felden.

Thank you for contacting Microsoft Community.

---

As far as i know, it is not possible to use the Hyper-V Management Console to create a virtual switch with LBFO. However, it is possible to use PowerShell to create this virtual switch.

First, create the Teaming of your network cards.

NIC Teaming Creation:

New-NetLbfoTeam -Name "NIC Team Name" -TeamMembers "NIC1 Name","NIC2 Name" -TeamingMode LACP -LoadBalancingAlgorithm Dynamic

Then execute the below PowerShell Command to create the virtual switch based on the teaming created in the previous step:

New-VMSwitch -Name "Hyper-V vSwitch Name" -NetAdapterName "NIC Team Name" -AllowNetLbfoTeams $true

Looking forward to your updates!

---

If you found this answer helpful, please click "Accept Answer" to share the love with everyone! 💖

Thank you again for your patience and support – it really means a lot to us!

Dustin Tran

Answer 2

To create a Switch Embedded Team (SET) for your Hyper-V virtual switch, you need to ensure that you are using the correct commands and parameters. Here’s a step-by-step guide based on your setup:

1. Create the Virtual Switch: Use the New-VMSwitch command to create a new virtual switch. Ensure you specify the correct parameters for your network setup.

      New-VMSwitch -Name <YourSwitchName> -NetAdapterName <YourNetAdapterName>
   

   Replace <YourSwitchName> with the desired name for your switch and <YourNetAdapterName> with the name of the network adapter you want to use.
2. Configure the Switch Team: After creating the virtual switch, configure the switch team using the Set-VMSwitchTeam command. Make sure to set the -TeamingMode to SwitchEmbeddedTeam if you are using SET.

      Set-VMSwitchTeam -Name <YourSwitchName> -TeamingMode SwitchEmbeddedTeam -LoadBalancingAlgorithm Dynamic
   

   Ensure that you replace <YourSwitchName> with the name of your switch.
3. Set IP Address and DNS: After configuring the switch, set the IP address and DNS server addresses as needed for your network configuration.

      New-NetIPAddress -InterfaceAlias <YourSwitchName> -IPAddress <YourIPAddress> -PrefixLength <YourPrefixLength>
      Set-DnsClientServerAddress -InterfaceAlias <YourSwitchName> -ServerAddresses <YourDNSServer>
   

   Replace <YourIPAddress>, <YourPrefixLength>, and <YourDNSServer> with your specific network settings.
4. Restart the Server: If you encounter issues, a server restart can sometimes help establish the connection.

If you still face issues, ensure that your network adapters are compatible with SET and check for any additional configurations that might be required for your specific environment.

Also, note that LACP (Link Aggregation Control Protocol) is not supported with SET; you should use SwitchEmbeddedTeam mode for your configuration.

---

References:

• Create and configure a virtual switch with Hyper-V (windows)
• Set-VMSwitchTeam

Answer 3

Hi Fabian,
Welcome to Microsoft Q&A forum. It's my pleasure to help you today.

Based on everything you described, the root cause is that the old LBFO (LACP) team was never fully removed from the system. Even if you run netcfg -d or stop using the team, as long as the LBFO team still exists in Windows (Network Connections, Get-NetLbfoTeam, Device Manager), Hyper-V will not bind the physical NICs correctly to the new SET switch.

When LBFO is still present, the two physical NICs remain "owned" by the team driver, so the SET vSwitch effectively has no real adapters to pass traffic through → resulting in no connectivity.

This is also why:

• -TeamingMode LACP fails (SET does not support LACP),
• the vEthernet interface never gets upstream connectivity even after reboot.

Once the LBFO team is completely removed, the NICs return to standalone mode, and the SET vSwitch will immediately start working normally.

So the fix is simply: delete the LBFO team entirely, then reattach the NICs to your existing SET switch. After that, your host and VMs will regain network connectivity.

If you believe this information adds some value, please accept the answer so that your experience with the issue would help contribute to the whole community.
Best wishes!
Titus Bui.

Answer 4

Hi Fabian ,

Sorry for the delay!

To fully remove the old LBFO (NIC Teaming) configuration (so your NICs can be used by the SET vSwitch), please use the supported LBFO cmdlets rather than netcfg -d.
**
Option 1 — PowerShell (Run as Administrator)

1. List existing LBFO teams

Get-NetLbfoTeam

2. Remove the team (replace with your actual team name)

Remove-NetLbfoTeam -Name "YourTeamName"

3. If the team had VLAN interfaces, remove those as well (optional)

The -Team value is the team interface name, e.g. "YourTeamName - VLAN 42"

Remove-NetLbfoTeamNic -Team "YourTeamName - VLAN 42"

4. Verify removal (should return nothing)

Get

Option 2 — Server Manager

• Server Manager → Local Server → NIC Teaming → select the LBFO team → Delete Team.

Reference:

Remove LBFO team: https://learn.microsoft.com/en-us/powershell/module/netlbfo/remove-netlbfoteam

LBFO cmdlets overview: https://learn.microsoft.com/en-us/powershell/module/netlbfo/

Note: netcfg -d resets the network stack and virtual adapter bindings, but does not remove LBFO because LBFO is managed by the NIC Teaming service.

If you’re in a new build or test environment, the fastest approach is:

Remove LBFO completely.

Recreate the SET configuration from scratch for a clean setup.

I hope you are clear with the information. It's really appreciated of you to accept the answer to let others know more about your issue. Should you have any more questions, feel free to leave a message.

Cheers!
Titus Bui.

Answer 5

Hi Fabian,

Thanks for following the steps to remove the LBFO team. Before we continue with deeper troubleshooting on the SET switch, I need to confirm that the old LBFO configuration has been fully removed at the OS level. Sometimes the LBFO service leaves behind team objects even if they no longer appear in the GUI, and this can block the SET vSwitch from passing traffic.

To make sure everything is clean, could you please provide the following screenshots?

1. PowerShell output

Please run:

Get-NetLbfoTeam
Get-NetLbfoTeamNic

And send me a screenshot of the result. Expected: Both commands should return no objects (blank result).
2. Server Manager - Nic Teaming

From: Server Manager → Local Server → NIC Teaming Please capture the section showing that:

• NIC Teaming = Disabled
• No LBFO teams listed

3**. Network Connections**
Please open ncpa.cpl and send a screenshot of all network adapters. I want to verify:

• No “Team” or “LBFO” virtual adapters remain
• Only the two physical NICs + the SET vEthernet adapter

Once I have these screenshots, I can confirm whether the LBFO was fully removed. This will help avoid false assumptions and ensure we troubleshoot the real root cause of the “No Internet” issue on the SET switch.

Thank you, Fabian — looking forward to your screenshots.