Nic Teaming broken in build 10586 RRS feed

  • Question

  • I just went back to build 10240, because I cannot get nic teaming working at all.

    In 10240 I have Nic teaming (LACP) with intel drivers, and another nic team via powershell (LACP),

    but after an upgrade to 10586 both could not be re-enabled.

    Powershell errors out with an 87 error and intel just refuses to enable the team.

    Has anyone got nic teaming working in windows 10 build 10586 ?

    Saturday, November 14, 2015 1:07 PM


All replies

  • Been noticed that NIC teaming does not work in the last couple of Insider builds as well

    Teaming not possible in Win10pro Insider Builds 10565 and 10576 - error 87

    No work-around that has been found for NIC teaming in 10586.

    Saturday, November 14, 2015 1:35 PM
  • Does anyone from Microsoft ever Read or Answer these posts?

    I've not seen one reply from Microsoft, as stated on another thread, Windows 10 Pro is getting Less Pro each time something is done to it. Almost every new Motherboard on the market has 2 nics, why is this not supported?

    Friday, February 26, 2016 5:34 AM
  • NIC Teaming failed (Build 10568) Windows 10

    Has a response from MSFT, sometime ago now perhaps but;

    "I wanted to let you know that we are tracking this issue currently, however no ETA on fix at this time. I will update the thread once we have identified a fix or workaround for the issue.

    Adam Rudell | Windows Networking Beta | Microsoft Corporation" Monday, November 16, 2015 7:00 PM

    Friday, February 26, 2016 11:34 AM
  • Any more movement of this.

    Getting very annoying having to deal with Microsofts more constant short-comings, but NIC teaming was killed months ago and still no word on a fix or even if their planning on fixing it.

    Just bought some new licenses for another project, but rethinking it now.

    Thursday, May 12, 2016 9:44 PM
  • 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.

    (Edit) NIC Teaming however can be done using 3rd party software, just the native LBFO teaming available from Microsoft is not supported on client SKUs.

    Adam Rudell | Windows Networking Beta | Microsoft Corporation

    Tuesday, September 6, 2016 4:17 PM
  •  I second that question. There are many NAS and wireless gigabit routers out there now that support port aggregation, so why would this be a server only option? If I have Windows 10 Pro that can join domains and supports RDP, why in the world can't I NIC Team?
    Sunday, December 18, 2016 6:05 AM