Can't create Hyper-V vSwitch with Teaming on Window server 2025

Hi Leanghor,

This error is expected behavior on modern versions of Windows Server and Hyper‑V, and it’s not a misconfiguration on your side. Hyper‑V no longer supports attaching a virtual switch to an LBFO (NIC Teaming) team, which is exactly what your screenshots show. The error message and the PowerShell warning are accurate: the -AllowNetLbfoTeams parameter is obsolete and ignored.

Microsoft replaced LBFO for Hyper‑V scenarios with Switch Embedded Teaming (SET) starting from Windows Server 2016. With SET, you do not create a NIC team first; instead, you give multiple physical NICs directly to the virtual switch. That is why your attempt using an existing team named “VM‑Teaming” fails both in the GUI and PowerShell.

To fix this, delete or leave the existing LBFO team unused, then create the vSwitch using the physical adapters themselves. The correct PowerShell syntax is:

New-VMSwitch -Name "vSwitch-01" -NetAdapterName "NIC1","NIC2" -EnableEmbeddedTeaming $true -AllowManagementOS $true

Here, NIC1 and NIC2 must be separate physical adapters, not a team. Hyper‑V will handle teaming internally using SET, which is the supported and recommended method according to Microsoft.

If this host is running Windows Server 2012 R2 or earlier, SET is not available and LBFO with Hyper‑V is supported there only; however, your PowerShell warning indicates you are on a newer OS, so SET is required. Also verify that all participating NICs are identical in speed and configuration, as SET enforces stricter requirements than LBFO.

Microsoft’s official documentation explicitly states that LBFO teams cannot be bound to Hyper‑V switches on modern systems and must be replaced by SET, which aligns exactly with the error you are encountering.

I hope you've found something useful here. If it helps you get more insight into the issue, it's appreciated to accept the answer. Should you have more questions, feel free to leave a message. Have a nice day!

Harry.