- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
OK, lets clear a few things up. Lets start with Windows Release Basics.
Windows 10 Version 1507 (build 10.0.10240), codenamed "Threshold 1"
Windows 10 Version 1511 (build 10.0.10586), codenamed "Threshold 2"
Windows 10 Anniversary Update, or Windows 10 Version 1607 (build 10.0.14393), codenamed "Redstone 1"
Windows 10 Creators Update[202] or Windows 10 Version 1703, codenamed "Redstone 2"
1) MS Windows 10 Redstone 1 is where the fix was rolled out by Microsoft was for Windows 10 Anniversary Update, or Windows 10 Version 1607 (build 10.0.14393). Versions prior to 1607 do not have the hot-fix available. Versions after 1511 are "Redstone 2" which is in Beta has not been released yet.
2) Beta releases of operating systems are not tested and validated on posted drivers on the web. If you install the v22.0.1 driver package on releases after Windows 10, version 1607 you will need to escalate any bugs directly to Microsoft.
3) All the issues I see above on these threads are related to a Beta version of Windows 10. propergol , deecol
4) Famaku , you are on Windows 10 version 10240 ("Threshold 1"). MS did not port the Hot Fix for that OS to TH1. Please upgrade to RS1
5) I don't know about this one MassimoS.. You might want to make sure that your system has all available updates from MS. If that doesn't fix the issue, then the Intel support team will need to look into it.
That's the best I can do. My recommendation is to move the request to a new thread for those systems that are RS1 that have all the correct patches installed (please verify they were successful). That way, it can be addressed as a new issue (which it will be) vs. the OS limitation that this string is about.
Link Copied
- « Previous
- Next »
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I contacted support again, this is what I got back:
Hello John,
Thank you very much for letting us know.
We are currently working on a fix so you can expect one in the near future.
Thank you for your patience and understanding!
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- « Previous
- Next »