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.

Yes, the Intel PROSet Software V20.2 you mention is exactly what's installed on the system. As Win10 has quiet a lot of flaws/bugs I'm somewhat inclined to believe the problem is on Microsofts end but it's always better to tackle an issue from two sides.

If you believe it helpful, I could also put an Intel I350-T4 in the system and see if that NIC works with teaming.

Thank you for your input!

Regards,

Famaku

----------

Edit:

Just tried the driver from ASRock's (Mainboard) page: it's a slightly newer version (v20.2.4001 instead of v20.2.3001) but otherwise "works" the same. No teaming that is.

I have a very similar issue. Just upgraded to Windows 10 and installed PROSet v20.2 on a I350-T4. I am able to create the team but then shows up disabled and when going into the team properties to create the required VLANs, all options are greyed out. Tried every which way from network connection page, device manager etc. etc. but no joy. If I revert my OS back to Windows 8.1, my adapters and ANS work just fine. Connecting back into my network via LACP to a Cisco 2960 switch.

For now I am going back to my Win 8.1 build but would very much appreciate it when a suitable driver update is available.

thanks for the update! Seems my suspicions as for the culptrit were justified... this OS launch is the best ad campaign linux could ever hope for. On a side note: the I350-T4 didn't work either. Lukily my other boxes aren't on Win10.

i have the same issue with a different NICs. Intel Pro/1000 PT Dual/Quad Server Adapter im using these cards in 2 systems and i cant enable LACP/Static either. it could be an issue with upgrading from 8.1 to 10 instead of performing a clean install, but i dont have the time to do a fresh installation atm and i needed the systems up and running.

One is a HP Z210 Workstation and the other one is my desktop system running fairly new hardware ~2014-2015.

i was checking on your driverpage for updates but the windows10 section only has the information files on it and had no updated drivers yet. im sure you guys and girls at intel are being spammed with support requests atm but i wanted to add my experience with the cards i described to this to make sure its not just a single chip causing an issue.

I have the same issue with the same drivers - but motherboard is gigabyte z87-oc-force - with latest BIOS 10b - worked fine in windows 8.1 and not in windows 10 - tried re-installing drivers - etc. Even in a brand new install of windows 10 - no luck in network teaming

Good day. We received feedback that creating Intel® ANS teams and VLANs on Microsoft* Windows* 10 is currently not supported. We expect that ANS will be supported on Microsoft* Windows* 10 client in a future release. In case you need teaming feature, you may try revert back to previous OS which can support the teaming. Apologize for any inconvenience this might have caused.