No it is not possible to get NIC teamin in Windows 10 client SKUs. But available for Server SKUs.
From 14393 version (Anniversary update) this NIC teaming feature had been blocked or removed forever. It is seemed that the feature mistakenly added to client Windows 10 SKUs. When you put New-NetLbfoTeam command in PowerShell e.g.
New-NetLbfoTeam -Name "NewTeam" -TeamMembers "Ethernet", "Ethernet2", the error shows as follows
New-NetLbfoTeam : The LBFO feature is not currently enabled, or LBFO
is not supported on this SKU. At line:1 char:1
+ New-NetLbfoTeam -Name "NewTeam" -TeamMembers "Ethernet", "Ethernet2"
+ CategoryInfo : NotSpecified: (MSFT_NetLbfoTeam:root/Standa rdCimv2/MSFT_NetLbfoTeam)
+ FullyQualifiedErrorId : MI RESULT 1,New-NetLbfoTeam
The main reason was given in Social.TechNet.Microsoft: Nic Teaming broken in build 10586 as follows (quoted):
"There are no native LBFO capabilities on Win10. Microsoft does not
support client SKU network teaming.
It was a defect in Windows 10 build 10240 that “New-NetLbfoTeam”
wasn’t completely blocked on client SKUs. This was an unintentional
bug, not a change in the SKU matrix. All our documentation continued
to say that NIC Teaming is exclusively a feature for Server SKUs.
While the powershell cmdlet didn’t outright fail on client, LBFO was
in a broken and unsupported state, since the client SKU does not ship
the mslbfoprovider.sys kernel driver. That kernel driver contains all
the load balancing and failover logic, as well as the LACP state
machine. Without that driver, you might get the appearance of a team,
but it wouldn’t really do actual teaming logic. We never tested NIC
Teaming in a configuration where this kernel driver was missing.
In the 10586 update (“Fall update”) that was released a few months
later, “New-NetLbfoTeam” was correctly blocked again.
In the 14393 update (“Anniversary update”), we continued blocking it,
but improved the error message."