NIC teaming sounds simple: combine two network adapters and get more bandwidth or redundancy. On Windows Server, that idea is familiar because LBFO NIC Teaming has been part of the server admin toolbox for years. On Windows 10, the story is messier.
Some Windows 10 builds include the NetSwitchTeam PowerShell cmdlets, and those cmdlets can create a switch team from multiple adapters. That is what most people mean when they ask how to enable NIC teaming in Windows 10 using PowerShell. But it is not the same as the full Windows Server LBFO experience, and it is not a magic way to turn two 1 Gbps adapters into one perfect 2 Gbps internet connection.
This guide shows the working PowerShell approach with New-NetSwitchTeam, how to verify and remove the team, and when you should stop trying to make Windows 10 do this and use Windows Server, a managed switch, or vendor-supported adapter software instead.
NetSwitchTeam vs LBFO in plain English
The confusing part is that Windows has more than one teaming-related command set.
Windows teaming options
| New-NetSwitchTeam | Creates a switch team controlled by the Hyper-V extensible switch forwarding extension. This is the command people commonly test on Windows 10. |
|---|---|
| New-NetLbfoTeam | Creates an LBFO NIC team. Microsoft documents this in the Windows Server PowerShell reference, and it is the server-style teaming model. |
| Switch Embedded Teaming (SET) | Used with Hyper-V virtual switches on modern Windows Server scenarios. This is not the same as classic Windows 10 client teaming. |
| Vendor teaming tools | Sometimes available from NIC vendors, depending on adapter model, driver package, and Windows version. |
For Windows 10, the practical command to try is New-NetSwitchTeam. If your actual requirement is LACP, production failover, or a supported server configuration, use the server path instead. Our Hyper-V external switch guide is also worth reading if your goal is VM networking rather than combining physical links on the client.
Before you start
Make sure the setup is worth attempting. NIC teaming is very sensitive to adapter drivers and the network gear on the other side.
NIC teaming prerequisites
- Two or more physical Ethernet adapters are installed and visible in Windows
- You are running PowerShell as administrator
- The adapters are not already part of another team or virtual switch
- You know which adapter currently holds your working IP configuration
- You have local access or another way back in if remote networking drops
- You are not expecting a single browser download or speed test to use both links automatically
Do this locally if possible. If you are connected over Remote Desktop and you team the adapter carrying your session, you can disconnect yourself. That is not a disaster if you are sitting at the machine. It is much less fun if the PC is in another room or another city.
Step 1: Open PowerShell as administrator
Right-click Start, choose Windows PowerShell (Admin) or Terminal (Admin), and confirm the UAC prompt.
Then list the adapters:
Get-NetAdapterLook at the Name, Status, MacAddress, and LinkSpeed columns. You need the exact adapter names for the team command.
Example output might include names like:
Name InterfaceDescription Status LinkSpeed
---- -------------------- ------ ---------
Ethernet Intel(R) Ethernet Connection Up 1 Gbps
Ethernet 2 Realtek PCIe GbE Family Controller Up 1 Gbps
Wi-Fi Intel(R) Wi-Fi Up 866.7 MbpsFor a normal wired team, use Ethernet adapters. Mixing Wi-Fi and Ethernet is usually a poor idea, even if a command lets you try it. Wi-Fi behaves differently at layer 2 and is not a good foundation for this kind of setup.
Step 2: Create the switch team
Use New-NetSwitchTeam with a team name and the adapter names.
New-NetSwitchTeam -Name "Team01" -TeamMembers "Ethernet","Ethernet 2"If the command completes without an error, Windows creates a team interface. The physical adapters become members of that team.
Use a simple team name. Avoid special characters. If you later need to remove it, you want the name to be obvious.
Step 3: Verify the team
Check the team:
Get-NetSwitchTeamThen check the adapters again:
Get-NetAdapterYou should see a new team-related interface and the member adapters. Depending on the Windows build and driver behavior, the active IP configuration may move to the team interface or need to be set again.
If the machine loses internet after creating the team, do not immediately assume the team failed. Check the IP configuration first:
ipconfig /allLook for:
- The team interface has an IP address.
- DHCP is enabled if you expect DHCP.
- The default gateway exists.
- DNS servers are present.
- The physical member adapters are not holding conflicting static settings.
If you recently changed DNS while troubleshooting, the guide on changing DNS on Windows covers how to confirm and reset DNS settings cleanly.
Step 4: Test the result correctly
This is where expectations go sideways. A team does not guarantee that one file download or one speed test will use both adapters. Many load-balancing methods distribute traffic by flow. A single TCP connection often stays on one link.
Better tests:
- Copy multiple large files at the same time to another machine on the LAN.
- Run several parallel network streams with a proper network test tool.
- Test failover by disconnecting one cable and confirming the machine stays reachable.
- Watch adapter counters instead of trusting one browser speed test.
If your goal is only faster internet from a normal home router, NIC teaming may not help. Your ISP speed, router uplink, switch, adapter drivers, and connection type all matter. Two local 1 Gbps adapters do not make a slow WAN link faster.
Remove the team safely
If the team does not behave well, remove it:
Remove-NetSwitchTeam -Name "Team01"Then check the adapters:
Get-NetAdapter
ipconfig /allAfter removal, confirm that your original adapter has the correct IP settings. If the team interface held a static IP address, you may need to put that configuration back on the physical adapter.
For DHCP networks, you can renew the address:
ipconfig /release
ipconfig /renewFor static networks, set the IP, gateway, and DNS again in the adapter properties or with PowerShell.
What about New-NetLbfoTeam?
You will still see older commands like this:
New-NetLbfoTeam -Name "Team1" -TeamMembers "NIC1","NIC2"That command belongs to the NetLbfo module and is documented for Windows Server. It is the right conversation when you are administering servers and need LBFO features such as teaming modes and load-balancing algorithms.
For Windows 10, do not build a plan around New-NetLbfoTeam. If it fails, that is expected on many client installations. If you need those features, move the workload to Windows Server or use a supported hardware/vendor path.
Troubleshooting common errors
The command is not recognized.
The NetSwitchTeam cmdlets are not available on your system, or the module is not present in that Windows build. Confirm with:
Get-Command *NetSwitchTeam*If nothing returns, do not force it with copied files or unsupported driver tricks. Use a supported option.
The team is created but there is no internet.
Check DHCP, gateway, and DNS on the team interface. The team may exist, but the usable IP configuration may not have landed where you expected.
The team works but speed is not doubled.
That is normal for many traffic patterns. Test multiple simultaneous flows. Also confirm the switch/router supports the behavior you expect.
One adapter is 1 Gbps and the other is 100 Mbps.
Avoid teaming mismatched adapters. Even when a command allows it, the result is often disappointing and difficult to reason about.
You are using Wi-Fi plus Ethernet.
Do not expect this to behave like a clean wired team. If you need reliable link aggregation, use wired adapters and network gear designed for it.
When Windows Server is the better answer
Use Windows Server instead of Windows 10 client teaming when:
- The machine provides a production service.
- You need a supported LBFO configuration.
- You need LACP or specific teaming modes.
- You are building Hyper-V infrastructure.
- You need predictable failover behavior.
- You are documenting the setup for other admins to maintain.
Windows 10 can be fine for a lab, a test bench, or a one-off workstation experiment. It is not the right place to hide a production networking dependency.
If your real goal is virtualization networking, start with the correct virtual switch design. Our guides on Hyper-V external virtual switches, Hyper-V VMs with no internet, and VirtualBox NAT vs bridged networking cover the problems most people are actually trying to solve when they reach for teaming.
Wrapping up
To enable NIC teaming in Windows 10 with PowerShell, the command to try is New-NetSwitchTeam:
New-NetSwitchTeam -Name "Team01" -TeamMembers "Ethernet","Ethernet 2"Verify it with Get-NetSwitchTeam, check the IP configuration, and test with realistic traffic. If it does not behave, remove it with Remove-NetSwitchTeam and restore the adapter settings.
The bigger point is knowing the boundary. Windows 10 switch teaming can work in some setups, but it is limited. For production networking, full LBFO behavior, or clean supportability, use Windows Server or a vendor-supported solution. That answer is less flashy, but it is the one that will still make sense when you have to troubleshoot the network later.
