Here is the reply I received from Intel Support:
This is on regards of service ticket 184630.
In order for you to get teamning working you will need to get Intel(R)Advanced network services
set up with the operating system but Windows(R) 10 is not supported for this feature.
Creating Intel® ANS teams and VLANs on Microsoft Windows® 10 is currently not supported.
As a result, when created, teams and VLANs do not pass traffic.
We expect that ANS will be supported on Microsoft Windows 10 client in a future release
The future releases will require modifications from Microsoft in the O.S, unfurntately
it is not possible for us to provide an ETA.
We will not be able why it worked before since we are not Microsoft support we will not have the information
about the previous update you installed.
In this case we may suggest you to contact Microsoft support to check if they have another solution available
since their update was taking that feature away and and from us Intel this feature will not be supported on your
Please let us know if further assistance is required and/or if we can proceed to close this service ticket.
We will be waiting for your response.
Have a great day!
Intel Customer Support
We had hoped the potential fix expected in the August 27, 2015 Microsoft release of KB3081448 would correct the OS limitation, but our testing revealed that the blocking issue still exists. Although it doesn't appear to be a driver issue, we are continuing to work with the MS Windows 10 NDIS teams in Redmond to root cause the issue.
Due to the OS limitation we are still seeing, this why you get a warning message during the PROset install on Win10 that should warn you that you will be unable to create VLANs/Teams. This is also why you see those fields grayed out the tabs in advanced properties. Once the issue is root caused and a fix identified, we can then re-enable the ANS functions (Teaming and VLANs). I will also post a reply to this thread when I hear anything.
The key thing is you have the right I350 silicon to enable it since the driver will have WHQL certifications.
I would also suggest pinging the Microsoft Windows 10 team for a status. A bit more noise in the signal can't hurt.
Hello, are there any news about this? I have a I218-v and I211, everything was working fine in Windows 8.1.
I thought these two cards were supported in Windows 10, but if I install the Intel drivers the teaming option is greyed out.
If I use the drivers supplied by Asus, the option is available. I create the team and everything seems fine, but the the team NIC stays disabled and if I try to enable it it says "enabled" and then it stays disabled all the same. No way to enable it.
So I hope this gets worked out.
There are blocking issues within the OS that prevents the teaming from working correctly. We are working with MS on the issue. Once the OS releases a patch to correct the blocking issue we can release drivers that support the teaming features.
My recommendation is to contact MS and ask when their OS will support teaming again.
Just for statistical purposes I have the same issue with Intel Nic Teaming on Windows 10. My configuration is almost the same as Famaku.
Board: ASRock Z87 Extreme 6 a/c (Intel Z87 chipset)
Onboard NIC: Intel I217-V + Intel I211
OS: Windows 10 Professional x64 Build10586
Drivers from Intel and Asrock webpage not working.
I hope it will be sorted out until free upgrade to Windows 10 is available.
Unfortunately, I have the same problem.
Before windows 10 update, all vlan works perfectly.
Now I cannot use VLAN with anyone driver version.
PC: HP Elite Desk 800 GI, NIC INTEL I217-LM.
OS Windows 10 PRO x64.
HP Computer, Intel Hardware, Microsoft Software !!! All regularly purchased.
It's is really true that I will need to change hardware or maybe complain to the ???????.
I really need VLAN to Work... !!!
Someone need to solve these problems.
There will be two actions that will be required in order to get Teaming and VLANs working under Windows 10.
1) Once the OS fix has been identified (either through a Hot Fix or Knowledge Base Article), users will need to implement those changes.
2) Intel will need to release a Windows 10 driver that re-enables the capabilities.
At this point, we need to have #1 identified before we can proceed with a plan for #2.
I will update this post once I have more information
we own 2 X710-DA4 and 2 X520_DA2 and of course, we are faing right the same problem described in this thread with teaming and windows 10 pro.
Do you have some hint about the probability the MS fix will eventually show up and the expected timeschedule ?
I understand this affects only a tiny fraction of Windows 10 users but this is still a quite serious regression, I hope you Intel guy have means to put some pressure on them about that.
By the way, I have a second issue that may be related :
one X520-DA2 is installed on a Dell Precision T7500 station, and both links are hooked to an Arista DCS7124S switch in DAC mode (1 m cables)
OS is Windows 10 pro.
Only one link (#2) detects the connexion and the other one remains "unconnected" on both switch and computer sides.
If I move this second link to one of the Netgear Prosafe 728TXS switch rigth above, both links are detected correctly. Any clue ?