<?xml version="1.0" encoding="utf-8" ?>
<?xml-stylesheet type="text/xsl" href="RSS_xslt_style.asp" version="1.0" ?>
<rss version="2.0" xmlns:WebWizForums="https://syndication.webwiz.net/rss_namespace/">
 <channel>
  <title>ASRock Forums : Fatal1ty X99 Professional Gaming i7 - LACP - Win10</title>
  <link>https://forum.asrock.com/</link>
  <description><![CDATA[This is an XML content feed of; ASRock Forums : Intel Motherboards : Fatal1ty X99 Professional Gaming i7 - LACP - Win10]]></description>
  <copyright>Copyright (c) 2006-2013 Web Wiz Forums - All Rights Reserved.</copyright>
  <pubDate>Sun, 21 Jun 2026 14:20:08 +0000</pubDate>
  <lastBuildDate>Fri, 19 Aug 2016 12:25:33 +0000</lastBuildDate>
  <docs>http://blogs.law.harvard.edu/tech/rss</docs>
  <generator>Web Wiz Forums 12.04</generator>
  <ttl>360</ttl>
  <WebWizForums:feedURL>https://forum.asrock.com/RSS_post_feed.asp?TID=3178</WebWizForums:feedURL>
  <image>
   <title><![CDATA[ASRock Forums]]></title>
   <url>https://forum.asrock.com/forum_images/web_wiz_forums_black.png</url>
   <link>https://forum.asrock.com/</link>
  </image>
  <item>
   <title><![CDATA[Fatal1ty X99 Professional Gaming i7 - LACP - Win10 :   parsec wrote:can someone explain...]]></title>
   <link>https://forum.asrock.com/forum_posts.asp?TID=3178&amp;PID=16016&amp;title=fatal1ty-x99-professional-gaming-i7-lacp-win10#16016</link>
   <description>
    <![CDATA[<strong>Author:</strong> <a href="https://forum.asrock.com/member_profile.asp?PF=3565">BlaÂ©k Widowmaker</a><br /><strong>Subject:</strong> 3178<br /><strong>Posted:</strong> 19 Aug 2016 at 12:25pm<br /><br /><table width="99%"><tr><td class="BBquote"><img src="forum_images/quote_box.png" title="Originally posted by parsec" alt="Originally posted by parsec" style="vertical-align: text-bottom;" /> <strong>parsec wrote:</strong><br /><br />can someone explain to me how it can be Intel's fault?</td></tr></table><div>&nbsp;</div><div>Well no problem: Ask MS. <img src="http://forum.asrock.com/smileys/smiley8.gif" height="17" width="17" border="0" alt="Clown" title="Clown" /></div><span style="font-size:10px"><br /><br />Edited by BlaÂ©k Widowmaker - 19 Aug 2016 at 12:26pm</span>]]>
   </description>
   <pubDate>Fri, 19 Aug 2016 12:25:33 +0000</pubDate>
   <guid isPermaLink="true">https://forum.asrock.com/forum_posts.asp?TID=3178&amp;PID=16016&amp;title=fatal1ty-x99-professional-gaming-i7-lacp-win10#16016</guid>
  </item> 
  <item>
   <title><![CDATA[Fatal1ty X99 Professional Gaming i7 - LACP - Win10 :   BlaÂ©k Widowmaker wrote: Well...]]></title>
   <link>https://forum.asrock.com/forum_posts.asp?TID=3178&amp;PID=15822&amp;title=fatal1ty-x99-professional-gaming-i7-lacp-win10#15822</link>
   <description>
    <![CDATA[<strong>Author:</strong> <a href="https://forum.asrock.com/member_profile.asp?PF=74">parsec</a><br /><strong>Subject:</strong> 3178<br /><strong>Posted:</strong> 13 Aug 2016 at 9:15am<br /><br /><table width="99%"><tr><td class="BBquote"><img src="forum_images/quote_box.png" title="Originally posted by BlaÂ©k Widowmaker" alt="Originally posted by BlaÂ©k Widowmaker" style="vertical-align: text-bottom;" /> <strong>BlaÂ©k Widowmaker wrote:</strong><br /><br />Well thanks for your replies. Making long story short:<div>&nbsp;</div><div><b><u>Intel says. "its not our fault - please ask MS"</u></b></div><div><b><u>&nbsp;</u></b></div><div><b><u>MS says: "its not our fault - please ask Intel"...</u></b></div><div>&nbsp;</div><div><img src="http://forum.asrock.com/smileys/smiley7.gif" height="17" width="17" border="0" alt="Angry" title="Angry" /></div><div>&nbsp;</div><div><table width="99%"><tr><td class="BBquote"><img src="forum_images/quote_box.png" title="Quote" alt="Quote" style="vertical-align: text-bottom;" /> Whether or not a board is ugly or not, depends upon the Person.</td></tr></table></div><div>&nbsp;</div><div>Perhaps, but there are some universal design rules. If you mix to much Colors, an object gets ugly. So for my Gaming i7 i will remove the red-white&nbsp; shields of the chipset- and mosfet-coolers, and paint the sillver of PCIe ports black to get a "cleaner" look. Perhaps i will overpaint also the advertisement and the logos on the MB in black, and overpaint the X99 logo in this deep red color.</div></td></tr></table><br><br>Why am I not surprised to see both of those responses, from MSoft and Intel.<br><br>My opinion is this: <br><br>Intel's network driver teaming feature has worked since Windows 7, and possibly before that. It worked fine with Windows 8 and Windows 8.1. I can (<i><b>could</b></i>... not anymore with Win 10) even team the Intel network chip with the Qualcom Atheros network chip on my ASRock X99 Extreme6/3.1 board. At least I could with the first version of Windows 10, the build before 10586.<br><br>But since Windows 10 build 10586 (which is older now), Teaming no longer works. The last version of the Intel network driver that still had working teaming was version 20.2, which ASRock still includes in the download list for Windows 10 for <b>all</b> of their X99 boards. I wonder why ASRock still has that version to download... no I don't.<br><br>Now we are on the 21.0 version of the Intel network driver. There are <i><b>four</b></i> official versions of the Intel networking driver <b>between</b> version 20.2 and 21.0. So five versions of the Intel network driver later, Intel still can't get Teaming and VLANs working.<br><br>So given this history of the Intel network driver, and then adding Windows 10 to the situation, whom do <b>I</b> blame? Not Intel.<br><br>Intel created and owns the code for their network drivers. Their networking chips and drivers are arguably the best in the business. Does Intel have complete access to the Windows 10 code related to networking? I highly doubt that. So how can Intel know what needs to be changed, if that is even possible, in their network driver to allow Teaming and VLANs to work again with Windows 10?<br><br>A change in the networking code in Windows 10 seems to have broken the Teaming and VLANs features. They still work in Windows 7, 8, and 8.1. Given all this, can someone explain to me how it can be Intel's fault?<br><br>]]>
   </description>
   <pubDate>Sat, 13 Aug 2016 09:15:52 +0000</pubDate>
   <guid isPermaLink="true">https://forum.asrock.com/forum_posts.asp?TID=3178&amp;PID=15822&amp;title=fatal1ty-x99-professional-gaming-i7-lacp-win10#15822</guid>
  </item> 
  <item>
   <title><![CDATA[Fatal1ty X99 Professional Gaming i7 - LACP - Win10 :  Well thanks for your replies....]]></title>
   <link>https://forum.asrock.com/forum_posts.asp?TID=3178&amp;PID=15821&amp;title=fatal1ty-x99-professional-gaming-i7-lacp-win10#15821</link>
   <description>
    <![CDATA[<strong>Author:</strong> <a href="https://forum.asrock.com/member_profile.asp?PF=3565">BlaÂ©k Widowmaker</a><br /><strong>Subject:</strong> 3178<br /><strong>Posted:</strong> 13 Aug 2016 at 8:16am<br /><br />Well thanks for your replies. Making long story short:<div>&nbsp;</div><div>Intel says. "its not our fault - please ask MS"</div><div>&nbsp;</div><div>MS says: "its not our fault - please ask Intel"...</div><div>&nbsp;</div><div><img src="http://forum.asrock.com/smileys/smiley7.gif" height="17" width="17" border="0" alt="Angry" title="Angry" /></div><div>&nbsp;</div><div><table width="99%"><tr><td class="BBquote"><img src="forum_images/quote_box.png" title="Quote" alt="Quote" style="vertical-align: text-bottom;" /> Whether or not a board is ugly or not, depends upon the Person.</td></tr></table></div><div>&nbsp;</div><div>Perhaps, but there are some universal design rules. If you mix to much Colors, an object gets ugly. So for my Gaming i7 i will remove the red-white&nbsp; shields of the chipset- and mosfet-coolers, and paint the sillver of PCIe ports black to get a "cleaner" look. Perhaps i will overpaint also the advertisement and the logos on the MB in black, and overpaint the X99 logo in this deep red color.</div><span style="font-size:10px"><br /><br />Edited by BlaÂ©k Widowmaker - 13 Aug 2016 at 8:28am</span>]]>
   </description>
   <pubDate>Sat, 13 Aug 2016 08:16:17 +0000</pubDate>
   <guid isPermaLink="true">https://forum.asrock.com/forum_posts.asp?TID=3178&amp;PID=15821&amp;title=fatal1ty-x99-professional-gaming-i7-lacp-win10#15821</guid>
  </item> 
  <item>
   <title><![CDATA[Fatal1ty X99 Professional Gaming i7 - LACP - Win10 : Thanks for sharing your response...]]></title>
   <link>https://forum.asrock.com/forum_posts.asp?TID=3178&amp;PID=15813&amp;title=fatal1ty-x99-professional-gaming-i7-lacp-win10#15813</link>
   <description>
    <![CDATA[<strong>Author:</strong> <a href="https://forum.asrock.com/member_profile.asp?PF=140">Xaltar</a><br /><strong>Subject:</strong> 3178<br /><strong>Posted:</strong> 13 Aug 2016 at 12:05am<br /><br />Thanks for sharing your response from ASRock Tech Support. I am sure others will find it useful too. Also thanks Parsec for the additional information, I was unaware that there was such a large issue with Teaming and windows 10 with intel NICs. Yet another reason I still have not moved over to win 10 myself. I am a big time supporter of the philosophy of "if it works, leave it alone".&nbsp;<div><br></div><div>Personally I love the look of the Taichi, I think the black and white contrasts very nicely and would be ideal for a white/black themed build or even blue/white. Of the 2 boards though I think I do prefer the specs of the Gaming i7, I like the inclusion of a better sound chip because I dabble in music recording.&nbsp;</div>]]>
   </description>
   <pubDate>Sat, 13 Aug 2016 00:05:24 +0000</pubDate>
   <guid isPermaLink="true">https://forum.asrock.com/forum_posts.asp?TID=3178&amp;PID=15813&amp;title=fatal1ty-x99-professional-gaming-i7-lacp-win10#15813</guid>
  </item> 
  <item>
   <title><![CDATA[Fatal1ty X99 Professional Gaming i7 - LACP - Win10 :   BlaÂ©k Widowmaker wrote:Hello...]]></title>
   <link>https://forum.asrock.com/forum_posts.asp?TID=3178&amp;PID=15811&amp;title=fatal1ty-x99-professional-gaming-i7-lacp-win10#15811</link>
   <description>
    <![CDATA[<strong>Author:</strong> <a href="https://forum.asrock.com/member_profile.asp?PF=74">parsec</a><br /><strong>Subject:</strong> 3178<br /><strong>Posted:</strong> 12 Aug 2016 at 9:55pm<br /><br /><table width="99%"><tr><td class="BBquote"><img src="forum_images/quote_box.png" title="Originally posted by BlaÂ©k Widowmaker" alt="Originally posted by BlaÂ©k Widowmaker" style="vertical-align: text-bottom;" /> <strong>BlaÂ©k Widowmaker wrote:</strong><br /><br /><p><strong>Hello dear AsRock Team,<br><br></strong> I plan an upgrade of my System to X99. I've waited over a year for a MB like the new <a href="http://www.asrock.com/mb/Intel/Fatal1ty%20X99%20Professi&#111;nal%20Gaming%20i7/" target="_blank" rel="nofollow"><u><font color="#0066cc">AsRock Fatal1ty X99 Professional Gaming i7</font></u></a><br><br><a href="http://www.asrock.com/mb/Intel/Fatal1ty%20X99%20Professi&#111;nal%20Gaming%20i7/" target="_blank" rel="nofollow"><img src="http://gzhls.at/p/0032/1480032/1480032-3.jpg" border="0" /></a><br> <u><b>This is the first X99 MB with two PCIe 3.0x4 M.2 Ports on it - that is not uggly </b></u>(like the Taichi or Extreme 11). But when i read the <a href="ftp://europe.asrock.com/Manual/Fatal1ty%20X99%20Professi&#111;nal%20Gaming%20i7.pdf" target="_blank" rel="nofollow"><u><font color="#0066cc">manual (page 3)</font></u></a> i saw this:<br><br><strong>Lan </strong><br><br> - Gigabit LAN 10/100/1000 Mb/s <br>- 1 x Giga PHY IntelÂ® I218V, 1 x GigaLAN IntelÂ® I211AT <br> - Supports Wake-On-LAN <br> - Supports Lightning/ESD Protection (ASRock Full Spike Protection)<br><strong><font color="#ff0000"> - </font><u><font color="#ff0000">Supports Dual LAN with Teaming* <br> * WindowsÂ® 10 is not supported. </font></u></strong><br> - Supports Energy Efficient Ethernet 802.3az <br> - Supports PXE<br><br> <u><b>Now does this means that this MB doesn't support LACP / IEEE 802.3ad with Win 10?</b></u><br> Why? Is this a bug, and will it be fixed with future BIOS/UEFI versions?<br> Is LACP / IEEE 802.3ad supported with Win 7?<br> Hope you can help me with some information. Sorry for my bad English.<br> Greetings from Germany<br><br></p></td></tr></table><br><br>The specification you are asking about means that the <i><b>Intel network driver's Teaming feature is not supported in Windows 10.</b></i><br><br>Intel's network driver has had the Teaming feature available with their networking chips, and some chips made by other manufactures, for several years.<br><br>When Windows 10 was released, for some reason it broke the Intel networking driver Teaming feature. The ability to create VLANs in the network driver was also broken. These problems are caused by some interaction between Windows 10 and the Intel network driver.<br><br>This problem affects <b>all mother boards using Intel networking chips when used with Windows 10</b>. It cannot be fixed with a UEFI/BIOS update, unless Intel creates a fix to the Intel network Option ROM that is part of a UEFI/BIOS file.<br><br>Since this problem was discovered, Intel has released at least four updates to their networking driver, but has been unable to fix the problem with Teaming and Windows 10. Intel documents this situation on the download page of their networking driver, which you can read about here (sorry that it is in English):<br><br><a href="https://downloadcenter.intel.com/download/25016/Intel-Network-Adapter-Driver-for-Windows-10?product=83418" target="_blank" rel="nofollow">https://downloadcenter.intel.com/download/25016/Intel-Network-Adapter-Driver-for-Windows-10?product=83418</a><br><br>To quote from the Intel networking driver download page:<br><br><i><b>Creating Intel ANS teams and VLANs on 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 Windows 10 client in a future release.</b></i><br><br>I don't understand your question about LACP / IEEE 802.3ad with Windows 10, which I think you were just confused about the specification you are asking about.<br><br>Whether or not a board is ugly or not, depends upon the person. <img src="https://forum.asrock.com/smileys/smiley2.gif" border="0" alt="Wink" title="Wink" /><br><br>]]>
   </description>
   <pubDate>Fri, 12 Aug 2016 21:55:49 +0000</pubDate>
   <guid isPermaLink="true">https://forum.asrock.com/forum_posts.asp?TID=3178&amp;PID=15811&amp;title=fatal1ty-x99-professional-gaming-i7-lacp-win10#15811</guid>
  </item> 
  <item>
   <title><![CDATA[Fatal1ty X99 Professional Gaming i7 - LACP - Win10 :  I wrote an email to AsRock Support...]]></title>
   <link>https://forum.asrock.com/forum_posts.asp?TID=3178&amp;PID=15809&amp;title=fatal1ty-x99-professional-gaming-i7-lacp-win10#15809</link>
   <description>
    <![CDATA[<strong>Author:</strong> <a href="https://forum.asrock.com/member_profile.asp?PF=3565">BlaÂ©k Widowmaker</a><br /><strong>Subject:</strong> 3178<br /><strong>Posted:</strong> 12 Aug 2016 at 9:01pm<br /><br />I wrote an email to AsRock Support and get this answer:<div>&nbsp;</div><div><p ="Ms&#111;normal"><span style='color: rgb31, 73, 125; font-family: "Calibri",sans-serif; font-size: 11pt; mso-fareast-: EN-US;'>Hello,<o:p></o:p></span></p><p ="Ms&#111;normal"><span style='color: rgb31, 73, 125; font-family: "Calibri",sans-serif; font-size: 11pt; mso-fareast-: EN-US;'><o:p></o:p></span>&nbsp;</p><p ="Ms&#111;normal"><span style='color: rgb31, 73, 125; font-family: "Calibri",sans-serif; font-size: 11pt; mso-fareast-: EN-US;'> Windows10 is not supporting this feature (anymore). In first available versions it was supported, but then having still trouble. So they remove that support in WIN10.<o:p></o:p></span></p><p ="Ms&#111;normal"><span style='color: rgb31, 73, 125; font-family: "Calibri",sans-serif; font-size: 11pt; mso-fareast-: EN-US;'>See Also here:<o:p></o:p></span></p><p ="Ms&#111;normal"><span style='color: rgb31, 73, 125; font-family: "Calibri",sans-serif; font-size: 11pt; mso-fareast-: EN-US;'><a href="https://www.computerbase.de/2016-01/kein-link-aggregati&#111;n-in-windows-10-build-11099/" target="_blank" rel="nofollow"><u><font color="#0066cc" face="Calibri" size="3">https://www.computerbase.de/2016-01/kein-link-aggregation-in-windows-10-build-11099/</font></u></a><o:p></o:p></span></p><p ="Ms&#111;normal"><span style='color: rgb31, 73, 125; font-family: "Calibri",sans-serif; font-size: 11pt; mso-fareast-: EN-US;'><o:p></o:p></span>&nbsp;</p><p ="Ms&#111;normal"><span style='color: rgb31, 73, 125; font-family: "Calibri",sans-serif; font-size: 11pt; mso-fareast-: EN-US;'>It is not ASRock?™s fault or a bug, Microsoft did not support it (well) with Windows 10 and remove the support.<o:p></o:p></span></p><p ="Ms&#111;normal"><span style='color: rgb31, 73, 125; font-family: "Calibri",sans-serif; font-size: 11pt; mso-fareast-: EN-US;'>You might check with Microsoft if an when they plan to implement it. (same is what we are still doing ??try to ?œpush??Microsoft and Intel to get it to work)<o:p></o:p></span></p><p ="Ms&#111;normal"><span style='color: rgb31, 73, 125; font-family: "Calibri",sans-serif; font-size: 11pt; mso-fareast-: EN-US;'><o:p>&nbsp;</o:p></span></p><p ="Ms&#111;normal"><span style='color: rgb31, 73, 125; font-family: "Calibri",sans-serif; font-size: 11pt; mso-fareast-: EN-US;'><o:p></o:p></span><span style='color: rgb31, 73, 125; font-family: "Calibri",sans-serif; font-size: 11pt; mso-fareast-: EN-US;'>Have to say sorry, but right now we cannot to more than waiting that Microsoft / Intel get it fixed ??or you have to use an other OS??o:p></o:p></span></p><p ="Ms&#111;normal"><span style='color: rgb31, 73, 125; font-family: "Calibri",sans-serif; font-size: 11pt; mso-fareast-: EN-US;'><o:p>&nbsp;</o:p></span><span style='color: rgb31, 73, 125; font-family: "Calibri",sans-serif; font-size: 11pt; mso-fareast-: EN-US;'>Best regards,<o:p></o:p></span></p><p ="Ms&#111;normal"><span style='color: rgb31, 73, 125; font-family: "Calibri",sans-serif; font-size: 11pt; mso-fareast-: EN-US;'><o:p>&nbsp;</o:p></span><span lang="EN-US" style='color: rgb31, 73, 125; font-family: "Calibri",sans-serif; font-size: 11pt;'>ASRock Support<o:p></o:p></span></p><div><p ="Ms&#111;normal"><span lang="EN-US" style='color: rgb31, 73, 125; font-family: "Calibri",sans-serif; font-size: 11pt;'><br>ASRock Europe B.V.<br>Bijsterhuizen 1111<br>6546 AR Nijmegen<br>The Netherlands<br><a href="http://www.asrock.com/" target="_blank" rel="nofollow"><span style="color: rgb31, 73, 125;"><u><font face="Calibri" size="3">www.asrock.com</font></u></span></a></span></p></div></div>]]>
   </description>
   <pubDate>Fri, 12 Aug 2016 21:01:43 +0000</pubDate>
   <guid isPermaLink="true">https://forum.asrock.com/forum_posts.asp?TID=3178&amp;PID=15809&amp;title=fatal1ty-x99-professional-gaming-i7-lacp-win10#15809</guid>
  </item> 
  <item>
   <title><![CDATA[Fatal1ty X99 Professional Gaming i7 - LACP - Win10 : Hello dear AsRock Team, I plan...]]></title>
   <link>https://forum.asrock.com/forum_posts.asp?TID=3178&amp;PID=15544&amp;title=fatal1ty-x99-professional-gaming-i7-lacp-win10#15544</link>
   <description>
    <![CDATA[<strong>Author:</strong> <a href="https://forum.asrock.com/member_profile.asp?PF=3565">BlaÂ©k Widowmaker</a><br /><strong>Subject:</strong> 3178<br /><strong>Posted:</strong> 03 Aug 2016 at 9:21pm<br /><br /><p><strong>Hello dear AsRock Team,<br><br></strong> I plan an upgrade of my System to X99. I've waited over a year for a MB like the new <a href="http://www.asrock.com/mb/Intel/Fatal1ty%20X99%20Professi&#111;nal%20Gaming%20i7/" target="_blank" rel="nofollow"><u><font color="#0066cc">AsRock Fatal1ty X99 Professional Gaming i7</font></u></a><br><br><a href="http://www.asrock.com/mb/Intel/Fatal1ty%20X99%20Professi&#111;nal%20Gaming%20i7/" target="_blank" rel="nofollow"><img src="http://gzhls.at/p/0032/1480032/1480032-3.jpg" border="0" /></a><br> This is the first X99 MB with two PCIe 3.0x4 M.2 Ports on it - that is not uggly (like the Taichi or Extreme 11). But when i read the <a href="ftp://europe.asrock.com/Manual/Fatal1ty%20X99%20Professi&#111;nal%20Gaming%20i7.pdf" target="_blank" rel="nofollow"><u><font color="#0066cc">manual (page 3)</font></u></a> i saw this:<br><br><strong>Lan </strong><br><br> - Gigabit LAN 10/100/1000 Mb/s <br>- 1 x Giga PHY IntelÂ® I218V, 1 x GigaLAN IntelÂ® I211AT <br> - Supports Wake-On-LAN <br> - Supports Lightning/ESD Protection (ASRock Full Spike Protection)<br><strong><font color="#ff0000"> - Supports Dual LAN with Teaming* <br> * WindowsÂ® 10 is not supported. </font></strong><br> - Supports Energy Efficient Ethernet 802.3az <br> - Supports PXE<br><br> Now does this means that this MB doesn't support LACP / IEEE 802.3ad with Win 10?<br> Why? Is this a bug, and will it be fixed with future BIOS/UEFI versions?<br> Is LACP / IEEE 802.3ad supported with Win 7?<br> Hope you can help me with some information. Sorry for my bad English.<br> Greetings from Germany<br><br></p><span style="font-size:10px"><br /><br />Edited by BlaÂ©k Widowmaker - 03 Aug 2016 at 9:36pm</span>]]>
   </description>
   <pubDate>Wed, 03 Aug 2016 21:21:29 +0000</pubDate>
   <guid isPermaLink="true">https://forum.asrock.com/forum_posts.asp?TID=3178&amp;PID=15544&amp;title=fatal1ty-x99-professional-gaming-i7-lacp-win10#15544</guid>
  </item> 
 </channel>
</rss>