Thank you for the post. We have received some feedback regarding the creation vlan and teaming in Windows 10, we are checking on this, for the meantime,
can you provide what is the brand and model of your system and when you said the latest driver, are you referring to the Intel PROSet software version 20.2 available from our downloadcente?
Please feel free to update me. Thank you.
Thank you for the prompt reply! My system is custom build and has the following components:
- CPU: Intel Core i5-4670
- Board: ASRock Z87 Extreme 6 (Intel Z87 chipset)
- Onboard NIC: Intel I217V + Intel I211AT
- CNA: QLogic BR-1020
- RAM: Patriot Viper 3 Intel Extreme Masters, 4x8GB DDR3-1866
- GPU: Asus ROG Matrix R9 290X
- System SSD: Samsung 840 Evo 250GB
- HDD: Toshiba 4TB 7200rpm HDD
- PSU: be quiet! Straight Power E9-CM 480W
- Switch1: Zyxel GS1910-24 Smart Managed (connected to the Intel NIC)
- Switch2: Brocade ICX6610-24 (connected to the QLogic CNA)
- OS: Windows 10 Professional x64 Build10240
- NIC Driver: Intel PROSet (PROWinx64.exe) v20.2 (https://downloadcenter.intel.com/de/download/25016/Network-Adapter-Driver-for-Windows-10-)
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!
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.
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.
How about an update on this issue. Letting it drop into a black-hole isn't "Intel like".
I've tried downloading and installing the 20.3 software that explicitly states the following, but it doesn't work
with continued failed to create new team errors. When I return to the Win 8.1 environment, everything works as it should.
Important Note: In order to create Intel® ANS teams and VLANs on Microsoft Windows® 10, you must install the Microsoft Cumulative update located here: Microsoft KB3081448.
Failure to install the update will result in teams and VLANs that do not pass traffic.
When can we expect a solution to this critical issue?
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.