VirtualPanther and mimi74 Yes, that is correct. My steps will be for once it is re-enabled within the OS framework. Sometimes a get a bit ahead of myself.
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.