none
NIC Teaming failed (Build 10568) Windows 10

    Question

  • The following does not work:

    First command to view the adapters:

    PS C:\Windows\system32> Get-NetAdapter

    Name                      InterfaceDescription                    ifIndex Status       MacAddress             LinkSpeed
    ----                      --------------------                    ------- ------       ----------             ---------
    ETH02                     Intel(R) 82579V Gigabit Network Conn...       4 Up           C8-60-00-A4-5B-66         1 Gbps
    ETH03                     Intel(R) Gigabit CT Desktop Adapter #2        6 Up           68-05-CA-13-F5-2F         1 Gbps

    Second command to make a teaming interface:

    PS C:\Windows\system32> New-NetLbfoTeam -Name Team001 -TeamMembers ETH02,ETH03 -TeamingMode LACP
    New-NetLbfoTeam : De parameter is onjuist.
    At line:1 char:1
    + New-NetLbfoTeam -Name Team001 -TeamMembers ETH02,ETH03 -TeamingMode LACP
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidArgument: (MSFT_NetLbfoTeam:root/StandardCimv2/MSFT_NetLbfoTeam) [New-NetLbfoTeam
       ], CimException
        + FullyQualifiedErrorId : Windows System Error 87,New-NetLbfoTeam

    Something broke in this build (10568). Any idea?

    Found this already: https://social.technet.microsoft.com/Forums/en-US/936e8936-810c-434f-9e06-525daafa50b8/teaming-not-possible-in-win10pro-insider-builds-10565-and-10576-error-87?forum=WindowsInsiderPreview

    And: https://social.technet.microsoft.com/Forums/en-US/504864ee-abad-49e0-9e6a-4a817e21e3d6/nic-teaming-broken-in-build-10586?forum=win10itpronetworking

    But no luck there.....

    PS: Using Intel cards: Intel dropped support for NIC teaming (Only Windows 10) in the latest update. Using a previous version of the utility does not work, because the teaming interface stays down. (Even the powershell modules are not supported....)  :'(

    There is one thing what works.... rollback or clean install your PC to the previous build and disable the Windows Update service. (services.msc => Windows Update set option disable and stop the service)


    • Edited by T Slenter Saturday, November 21, 2015 12:51 PM
    Saturday, November 14, 2015 7:03 PM

