Fatal1ty X99 Professional Gaming i7 - LACP - Win10

I wrote an email to AsRock Support and get this answer:

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". 

Bla©k Widowmaker wrote: Well thanks for your replies. Making long story short:   Intel says. "its not our fault - please ask MS"   MS says: "its not our fault - please ask Intel"...     Whether or not a board is ugly or not, depends upon the Person.   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  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.

Why am I not surprised to see both of those responses, from MSoft and Intel.

My opinion is this:

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 (could... 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.

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 all of their X99 boards. I wonder why ASRock still has that version to download... no I don't.

Now we are on the 21.0 version of the Intel network driver. There are four official versions of the Intel networking driver between version 20.2 and 21.0. So five versions of the Intel network driver later, Intel still can't get Teaming and VLANs working.

So given this history of the Intel network driver, and then adding Windows 10 to the situation, whom do I blame? Not Intel.

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?

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?