I211/I217-V Windows 10 LACP teaming fails

[FKurt]

Hello,

after the update to Windows 10 (x64, Build 10240) the creation of a teaming group (static or IEEE802.3ad) with a I211+I217-V NIC fails.

Drivers have been upgraded to the latest version available and multiple reinstallations with reboots din't help either. Whenever the group creation wizzard is used and a groupname (several tried), the adapters and LACP have been selected, a Windows pop-up appears to tell me group creation has failed.

However the Windows Device Manager shows a newly created "Intel Advanced Network Services Virtual Adapter", so some kind of configuration seems to get done.

Using Windows 7 SP1 x64 the exact same setup worked flawlessly for months, so Win10/the driver are the likely culprit.

Is anyone experiencing similar problems and/or is this a known bug? Feedback on this issue is greatly appreciated.

Thanks in advance!

Kind regards,

Famaku

[AToto]

since you arent an official intel employee and you arent adding any usefull information to the thread i would ask you to not post here just for the sake of posting.

we KNOW that not all adapters are supported yet. the driver download page of the PT adapters lists a windows10 driver tab and therefor is missleading ppl about the support. the card itself supports operation in the windows 10 enviroment and its safe for customers to asume that windows 10 would support teaming, if win7/win8.1 supported it without any flaws. if intel decides to stop supporting the older server adapters that is unfortunate for alot of people, because they are perfectly good cards and i dont see a reason to sidegrade to i350s. there is no incentive whatsoever to upgrade a high quality server adapter if you dont go to at least a 10gbe. we are simply waiting for intel to give us some information about the reasons why drivers work for singleports but teaming doesnt currently work in windows 10.

TLDR, please dont post, if you cant add anything beyond what the official intel employees allready told us earlier. we know its not supported right now and we are waiting for OS integration and/or intel driver workaround

[MMath7]

Hello,

this morning (2nd march 2016) was another cumulative update to version 10586.122 and still no teaming or vlan...

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

This is really a long time now since we had no updates on this issue (either tfrom intel here or microsoft here :

https://social.technet.microsoft.com/Forums/en-US/66166918-5b67-4754-89e5-a2572b1888a2/nic-teaming-failed-build-10568-windows-10?forum=win10itpronetworking NIC Teaming failed (Build 10568) Windows 10)

I hope you can provide with some news (hopefully good ones)

Regards

[st4]

Hi Matioupi,

I am sorry to inform there is no update yet about VLAN support in Windows 10. You may check the note on the latest driver we have:

https://downloadcenter.intel.com/download/25016/Network-Adapter-Driver-for-Windows-10?v=t Download Network Adapter Driver for Windows® 10

rgds,

wb

[CKlut]

So are we waiting on Microsoft or Intel here? Sorry, but this is really a joke.

[VDifi]

This is indeed a joke, we have an entire office with over a dozen workstation all with Intel i350-t2/4 cards and since we upgraded (we had to in order to stay current with some of our vendor's software) we have lost the ability of teaming our NICs.

This is causing delays in our work and frustration in our employees. If Intel cannot offer this functionality anymore, they shold be issuing a refund for their NIC adapters.

To tell your customers to complain to MS is irritating at best.

Intel get your act together and provide us with a timeline of resolution.

Thank you

[DGara]

I am throwing my hat into the ring here as well. wondering when this might be fixed.

[MMath7]

This morning, cumulative update to Win 10 : 10586.164

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

[idata]

I have been waiting EIGHT MONTHS for this foolish fiasco to be resolved too, with several driver updates and Windows 10 builds not addressing it. What is the hold up? I used to have a 4x1Gbps trunk to my Synology and VMs and I've been stuck with 1Gbps while I wait, or go back to Windows 8.1. I have customers griping about this as well.

[CARL_W_Intel]

Here is a bit of real-time data. We are testing the latest Hotfixes from MS (one for Win10 TH2 and one for Win10 RTM) and are seeing very promising results that the issue appears to fix the Teaming/VLAN issues. However, until run a full test pass through our SW teams we won't know if fixing this one issue has introduced new issues. Only a full test pass can reveal theses potentially hidden bugs.

I'll keep you posted.

[MMath7]

Great news, and thanks to intel for breaking this disapointing silence first (of the 2 companies involved...) !

Please keep updating, this is always better than nothing !

[KKuhl]

Thank you Carl_Wilson for letting us know this is still a live issue, and Intel is working on a solution. The tendency of some companies to remain completely silent on issues can make customers believe nothing is happening.

[NAlle]

Carl what hot fix are you referring to is it a insider build? I am open to testing anything needed as this is not a production box. I have been thinking abought loading TH2 but have put it off as of yet however if it may resolve this im game. PM me if you would like me to test anything.

[AChar2]

Thanks Carol! Looking forward to an update in the coming days/weeks. This is a hot item for my team for our next phase of deployment.

[JEber1]

Hi Carl

Just posting here as yet another user seeking Teaming driver for Windows 10. My adapter is Intel(R) PRO/1000 PT Quad Port Server Adapter. Looking forward to it!

John

[THash5]

I second that. Carl_Wilson do you have any details on the hotfix you referred to? Many people will want to test this before we're all surprised (again) with what it fixes and what it may break. Thanks!

[CARL_W_Intel]

Once I am able to confirm that the MS provided 'hot fix' corrects the issue and doesn't break anything else I can state specifically which one it is. However, again - this only gets you 50% there. After we confirm the hotfix corrects the issue, then we need to release a tested/validated driver that re-enables the features.

[THash5]

Thanks Carl_Wilson, really appreciate your follow up on this. The community thanks you!

[MMath7]

Hello Carl, thank you for the updates.

Once you tells us which hotfix to test, would reverting to intel drivers without ANS and VLAN purposely disabled be a temp workaround ?

Do you have an ETA for final tests and the next driver serie release ? (assuming that nothing goes wrong in between) ?

Regards

[CARL_W_Intel]

Not yet. But then again, I am only asking the engineering team 2-3 times a week for updates. Its complication is in the fact that it takes several weeks to go through an entire test pass, given the number of platforms and devices that we have to test with.

[ABurn5]

Hi Carl, could we please have an update on the current situation?

[EAlle2]

We're really in need of this updated driver. Here's hoping it comes soon!