All replies

  • This has been reported by and recreated by others (and in the last two Insider Builds the same issue as well)

    Nic Teaming broken in build 10586

    No current fix or work-around I am aware of.

    Saturday, November 14, 2015 7:14 PM
  • Same for me... I went back to 10240 where it was at least working thru the drivers of intel.
    Saturday, November 14, 2015 8:01 PM
  • What the hell? I just updated to TH2 and NIC Teaming is gone. Installing newest Intel drivers does not work. Why would you do that MS?
    Sunday, November 15, 2015 1:46 PM
  • I echo the sentiments expressed in this thread. I'm very unhappy about this.

    Bring back NIC teaming Microsoft!
    Monday, November 16, 2015 7:14 AM
  • 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
  • Is there any progress in identifying the fix/workaround?
    Tuesday, December 8, 2015 8:02 PM
  • We are still waiting for a fix. I don't want to roll back and disable Windows 10 updates.....
    Sunday, December 13, 2015 5:08 AM
  • Same here add me to the list of people complaining about this with no feedback from MS

    Monday, December 14, 2015 1:06 PM
  • I am also waiting. Updates off? Stay at Win 7? Rather poor options. How about adding support for ANS? Intel can do it then. I think most started using New-NetLbfoTeam because ANS is not supported in Windows 10. It would be nice to know if there are actually plans for ANS support.
    Wednesday, December 16, 2015 12:07 AM
  • Looking forward to having it back!
    Saturday, January 16, 2016 4:21 AM
  • 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

    Ok. MS broke this over 2 months ago. A fix, or at lest projected fix date is long overdue, especially since MS is tracking and can replicate the issue. Making me sad I ever upgraded to Windows 10 #anotherpieceshitOSfromMS  
    Saturday, January 16, 2016 5:04 AM
  • MS please provide an update.
    Monday, February 1, 2016 10:57 PM
  • Is there any progress in identifying the fix/workaround?
    Monday, February 8, 2016 2:34 PM
  • Also waiting for update here too
    Friday, February 12, 2016 11:32 AM
  • Desperately need this to work again.  Can't afford the upgrade to 10Gbe, but have several 4 port NICs now useless!!!
    Tuesday, February 16, 2016 12:20 AM
  • How can I do this?  I need it to work more than I need the updates.
    Tuesday, February 16, 2016 12:21 AM
  • I'm starting to believe that MS has no intention of fixing this - been broken for at least 2 months at this point...
    Tuesday, February 16, 2016 12:22 AM
  • I wonder how serious the risks are using that old build? No easy way to tell with fixes on fixes on the new builds, I guess I don't trust the old builds security updates. How do I go back and use my apps etc. on Windows 7. If MS doesn't fix it I would like downgrade rights to windows 8.1 - at least it will be around for several years unlike windows 7. For the effort it will take me windows 8.1 sounds like the best (cough cough) solution for an unacceptable situation.

    Is the real problem not enough people care?

    Wednesday, February 17, 2016 3:47 PM
  • Have had to roll back over 12 PCs for my clients... any update?
    Wednesday, February 17, 2016 10:15 PM
  • Hello,

    same issue here with Intel dual and quad port hardware  (x520da2 / x540t2  / x710da4)

    We upgraded from Windows 7 to Windows 10 and now strongly regret it.Please at least communicate upon the real reasons/status.I cant believe this kind of issue takes so long only for technical reasons. We are talking about "professionnal" versions of the OS. I know this word "professionnal" is often over-employed :I have even seen  professionnal toilet paper and womens tampons in some supermarket but despite the joke remains some biterness.

    Regards

     

    Tuesday, February 23, 2016 9:38 PM
  • Sorry to insist, but are there any progress/news since this statement of mid November that Microsoft is working on this issue ?

    Regards

    Tuesday, March 1, 2016 5:56 PM
  • This morning, cumulative update to Win 10 : 10586.122

    Link aggregation between the 2 ports of a Intel X520-DA2 still not working.

    We reverted to Win 7 on all machines but one for monitoring this issue...

    This makes the "Microsoft recommands  Windows 10 upgrade" popup even more upsetting than beofre...

    • Proposed as answer by Røman Tuesday, March 8, 2016 12:31 AM
    • Unproposed as answer by Røman Tuesday, March 8, 2016 12:31 AM
    Wednesday, March 2, 2016 8:39 AM
  • This morning, cumulative update to Win 10 : 10586.164

    Still no teaming possible (I understand this will requiere also a modification from Intel side, but nothing in the release notes that says this issue is being adressed...)

    Wednesday, March 9, 2016 9:09 AM
  • Basic OS Teaming (no Intel drivers needed) is as well not working.

    I usually  create my Teaming with Powershell.

    See powershell Command: Get-NetLbfoTeam and New-NetLbfoTeam

    The scripts still do not work as with old builds.


    • Edited by Haikos Friday, March 11, 2016 9:22 AM
    Friday, March 11, 2016 9:21 AM
  • It's amazing that it is not solve the problem. You have to sue Microsoft to give back the money you spent on the devices.
    Saturday, March 12, 2016 8:19 AM
  • 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

    Any updates on this? This issue still isn't solved.

    Last we got from you was 5 Months ago, nothing since...

    Sunday, March 13, 2016 9:33 PM
  • +1

    Leaving us alone with this issue for nearly half a year is bold, especially since MS slowly but steadily enforces the "optional" upgrade to Win10.

    We all know it worked once, so it can't be that hard to fix this issue. However, I have the strong suspicion that MS wants to swap out such Pro-User-features into the Windows Server Edition...

    Monday, March 14, 2016 2:06 PM
  • 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

    Is there someone specific that we can contact in order to get this issue worked on?

    Do we need to sign a petition?

    Are these forums even read by MS development team? I feel like issues like this one are simply getting ignored because there is no outcry about it.

    Please ARUDELL, let us know, what do we need to do to have somebody at MS listen to us and get this fixed? Because 5 months is an excessively long time to fix something that was previously working.

    Things don't simply go away if you ignore them...

    I suppose I shouldn't expect you or any other MS staff to respond, since this has been silent for a while but an update or an ETA would be acceptable. 

    Tuesday, March 15, 2016 12:16 AM
  • Adam,

    Please provide an update with a ETA for the fix. This problem has been causing huge disruption in our company for the past months, and we had to purchase smart switches for all collaborators as a manual workaround for this issue.

    - Daniel

    Tuesday, March 15, 2016 10:35 AM
  • it's still alive on Intel side...

    https://communities.intel.com/thread/77934?start=45&tstart=0

    and maybe the end of the tunnel is coming (but we don't see light yet !)

    Tuesday, March 15, 2016 8:03 PM
  • it's still alive on Intel side...

    https://communities.intel.com/thread/77934?start=45&tstart=0

    and maybe the end of the tunnel is coming (but we don't see light yet !)

    I hope the same...

    Santiago Fernandez Devoto

    Wednesday, March 16, 2016 8:28 PM
  • I agree this is absolutely ridiculous that NIC teaming does not work.  This should be table stakes as far as requirements go.  As PCs need to support additional performance and resiliency, this is a very important feature.  Microsoft without this feature, you are pushing your customers away to non-Microsoft alternatives.


    Sunday, March 20, 2016 2:07 PM
  • I have given up on Windows 10...I am going back to Windows 8.1, just so that I can use NIC Teaming again.

    Please consider fixing this!!  ASAP!!


    • Edited by faith2walk Sunday, March 20, 2016 6:14 PM
    Sunday, March 20, 2016 6:14 PM
  • Microsoft will publish a hotfix that will be available to beta testers today only.
    Friday, April 1, 2016 3:03 PM
  • Was this a (bad) April fool's joke or is this really happening (@Mario_Sd)? I can't believe MS is taking so long to fix this integral feature. 
    • Edited by Robpollard Tuesday, April 5, 2016 12:57 AM
    Tuesday, April 5, 2016 12:56 AM
  • Looks like we are as likely to get this fixed as SSTP on Windows Phone.

    They can get sodding bash on it to please people who would rather stick needles in their eyes than use windows but they cant fix nic teaming for their loyal customers.

    What a joke; Say what you want about Ballmer but this bull wouldn't have happened under his watch.


    Thursday, April 7, 2016 4:40 PM
  • Yeah what a bunch of pr***. Won't answer or comment. Not brave enough might have to answer to the money people. Now I have to do a bunch of extra stuff and install windows 10 just to get digital entitlement then blow it away if they fix it. I wonder if MS thinks this is it is hard to do. Well only for the stupid or paying sucker there are lots - thankfully for me it is easy. Till then use windoze 8.1. I'd rather suspect it it political and Investment based due to a marketing spyware problem with ANS or NIC teaming. Any other reasons you can think of for no descent responses? Too bad they shifted from technology and capability to what's in it for me. Guess we need a new technology like OS independent Network optimization so we don't rely on MS again.

    Saturday, April 9, 2016 7:54 AM
  • I've been looking at server 2016 TP4 just to see what differences there were between win10 that cannot do teaming and server 2016tp4 that can. One of the things I noticed is that the MsLbfoProvider.sys is there in server 2016 but not in windows 10. But even in server2016, teaming cannot be enabled thru powershell. You have to do it thru LfboAdmin.exe.

    Unfortunately you cannot edit a windows 10 machine in the admin since it isn't a registered server.

    Also the Microsoft Network Adapter Multiplexor Driver is not installed by default in windows 10 where it is in server 2016. Without that, no teaming. It is provided by ndisimplatformmp.inf

    The inf that is supposed to install the multiplexor driver is hidden from selection by default. If I remove [ControlFlags]
    ExcludeFromSelect = COMPOSITEBUS\MS_IMPLAT_MP 

    It will try to install it but fails on inf signature. Without this driver installed we cannot get it to work.

    I've tried adding it to the upnp store to see if it would load, but no luck.

    Tried thru rundll32.exe but I am not sure on the proper command line :

    C:\WINDOWS\system32>RUNDLL32.EXE SETUPAPI.DLL,InstallHinfSection COMPOSITEBUS\MS_IMPLAT_MP 132 c:\Windows\INF\ndisimplatformmp.inf
    C:\WINDOWS\system32>RUNDLL32.EXE SETUPAPI.DLL,InstallHinfSection NdisImPlatformMp.AddService 132 c:\Windows\INF\ndisimplatformmp.inf

    C:\WINDOWS\system32>RUNDLL32.EXE SETUPAPI.DLL,InstallHinfSection NdisImPlatformMp 132 c:\Windows\INF\ndisimplatformmp.inf

    Anybody with some insight ?

    In Windows 10 build 10240, where you can still have teaming, this driver is not used at all for teaming. So it is a new tech that they are building right now.

    In my opinion they should not have moved from the model that was in build 10240 until the new model was ready. Now the november update is killing a lot of goodwill among people.

    Lets hope that the summer update brings us better news, and until then I'm staying at build 10240.


    Thursday, April 14, 2016 8:05 AM
  • Any update?
    Monday, April 18, 2016 3:57 AM
  • Is this solved yet, getting bored with this... Bought a Intel quad card now cant use its full potential. 
    Tuesday, April 26, 2016 3:08 PM
  • Nope, not on the latest 14328 public Preview build I'm afraid. Tried it on that and still the same error.

    PS C:\Windows\system32> $PSVersionTable.PSVersion
    
    Major  Minor  Build  Revision
    -----  -----  -----  --------
    5      1      14328  1000
    
    
    PS C:\Windows\system32> New-NetLbfoTeam -TeamMembers Ether* -Name '2Gpbs Team'
    New-NetLbfoTeam : The LBFO feature is not currently enabled, or LBFO is not supported on this SKU.
    At line:1 char:1
    + New-NetLbfoTeam -TeamMembers Ether* -Name '2Gpbs Team'
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : NotSpecified: (MSFT_NetLbfoTeam:root/StandardCimv2/MSFT_NetLbfoTeam) [New-NetLbfoTeam],
       CimException
        + FullyQualifiedErrorId : MI RESULT 1,New-NetLbfoTeam



    • Edited by -Mr Happy- Wednesday, April 27, 2016 12:33 AM
    Wednesday, April 27, 2016 12:30 AM
  • on this intel link I found some good news:

    https\\communities.intel.com/message/388249#388249


    On April 15 Carl Wilson reported:

    We have good news!

    We have been testing the two Microsoft Hot-fixes (KB3140745 and KB3140743, depending on OS version) internally with our SW teams. 
    The fixes look good, so we are moving to intercept our next SW driver release (Network Adapter Driver package version 21.0) targeted for the beginning of June to re-enable the Teaming and VLAN capabilities! 
    This new driver will check to see if these hot-fixes are installed before allowing the settings to be changed. 
    If your system doesn't allow fro the teaming/VLAN settings, it is an indication you need to install the hot-fixes).

    Thursday, April 28, 2016 8:49 PM
  • on this intel link I found some good news:

    https\\communities.intel.com/message/388249#388249


    On April 15 Carl Wilson reported:

    We have good news!

    We have been testing the two Microsoft Hot-fixes (KB3140745 and KB3140743, depending on OS version) internally with our SW teams. 
    The fixes look good, so we are moving to intercept our next SW driver release (Network Adapter Driver package version 21.0) targeted for the beginning of June to re-enable the Teaming and VLAN capabilities! 
    This new driver will check to see if these hot-fixes are installed before allowing the settings to be changed. 
    If your system doesn't allow fro the teaming/VLAN settings, it is an indication you need to install the hot-fixes).


    Those are the Cumulative March update so they have not helped with the standard PowerShell teaming.
    Friday, April 29, 2016 12:52 PM
  • on this intel link I found some good news:

    https\\communities.intel.com/message/388249#388249


    On April 15 Carl Wilson reported:

    We have good news!

    We have been testing the two Microsoft Hot-fixes (KB3140745 and KB3140743, depending on OS version) internally with our SW teams. 
    The fixes look good, so we are moving to intercept our next SW driver release (Network Adapter Driver package version 21.0) targeted for the beginning of June to re-enable the Teaming and VLAN capabilities! 
    This new driver will check to see if these hot-fixes are installed before allowing the settings to be changed. 
    If your system doesn't allow fro the teaming/VLAN settings, it is an indication you need to install the hot-fixes).


    Those are the Cumulative March update so they have not helped with the standard PowerShell teaming.
    yes but the teaming feature will be reanabled with the intel driver coming in June. so the current KB's mentioned are the first side of the medal the coming intel driver in june will be the second...
    or do I miss something?
    • Edited by gkaefer Friday, April 29, 2016 4:41 PM
    Friday, April 29, 2016 4:40 PM
  • yes but the teaming feature will be reanabled with the intel driver coming in June. so the current KB's mentioned are the first side of the medal the coming intel driver in june will be the second...
    or do I miss something?

    Interesting news for Intel nic users so thanks for that. But I do not have Intel nics. In 10240 the July release can team my nics with PowerShell and New-NetLbfoTeam, failed since the November 10586 release. Failed in every Insider Release since, including the 14332 latest at the time of writing. So for people without Intel nics?


    • Edited by -Mr Happy- Friday, April 29, 2016 9:04 PM
    Friday, April 29, 2016 9:03 PM
  • 14342 latest Insider build, no teaming.

    Windows PowerShell
    Copyright (C) 2016 Microsoft Corporation. All rights reserved.
    
    PS C:\Windows\system32> $PSVersionTable.PSVersion
    
    Major  Minor  Build  Revision
    -----  -----  -----  --------
    5      1      14342  1000
    
    
    PS C:\Windows\system32> New-NetLbfoTeam -TeamMembers Ether* -Name '2Gpbs Team'
    New-NetLbfoTeam : The LBFO feature is not currently enabled, or LBFO is not supported on this SKU.
    At line:1 char:1
    + New-NetLbfoTeam -TeamMembers Ether* -Name '2Gpbs Team'
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : NotSpecified: (MSFT_NetLbfoTeam:root/StandardCimv2/MSFT_NetLbfoTeam) [New-NetLbfoTeam],
       CimException
        + FullyQualifiedErrorId : MI RESULT 1,New-NetLbfoTeam
    
    PS C:\Windows\system32> Get-NetAdapter
    
    Name                      InterfaceDescription                    ifIndex Status       MacAddress             LinkSpee
    ----                      --------------------                    ------- ------       ----------             --------
    Ethernet                  Microsoft Hyper-V Network Adapter             5 Up           00-15-5D-01-67-0A         1 Gbp
    Ethernet 2                Microsoft Hyper-V Network Adapter #2          6 Up           00-15-5D-01-67-00         1 Gbp
    
    
    PS C:\Windows\system32>


    • Edited by -Mr Happy- Wednesday, May 11, 2016 10:37 PM
    Wednesday, May 11, 2016 10:36 PM
  • Microsoft givith, Microsoft taketh away!
    Friday, May 20, 2016 8:43 PM
  • Tested on 14352 (this weeks Insider build) same error.

    Windows PowerShell
    Copyright (C) 2016 Microsoft Corporation. All rights reserved.
    
    PS C:\Windows\system32> $PSVersionTable.PSVersion
    
    Major  Minor  Build  Revision
    -----  -----  -----  --------
    5      1      14352  1002
    
    
    PS C:\Windows\system32> New-NetLbfoTeam -TeamMembers Ether* -Name '2Gpbs Team'
    New-NetLbfoTeam : The LBFO feature is not currently enabled, or LBFO is not supported on this SKU.
    At line:1 char:1
    + New-NetLbfoTeam -TeamMembers Ether* -Name '2Gpbs Team'
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : NotSpecified: (MSFT_NetLbfoTeam:root/StandardCimv2/MSFT_NetLbfoTeam) [New-NetLbfoTeam],
       CimException
        + FullyQualifiedErrorId : MI RESULT 1,New-NetLbfoTeam
    
    PS C:\Windows\system32>
    
    

    Saturday, May 28, 2016 4:00 PM
  • For the moment NIC Teaming is still broken. :-( Broken voor 7 months now....

    Microsoft unlocked a achievement:
    - Failure in full view
    :'(

    Anyone found a fix, workaround? MS failed to do the job apparently.....
    Wednesday, June 1, 2016 8:47 PM
  • For the moment NIC Teaming is still broken. :-( Broken voor 7 months now....

    Microsoft unlocked a achievement:
    - Failure in full view
    :'(

    Anyone found a fix, workaround? MS failed to do the job apparently.....

    regarding Intel drivers: Carl Wilson replied on this thread on 26.5.2016:

    "Unfortunately, after a full test and validation run, it was determined that the hot fixes introduced new issues that prevented VLAN/teaming support from being re-enabled in this release.  I have escalated to the SW development team for a plan and point release.  As soon as I have more details I will provide it."


    source: thread 77934 on communities dot intel dot com (sorry still not allowed to paste links even my profile is verified with LinkedIn...)

    • Edited by gkaefer Sunday, June 5, 2016 7:14 AM
    Sunday, June 5, 2016 7:11 AM
  • And once again, MS screws the pooch.  This time we're the pooch.  This has been a known issue for far too long.  Several patch Tuesday's under the hood and no resolution, nor further acknowledgement, is embarrassing.  Just because most of us got this POS for free, doesn't mean we shouldn't have a voice and the ability to demand they fix what's broken.  Had it never been there, that would be one thing, but to take it away with an "update" is just ridiculous.
    Tuesday, June 7, 2016 5:22 AM
  • This is just ridiculous! Come on MS we need something from you guys on this! There should be no reason why it takes almost 2 years to fix a CRITICAL feature. situations like this is why you guys are losing market share to Unix/linux competitors. 
    Saturday, June 18, 2016 9:14 AM
  • +1

    This is annoying.

    Saturday, June 18, 2016 10:55 AM
  • I do try teaming in the Windows 10 TP builds when they come out, hoping one day to see it work. Alas not yet, tried on the latest at this time 14367 still same 'The LBFO feature is not currently enabled, or LBFO is not supported on this SKU' error.
    Saturday, June 18, 2016 7:34 PM
  • It's a shame they don't manage to re-include this feature. C'mon Microsoft!
    Wednesday, June 22, 2016 8:37 AM
  • At a minimum a clear response would be nice.  Is this considered a defect or have they decided that Windows 10 does not support nic teaming.

    I'm pretty sure my Intel i350's are on intel's list for release in August (fingers crossed) but it is annoying when MSFT can't answer a straight question.

    Friday, July 1, 2016 4:33 AM
  • Has anyone tried Server 2016? Doesn't it use the same codebase? If teaming works there, then either MS will limit it to Server OS or there is a small light at the end of a long tunnel.

    Friday, July 1, 2016 3:34 PM
  • Has anyone tried Server 2016? Doesn't it use the same codebase? If teaming works there, then either MS will limit it to Server OS or there is a small light at the end of a long tunnel.

    Server 2016 TP5 works fine (EDIT icon in taskbar shows network disconnected, but it works fine). Setup team with PowerShell simple command, then shows in Server Manager

    THIS IS SERVER 2016

    PS C:\Windows\system32> $PSVersionTable.PSVersion
    
    Major  Minor  Build  Revision
    -----  -----  -----  --------
    5      1      14300  1000
    
    
    PS C:\Windows\system32> New-NetLbfoTeam -TeamMembers Ether* -Name '2Gpbs Team'
    
    Confirm
    Are you sure you want to perform this action?
    Creates Team:'2Gpbs Team' with TeamMembers:{'Ethernet 2', 'Ethernet'}, TeamNicName:'2Gpbs Team',
    TeamingMode:'SwitchIndependent' and LoadBalancingAlgorithm:'TransportPorts'.
    [Y] Yes  [A] Yes to All  [N] No  [L] No to All  [S] Suspend  [?] Help (default is "Y"): Y
    
    
    Name                   : 2Gpbs Team
    Members                : {Ethernet 2, Ethernet}
    TeamNics               : 2Gpbs Team
    TeamingMode            : SwitchIndependent
    LoadBalancingAlgorithm : TransportPorts
    Status                 : Down
    
    
    
    PS C:\Windows\system32>


    • Edited by -Mr Happy- Friday, July 1, 2016 5:59 PM
    Friday, July 1, 2016 5:52 PM
  • Windows 10 TP 14379 latest Insider Preview at this time, no go.

    PS C:\Windows\system32> $PSVersionTable.PSVersion
    
    Major  Minor  Build  Revision
    -----  -----  -----  --------
    5      1      14379  0
    
    
    PS C:\Windows\system32> New-NetLbfoTeam -TeamMembers Ether* -Name '2Gpbs Team'
    New-NetLbfoTeam : The LBFO feature is not currently enabled, or LBFO is not supported on this SKU.
    At line:1 char:1
    + New-NetLbfoTeam -TeamMembers Ether* -Name '2Gpbs Team'
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : NotSpecified: (MSFT_NetLbfoTeam:root/StandardCimv2/MSFT_NetLbfoTeam) [New-NetLbfoTeam],
       CimException
        + FullyQualifiedErrorId : MI RESULT 1,New-NetLbfoTeam

    Friday, July 1, 2016 9:16 PM
  • With the Build 14383 on August 2nd, this bug will it be resolved ?
    • Edited by JeromeC-FR Friday, July 8, 2016 11:32 AM
    Friday, July 8, 2016 11:30 AM
  • 14383 Threshold release? discussion (started by me) and has a note from the release saying "But we’re not finished yet and will have more builds to release to Windows Insiders between now and then"

    On 14383 no go

    Windows PowerShell
    Copyright (C) 2016 Microsoft Corporation. All rights reserved.
    
    PS C:\Windows\system32> $PSVersionTable.PSVersion
    
    Major  Minor  Build  Revision
    -----  -----  -----  --------
    5      1      14383  0
    
    
    PS C:\Windows\system32> New-NetLbfoTeam -TeamMembers Ether* -Name '2Gpbs Team'
    New-NetLbfoTeam : The LBFO feature is not currently enabled, or LBFO is not supported on this SKU.
    At line:1 char:1
    + New-NetLbfoTeam -TeamMembers Ether* -Name '2Gpbs Team'
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : NotSpecified: (MSFT_NetLbfoTeam:root/StandardCimv2/MSFT_NetLbfoTeam) [New-NetLbfoTeam],
       CimException
        + FullyQualifiedErrorId : MI RESULT 1,New-NetLbfoTeam

    Friday, July 8, 2016 6:17 PM
  • Still not working on the latest insider build 14393.0.. such a shame MS.. please fix the network stuff.
    Friday, July 22, 2016 3:25 PM
  • Hello Microsoft.

    Do Microsoft draw breath????

    Friday, July 22, 2016 7:19 PM
  • Hello Microsoft.

    Do Microsoft draw breath????

    +1


    Monday, July 25, 2016 4:26 PM
  • Still Nothing.
    Monday, July 25, 2016 4:51 PM
  • Not working in Redstone build 14393.3 Win 10 Enterprise.

    Looks like this is a no go. Have to wait for Intel to get their act together. Don't hold your breath. Been 8 months waiting on them too.

    Next major release, Redstone 2, will be spring 2017. Doubt teaming will be there either. I gave up on MS.


    Monday, July 25, 2016 11:33 PM
  • no. I have that build and still no-go. Next major release will be spring 2017
    Monday, July 25, 2016 11:47 PM
  • You would expect the Enterprise version would have teaming. Not much of an Enterprise version if you ask me. You know they have the code. Not sure why even Enterprise commercial customers can't get it either?
    Monday, July 25, 2016 11:54 PM
  • You would expect the Enterprise version would have teaming. Not much of an Enterprise version if you ask me. You know they have the code. Not sure why even Enterprise commercial customers can't get it either?
    So basiclly we have to roll back to windows 8 thanks ms
    Thursday, July 28, 2016 8:59 PM
  • Just to save everyone checking its still broken in the latest release on MSDN Windows 10 Enterprise, Version 1511 (Updated Apr 2016)

    What a sodding joke, "Lots of great features to get excited about" (Except the one we stole from you Nic Teaming)

    I'm surprised the people responsible still have their heads never mind their jobs.



    Tuesday, August 2, 2016 12:29 PM
  • And with the anniversary release today.... it's still broken... same error.

    Tuesday, August 2, 2016 10:09 PM
  • Seriously considering rolling back to win8 with good old Classic Shell Start Menu. I really like win10 better, so you can imagine how sad I am to make this move. However, I can't run my stuff without VLAN and Teaming capability. Or maybe I should just get back to build 10240 and cut Windows update. It will suck to run an outdate system, but this is the price you pay.
    Monday, August 8, 2016 8:19 PM
  • Teaming works in the current 10204 Enterprise LTSB build. 10240 being the key I guess. Be interesting what happens with a talked about update for that in October.
    Monday, August 8, 2016 9:23 PM
  • Since Microsoft sems to remove more and configurations capabilities from the Pro - version (eg.: some GPOs are no longer working, registry settings keep reverting to standard settings) it gets more and more plausible that NIC teaming will never return to Win10 Pro.

    This would fit Microsoft's tendency to get business users to change to the enterprise version (subscription basis) by "castrating" all other versions (even the domain capable Pro version).
    Tuesday, August 9, 2016 10:10 AM
  • It only works in the LTSB because it hasn't been updated when they do update it will remove this feature. So its not a solution at all.

    Even in the regular Enterprise version its missing.
    Tuesday, August 9, 2016 5:48 PM
  • Did you try using bcdedit to enter testsigning mode? That might allow the driver to be installed. You can then turn off testsigning mode again.
    Saturday, August 13, 2016 12:59 PM
  • Did you try using bcdedit to enter testsigning mode? That might allow the driver to be installed. You can then turn off testsigning mode again.

    I did try this it did not work. As I am using the PowerShell command and no drivers other than what is in use that Windows installed, I do not see how this could help.

    Saturday, August 13, 2016 2:43 PM
  • Tried on the latest Insider Build, 14901 same error.

    Windows PowerShell
    Copyright (C) 2016 Microsoft Corporation. All rights reserved.
    
    PS C:\Windows\system32> $PSVersionTable.PSVersion
    
    Major  Minor  Build  Revision
    -----  -----  -----  --------
    5      1      14901  1000
    
    
    PS C:\Windows\system32> New-NetLbfoTeam -TeamMembers Ether* -Name '2Gpbs Team'
    New-NetLbfoTeam : The LBFO feature is not currently enabled, or LBFO is not supported on this SKU.
    At line:1 char:1
    + New-NetLbfoTeam -TeamMembers Ether* -Name '2Gpbs Team'
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : NotSpecified: (MSFT_NetLbfoTeam:root/StandardCimv2/MSFT_NetLbfoTeam) [New-NetLbfoTeam],
       CimException
        + FullyQualifiedErrorId : MI RESULT 1,New-NetLbfoTeam
    
    PS C:\Windows\system32>

    Saturday, August 13, 2016 2:48 PM
  • latest build 14905,1000 (08/19) doesn't work yet.

    Saturday, August 20, 2016 9:51 AM
  • Just when you think it cant get worse... It does.

    Not even the LTSB is safe, en_windows_10_enterprise_2016_ltsb_x64_dvd_9059483.iso has the feature removed!

    What this means is that if you have this in place on the LTSB which "Enables long-term deployment of selected Windows 10 releases in low-change configurations" after the update you'll lose these features.

    This is a complete let down even to the enterprise users.

    "For specialized devices, Windows 10 Enterprise Long Term Servicing Branch (LTSB) ISO images will be made available. These are expected to be on a variable schedule, less often than CB and CBB releases. Once released, these will be supported with security and reliability fixes for an extended period; no new features will be added over its servicing lifetime"

    Well I guess they never said now features would be removed in its servicing lifetime.

    I don't buy the claim that its a technical problem either because they removed the generic error 87 with "this feature is not available in your sku"

    This is completely pathetic and will cause a real headache when users come in on Monday to find their networking ****ed!

    Tuesday, August 23, 2016 1:54 PM
  • As predicted

    Not even the LTSB is safe, en_windows_10_enterprise_2016_ltsb_x64_dvd_9059483.iso has the feature removed!

    What this means is that if you have this in place on the LTSB which "Enables long-term deployment of selected Windows 10 releases in low-change configurations" after the update you'll lose these features.

    This is a complete let down even to the enterprise users.

    "For specialized devices, Windows 10 Enterprise Long Term Servicing Branch (LTSB) ISO images will be made available. These are expected to be on a variable schedule, less often than CB and CBB releases. Once released, these will be supported with security and reliability fixes for an extended period; no new features will be added over its servicing lifetime"

    Well I guess they never said now features would be removed in its servicing lifetime.

    Tuesday, August 23, 2016 2:05 PM
  • Start looking for a new OS...

    From the Intel Forum on the same subject:

    "

    Wow... I've engaged Microsoft through a Premier support request and I am absolutely, 100% satisfied, that it's Microsoft who is stonewalling this. No question about it.

     

    It would probably be inappropriate for me to copy any paste directly what I was privy to, but suffice it to say if there was a "bug" in Windows 10 it's not that native LBFO has stopped working... The bug, in Microsoft's view, was that native LBFO wasever working in the first place, and Microsoft "fixed the bug" by *really* breaking it in subsequent releases / updates to Windows 10.

     

    The door was left open for "third party" developers to have LBFO support via their utilities, such as Intel ANS, and that Microsoft would provide "developer support" to troubleshoot issues they run into... But the vibe I got reading between the lines from what I was seeing from support via copy / pastes of E-Mails from the Product Groups involved was that "if you want LBFO, use Server SKUs". It's NOT (and they actually used capital letters for emphasis there) supported in client SKUs - and if it ever worked natively in Windows 10 for a short time that was unintentional and absolutely not by design.

     

    So, looks like we can pretty much kiss Windows 10 "native" LBFO goodbye, unless they have some massive change of heart. So the only hope, if Intel keeps on it, is that it may eventually work out with ANS. But probably not because Microsoft wants it to... More like because they feel like, as good development partners, they "have to".

     

    Kind of like a kid being told he needs to eat his peas. He doesn't like it, he'll grit his teeth and do it, and it might take him 3 hours to finish dinner.

     

     

    Pretty blown away by the response from Microsoft, to be honest. I'm challenging it and telling our contacts that, basically, the decision is crap. So we'll see if my little voice in this has any impact at all (not holding my breath).

     

    But, yeah, it's Microsoft on this one. No doubt about it.

     

     

    PS: Sorry, Carl, I just saw a little bit of the hell you guys are going through. Keep up the good fight!"

    Looks like M$ is doing everything they can to get rid of their desktop users and focus solely on their Surface people. Sad. Go too big for themselves and now instead of being responsive, truly innovative and for the "masses", they have gone the way of government... 

    Sunday, August 28, 2016 12:35 AM
  • 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

    Hello Adam.

    I note that your post was from November 2015 - almost a year ago. What's happening with this ? It's still broken even in the current builds !

    Monday, August 29, 2016 5:55 AM
  • Well after all these comments, i think it is safe to conclude that Microsoft is not going to solve the NIC teaming (bug?) in the future. It is broken for 10 months now. (Probably to make it a enterprise (server) option, just to make some $$). It is a shame that a basic option like this is not supported by default. Well i changed the solution to a UNIX o/s. No problem there.
    Tuesday, August 30, 2016 1:32 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
  • There are no native LBFO capabilities on Win10. Microsoft does not support client SKU network teaming.

    [...]

    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.

    OK, teaming is one thing; and I'm not exactly of the opinion that there are no client workloads that can effectively take advantage of teaming, and did so in previous Windows versions. But let's leave that aside.

    There is another part of the functionality that is apparently intricately linked to the teaming feature in all vendors' drivers, which is creating VLANs. No matter what the support statement is for teaming, there is no way Microsoft can claim that users of client SKUs should not be allowed to create VLAN interfaces. There are plenty of situations where, say, IT staff have to be able to connect to various network segments around the organization that is easiest done using VLAN interfaces. Telling those people (and me) that running 2016 on the desktop is the way to go there does not really sound realistic, or indeed sane.

    So: Keep teaming to the server, if you want, it's not an essential thing as far as I'm concerned. But I want my VLANs back.

    Tuesday, September 6, 2016 6:51 PM
  • Adam,

    Can you please comment on how Microsoft is assisting Intel with a developer support request for assisting them in troubleshooting issues with their ANS software on Windows 10? This is a third party utility that Intel produces which provides an option for Microsoft and Intel customers who require VLAN and LBFO capability to Windows Client SKUs.

    To be clear, this third-party solution has been working, just fine, under Windows 7. This third-party solution has not been working under Windows 10 (at least in terms of VLAN and LBFO features).

    There is a very lengthy discussion going on in the Intel support forums (https://communities.intel.com/thread/77934) where one of the latest updates from Intel's Carl Wilson stated the following:

    "...There are fundamental issues with miniport driver configuration/setup that will not allow for a successful configuration in certain circumstances.  We are confident that our driver configuration is behaving properly, since the failures we are seeing in validation are OS specific in nature.  The issue we are experiencing may or may not be seen by other vendors, depending on the thoroughness of their testing environments.  However due to the nature of our extensive testing/validation - what we are seeing is more than likely not vendor specific since the failures are not related to anything we are doing in our driver code, but core networking stack functions.

    We are continuing to provide assistance to Microsoft networking team to debug this issue.  If there is a resolution that comes from Microsoft that allows us to re-enable the feature in our driver, we will release a point release so our customers can finally take advantage of these features again.  My recommendation is for our customers to escalate to the Windows 10 support team as well..."

    and the more technical note:


    "...The failure is related to setup/tear-down of the required miniport driver that allows teaming and multiple VLANs to function.  This setup/teardown is 100% in the domain of the core OS.  In most cases, this works fine (say ~90% of the time).  So, as the Product Marketing guy, my first response would be 'well that's fine, lets enable it and then document how to manually work around the 10% of the time it fails'.  That sounds reasonable and happens often while in the process of debugging a full fix is ongoing.  Trust me, this was the first statement I made to our software development team.
     
    So - what would keep me from pushing down that path?  The one work around that is not acceptable.  In the ~10% of the time the teardown fails, it requires a complete OS reinstall to correct.  <At this point in my engineering conversation is where I exhaled slowly, whispering words normally banned from workplace lexicon>.  We have explored all options - and this is the only one that puts it back into its original state.  This, as you can imagine, is not acceptable.  I can't image 'hey, that is a reasonable fix!' is a response I would expect to hear from anyone.  Thus the reason to not enable it in the 21.1 release.
     
    That's about as transparent as I can get.
     
    I normally don't get involved in Community posts.  I respond on this thread because this is an important feature for me personally, and an important feature for our customers.  I'm the guy standing in the cubicles of the engineers who work on this code and getting answers from the management team on exactly what is going on. This team shares my passion and commitment to the feature."


    Can you please also comment on these updates from Intel, Adam?

    You'll have to pardon the community members, both here and on Intel's site, who can't help but think "man, it's been almost a year and Intel and Microsoft can't seem to figure out how to get these bugs resolved... what's the deal?".

    With all due respect, many of us are starting to wonder if Microsoft is back burnering this developer support request from Intel. I for one sincerely hope that's not the case, but after nearly a year of Intel seemingly working with Microsoft in a developer support arrangement, it's hard not to wonder if that's what's going on.

    I would appreciate your thoughts and comments and also some guidance on the general expectations the community should have for this important issue for many Microsoft customers.

    Thanks Adam for your time.

    Tuesday, September 6, 2016 8:37 PM
  • I can go into some detail, however not much due to confidentially.

    I can confirm we we are working closely with Intel in regards to issues they have encountered with their ANS software that enables VLAN tagging and NIC teaming. My understanding after discussion with the product group last week is that all the outstanding issues that had been filed with us have been resolved at this time and we are waiting to hear back further regarding testing/validation to ensure no other bugs are blocking Intel regarding their ANS solution.

    I hope this helps.


    Adam Rudell | Windows Networking Beta | Microsoft Corporation


    Wednesday, September 7, 2016 6:10 PM
  • Hi Adam,

    Thank you very much for this info. If this is indeed the case, we'll look toward Intel for the next update and very much appreciate Microsoft working with Intel to troubleshoot these remaining issues (and, of course, any new ones they find as they complete their testing/validation).

    Cheers!


    Wednesday, September 7, 2016 9:10 PM
  • Eagerly waiting for the fix.

    Atique

    Thursday, September 8, 2016 5:31 AM
  • Hi Adam,


    Per Carl Wilson at Intel (https://communities.intel.com/message/420212#420212):

    The good news.  I've checked with the Windows driver development team here.  The comment from Adam (MS Networking Beta) is accurate.  I can confirm that our testing with the latest RS2 Beta shows no blocking issues with Teaming and VLAN setup/tear-down with our existing driver (internally enabled for testing of the features).  Therefore, once RS2 is released it can be re-enabled for that Windows release.

     

    The not as good news, it doesn't help with the existing releases.  We are working with MS to determine if there is something they can do to help re-enable the capability in the current shipping releases.  If there is a patch to the OS that applies the RS2 changes to the previous releases, we can do a very fast point release since only the driver needs to code changes (only turning the capability back on).



    What are your thoughts on this?


    Friday, September 9, 2016 8:42 PM
  • Working with the PG as well from my end to see if we can get the fixes ported to the previous builds. I will keep you posted on any updates.

    Adam Rudell | Windows Networking Beta | Microsoft Corporation


    Tuesday, September 13, 2016 9:02 PM
  • Thank you Adam, looking forward to the update on this.
    Wednesday, September 14, 2016 7:16 PM
  • Working with the PG as well from my end to see if we can get the fixes ported to the previous builds. I will keep you posted on any updates.

    Adam Rudell | Windows Networking Beta | Microsoft Corporation


    @Arudell, @adam:

    This is a major issue affecting IT consumers of your Windows 10 client operating system. There is extensive discussion and interest on Intel's forums on this issue. I'm surprised this hasn't taken a higher priority at MSFT. For example, as someone who loves Linux, I was very pleased to see Bash for Windows roll out. However, this tip of the cap to your IT client base should have come after getting the very basics ironed out, such as fixing VLAN compatibility with your largest hardware vendor, Intel. Layer 2 VLAN support is a very basic function, but an important one to anyone having to communicate directly with multiple VLANs through a single, or multiple, NIC adapter/s. There are countless examples where this functionality is absolutily required, particlarly with third-party virtualization.

    That said, this should be an escalated trouble ticket, as this problem has been unresolved for far too long. Please continue to provide updates on the corrective actions going forward to remedy this ongoing issue. 

    Wednesday, September 21, 2016 5:14 PM
  • MSFT says NIC teaming is a server only feature that is not supported on client SKUs
    Friday, September 23, 2016 6:34 PM
  • Any movement on this ?

    I've recently upgraded my networking infrastructure, and it will be for naught if I can't get LACP going. Please don't make me revert to Windows 8.1, or even Linux ...

    Sunday, September 25, 2016 8:31 AM
  • Super! 
    I've been following the intel forums for about a year on this issue.
    Waiting eagerly for updates on this topic.

    I really hope you can port this to earlier builds! Have to wait for RS2 on my workstations if not.
    • Edited by JKJK Wednesday, September 28, 2016 10:18 PM
    Wednesday, September 28, 2016 12:12 PM
  • MSFT says NIC teaming is a server only feature that is not supported on client SKUs

    I've read SO much, and still haven't understood whether or not NIC Teaming will be provided for Windows 10 or not!

    I have spent a SHIT TON of hard-earned Canadian cash money trying to get a 2GB connection

    ~$400.00 for an ASUS RT-AC88U router, which says you combine ports 1 & 2 to get (almost) 2GB

    ~ $150.00 StartTech ST1000SPEXD3 2-port Gigabit NIC

    Still nothing, and I'm pissed!

    ASUS customer support sent me instructions that do not appear to be Windows 10 Control Panel screenshots, and what on earth does "Synology NAS interface" have to do with an ASUS router?:

    (*Please do not change the subject line when you reply to this email)

    Dear Don Leverton,

    Thank you for contacting ASUS Customer Service.

    My name is Prem J. and  I understand that you are would like to configure Link Aggregation.

    Please refer to the guideline steps . 

    Details can be found below: 

    To enable the function, users will first have to enable the feature (must be supported within their NAS system).

    For example on Synology NAS interface (referenced from www.synology.com):

     

    To combine multiple LANs with Link Aggregation:

    1. Go to Control Panel > Network > Network Interface. Click Create > Create Bond.

     

    2. Select IEEE 802.3ad Dynamic Link Aggregation

     

     

     

    3. Select the interfaces to create Link Aggregation.

     

     

    4. Configure the IP settings. You can also enable VLAN if necessary. Click Apply to complete the setup.

     

     

    5. Once finished, you can see the new interface named Bond 1 in the Network Interface list.

     

     



    • Edited by Don Leverton Saturday, October 1, 2016 10:09 PM added "NIC"
    Saturday, October 1, 2016 10:08 PM
  • Thanks for the update, just wondering why this is this so hard to fix? what's the technology issue?
    Sunday, October 2, 2016 1:46 PM
  • The issue is that, Microsoft, in it's quest to secure as much money for itself as possible, took steps to remove NIC teaming and VLAN support from its client operating systems, and move it to server SKUs (despite the fact that some client OS versions have Hyper-V support). However, apparently Microsoft either failed to consider, or adequately respond once discovered, that their efforts have also disabled third-party VLAN and NIC teaming support, despite its largest hardware supplier, Intel, having promised that this feature would be available in future driver releases. However, driver releases will not fix the issue, as Microsoft has to take steps to allow VLAN tagging and NIC teaming back in their client OS before this will happen. Despite promises to the contrary, after more than a year of broken promises, hope is fading that this will ever become a reality, as Microsoft appears to be fighting to maintain that support exclusively for its server SKUs. 
    Monday, October 3, 2016 5:00 PM
  • MS should, at least, enable teaming in their enterprise version. Sort of makes the Enterprise version of Windows 10 a waste of money. If they enabled teaming in that version, their sales may actually go up. So I don't see why it would be a money issue. I just don't think they have the current staff that is capable of making it work. They must have found something and no one knows how to fix it. That sounds more like MS to me.
    Tuesday, October 4, 2016 4:48 PM
  • The Windows 10 client OS doesn't support teaming. Teaming may be enabled on Windows 10 client SKUs by 3rd parties at which point the solution is supported by the 3rd party. Intel is an example of a company doing this work.
    Thursday, October 13, 2016 3:36 PM
  • The issue is that there apparently needs to be some collaboration between MS and Intel as expressed in the Intel forum on the same subject. I can't tell who's waiting on who since info is sparse on this subject from both parties. Also, since teaming worked on previous OS's there is no explanation from MS as to why they decided to eliminate a feature that people were using in those OS's. If MS decides they are eliminating a feature, then explain why. Removing this feature contradicts their backward compatibility stance on Windows 10.



    • Edited by dalicollins Saturday, October 15, 2016 5:55 PM
    Saturday, October 15, 2016 5:50 PM
  • Let's clear the air here on a few things, as having been someone who has had a bit more knowledge than the average user on this.

    As far as my credentials (so to speak) on this issue, I have Microsoft Premier account through work and actually went so far as to log a support ticket that got me more direct responses from "the horses mouth" as to what's going on from Microsoft's side. I also have spoken directly with Carl Wilson, the program manager at Intel who oversees the Intel ANS software. So, to be clear, I don't work for either Intel or MS, but have taken the initiative to have as low-level conversations with them as I can. Here is the summation of what I've found:

    - To be clear, Microsoft has *never* officially supported the use of the New-NetLbfoTeam command on non-server OSes. This command *never* worked in Windows 7, Windows 8/8.1, nor Windows 10. There was a brief time when it appeared to work in early builds of Windows 10, but when Microsoft was pressed on this point issue they admitted that there was (their words) "a bug" in early builds of Windows 10 (prior to build 1511, if memory serves) where the command would in fact return without error... but... if you ran a packet trace you'd find that the team was not actually functional. So, there was a brief period between Windows 10 RTM and built 1511 where there was a surface-level "appearance" of a team being built via the New-NetLbfoTeam command, but it was *NEVER* actually built, nor was it ever actually functional.

    - Intel has offered third-party support for LBFO and VLAN support via it's ANS software for some time. The Intel ANS software has worked with Windows 7, Windows 8/8.1, and continues to work with Windows 10 (wait for it...). On Windows 7, Windows 8/8.1 that software is feature-complete, fully functional. On Windows 10, however, Intel has found that due to underlying code changes to the core networking stack within Windows 10, they were forced to disable all LBFO and VLAN features within their driver due to instability issues. These instability issues are inconsistant (i.e., not 100%) but for obvious reasons, Intel didn't want to release a product that causes other issues. One of the issues Intel identified is that when a failure does occur as a result of ANS with LBFO / VLAN features enabled, on Windows 10, the only recourse is a full OS reinstall to recover. That's disasterous enough that Intel wasn't willing to release the feature-set, on a wide scale, and have hundreds or thousands of customers unknowingly bricking their machines as a result of simply installing / running Intel ANS. That's a crappy situation, but in my view it's the right call for Intel to make, given the tough circumstances.

    - Intel has had an open dialog with Microsoft on this issue (Microsoft provides "developer support" for third-party developer partners, like Intel, where they will assist in troubleshooting issues found with the Microsoft OS as a result of third-party app development, like Intel ANS). Microsoft has apparently been able to resolve these issues, based on Intel's latest tests, but those fixes aren't scheduled to be included in Windows 10 until the "Redstone 2" release (last I heard, sometime in late Q1 or Q2 of 2017).

    - Intel's Carl Wilson, who comments on this from time to time on the Intel Forum (https://communities.intel.com/thread/77934?start=270&tstart=0) was going to see if Microsoft would be willing to back-port these fixes into a patch roll-up between now and the release of Windows 10 / Redstone 2. So far, we've not heard back on that (it's been a bit more than a month).

    So, to recap: It's unfair to say that Microsoft supported native (i.e., built-into-the-OS) LBFO on Windows 7/8/8.1, so therefore it should be supported on Windows 10 as well. They never did. Third party utilities, such as Intel ANS, Realtek, etc, had ways to make this work on client OSes. Microsoft made things a bit more confusing by given the "appearance" that the command was suddenly supported on a non-Server SKU in early Windows 10 builds, but it never actually worked. Furthermore, Microsoft also made underlying networking stack changes that broke Intel's ability to support the feature via their third-party ANS software. After this was discovered (many months ago) Intel has been working with Microsoft on this issue and between the two of them have gotten a fix that *should* be released with Windows 10 Redstone 2. Intel would like it back-ported, but it's unclear if that will or won't happen (Microsoft's choice on if they will or won't do that).

    Has this issue taken way longer than any of us would want to have fixed: Yes. Is there any clear indication at this point in time if this will be fixed anytime soon (i.e., weeks or months): No.

    PS: All that is left for Intel it seems is to make a small tweak (what they refer to as a "point release") to their ANS Software to enable LBFO / VLAN support as soon as Microsoft releases Redstone 2 (or, presumably, if Microsoft back-ports a patch to existing Windows 10 builds).

    Anyway, I hope that helps fill in the gaps and clear out some of the FUD out there.

    Adam (ARUDELL with MSFT),

    Please feel free to correct anything I miss-stated. Also feel free to give us an update on if Microsoft is going to back-port the fix that Intel said you guys came up with in RS2, back to the current Windows 10 builds out right now.

    Joey


    Friday, October 21, 2016 12:30 AM
  • Good news on the Intel front:

    Sorry for the delay.

     

    So a quick update (with at least one more to come).

     

    With regard to Teaming and VLANS, we now know 2 things. 

     

    1) We will 100% be able to re-enable teaming and VLANs within our drivers for Windows 10 the with RS2 release from Microsoft when it ships.  We have confirmed the RS2 changes do in fact allow expected behaviors for teaming and VLAN configuration.  This I believe I have already made a note of before, but we are confirmed a 'go' for the official RS2 release.

     

    2)  This leave previous releases.  Happily, we are in the process of testing a MS provided beta fix for RS1 that is looking very, very good.  I should know by 10/21 or 10/24 how the full regression test passes are going.  If this passes, we will provide the feedback to MS that it is also a go and then two more things can happen.

         a) MS will incorporate the fix into a future RS1 monthly patch (which I will let you know when I know).

         b) We will 're-enable' out current driver (with a small step added which checks for version/patches to confirm the fix is loaded).  We already have the      team standing by to do an out-of-cycle release just for Windows 10 to make this happen.

     

    This probably means that TH1./TH2 will still not have the capability, but I am pretty sure that RS1/RS2 will be the broad deployment moving forward.

     

    I'll keep you posted!!

     

    - Carl

    Source: https://communities.intel.com/thread/77934?start=300&tstart=0

    Saturday, October 22, 2016 12:16 AM
  • Don't hold your breath, Looks like a 3-6 month wait according to Carl Wilson. With a lot of if's in there. Just release the drivers already. Redstone has been out there for months. The current release,19455, seems to be very stable with all the major issues resolved.

    Let's firm down what I meant by major issues. These are issues which affect 50% or more of the community. Does not include hardware specific issues. You will never achieve 100% working with an open architecture operating system. Too many variables.

    Monday, October 31, 2016 5:47 PM
  • The feature never existed in Windows 10 LTSB as it never included the mslbfoprovider.sys driver that provides the functionality. There was a code defect though that allowed New-NetLbfoTeam to be run on Windows 10 making it appear like a NIC team was being created, but it had no underlying functionality.

    Adam Rudell | Windows Networking Beta | Microsoft Corporation

    Wednesday, November 16, 2016 4:51 PM
  • What is the ETA now, over a year later, please?


    --------------------------------- ...ich bin der Jäger des Mondes, bis der Morgen erwacht!

    Wednesday, November 30, 2016 1:56 PM
  • If it never existed in Windows 10, why does Technet list Windows 10 alongside Windows Sever 2016 for all *-NetLbfoTeam commandlets ?
    Tuesday, December 20, 2016 12:44 AM
  • If it never existed in Windows 10, why does Technet list Windows 10 alongside Windows Sever 2016 for all *-NetLbfoTeam commandlets ?

    I agree.
    It sais it is available on Windows 10 and Windows Server 2016 in MSDN:
    https://technet.microsoft.com/en-us/library/jj130847.aspx?f=255&MSPPError=-2147217396

    But it is not Working. I just tried it on Windows 10 Pro

    Monday, January 23, 2017 5:16 PM
  • What is the ETA now, over a year later, please?



    I'd also like to have a current status. Really waiting for this ... 

    I don't want to go back to Win8/7

    Wednesday, January 25, 2017 7:39 AM
  • would love an update on this..  teaming on client SKUs is almost at a mandatory state.. 10Gb/s gear is too expensive to upgrade for most of my clients

    Monday, January 30, 2017 9:17 AM
  • Thas why i use macos hackintoshes to my clients.
    Thursday, February 9, 2017 12:37 AM

  • New-NetLbfoTeam

    Windows Server 2016 and Windows 10

    https://technet.microsoft.com/en-us/library/jj130847.aspx

    Monday, February 13, 2017 4:58 PM
  • HELLO MICROSOFT! FIX IT MICROSOFT! FOR GOD'S SAKE!

    What are the engineers getting paid for over at Microsoft? To stare at their computers all day and do nothing? It's preposterous that VLAN's & Teaming are still not working in LTSB 1607 (14393.726). 


    • Edited by Rick Tyler Tuesday, February 14, 2017 12:14 AM
    Tuesday, February 14, 2017 12:11 AM

  • New-NetLbfoTeam

    Windows Server 2016 and Windows 10

    https://technet.microsoft.com/en-us/library/jj130847.aspx

    Seems they are making it very clear that a home user that wants this feature must return back to windows 7

    This is very sad,  my NAS has 4 teamed network connections to my switch and in windows 7 had no problems doing this with very good results. Now I have no real options.  I would think the way video and other stuff is going on teaming a few 1Gb connection is the only option for a home user as 10Gb is still out of reach.

      I would like to hear what they suggest as a solution is to this challenge of moving large data around your network?

    • Proposed as answer by RogerAMoe Thursday, February 23, 2017 5:44 AM
    • Unproposed as answer by RogerAMoe Thursday, February 23, 2017 5:45 AM
    Thursday, February 16, 2017 10:35 PM
  • I stumbled across this link on the Intel Website:

    https://downloadcenter.intel.com/download/25016/Intel-Network-Adapter-Driver-for-Windows-10 

    It includes link aggregation for Windows 10 latest build. I have not tried it yet but for those with Intel NICs this may be a solution while we age waiting on Microsoft. With all the Linux luv Microsoft is showing of late, emulating Linux ubiquitous link aggregation support would be a good place to start.

    RAM.

    Thursday, February 23, 2017 5:52 AM
  • I wish that was the magical solution. However, I did stumble on the greatest workaround ever. I am now getting full dual gigabit speeds between my client and server saturating up to 240mbps!!!!!!!!! Forget the drivers and waiting on their support. If you want it done right, do it yourself! I can create a video walkthrough on how to do it, but in short it just involves setting both (or all you want to use) ports to the same IP address for the computer and adjusting your network settings accordingly. Once theyre all set on the same IP, DNS, metric, etc. you just bridge your adapters and presto! Works like a charm! 
    Tuesday, February 28, 2017 7:19 AM
  • Intel has released a driver that has confirmed working teaming and trunking/vlan:
    https://downloadcenter.intel.com/download/25016/Intel-Network-Adapter-Driver-for-Windows-10

    Works with Win10 1607 only (you need to have -all- windows updates).

    Team and vlan must be set up within the driver, not via windows. (Just like it always has been on client OS).

    Tuesday, February 28, 2017 12:24 PM
  • Hi,

    I have a different request/angle on this thread which I have been following for some time.

    Does this affect SMB Multichannel under SMB3?

    I have just managed to find a workaround for the SAMBA install on my Synology NAS and wanted to go this path instead of a NAS rebuild and installing 10GBe.

    I do not use VM's and I am after high transfer rates to/from a single client for large file access, so I have considered teaming to be unimportant (though it is considered a setup component of SMBMC from what I read on MS site?

    It does not seem like link aggregation is essential but I got the impression from reading that it is recommended.

    Can anyone comment on the current status of this with regard to Win 10 Home?

    Saturday, March 11, 2017 11:26 PM
  • Intel has released a driver that has confirmed working teaming and trunking/vlan:
    https://downloadcenter.intel.com/download/25016/Intel-Network-Adapter-Driver-for-Windows-10

    Works with Win10 1607 only (you need to have -all- windows updates).

    Team and vlan must be set up within the driver, not via windows. (Just like it always has been on client OS).

    I bought two Intel I350-T4 (quad port network cards), put them in both my machines (Win10 Pro), downloaded and installed the driver mentioned in the quote above and was able to bond/team the ports (for now just with two gigabit ethernet cables per card) via driver settings, resulting in a 2-gigabit-bond. Awesome!
    Monday, April 24, 2017 11:52 AM
  • needless to say, it still does not work natively.

    I have some intel nic on my motherboard and a dual gigabit usb3 adaptor.

    I have just created a 3Gbps bond using the intel teaming driver utility, it detected the startech usb3 nic''s and I just added them in and it works.

    well, it works so far anyway.

    Even linux makes bonding very easy these days, it is unacceptable that it is not here in windows 10 but this workaround it here if people have to use win10.

    https://downloadcenter.intel.com/download/25016/Intel-Network-Adapter-Driver-for-Windows-10

    I dont knwo what will happen if you have no intel nics at all but its worth a try, even a temporary install of an intel nic, add the non intel nics and then remove the intel nic should work.

    Wednesday, May 3, 2017 9:52 PM
  • Any chance this feature will be included in the upcoming Windows 10 Workstation edition (mentioned in leaks), or added to Enterprise edition in the future? It would be very helpful. It's not just that we cannot do teaming without it, we also cannot do trunking with a single NIC (trunking requires creating a team first, even if it's a team of just one interface).

    Eric Hodges

    Wednesday, June 14, 2017 3:56 PM