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.
The bottom line is that customers should NOT attempt to create teams on client SKU. It is NOT supported on client SKU, and never has been. Classic NIC Teaming continues to be supported in Windows Server 2016.