Is it amateur hour at Intel now? Working with your #1 partner, Intel can't resolve an issue over a year old involving a couple lines of code???
This is absolutely unacceptable that a key differentiating feature of a NIC using code NOT SUPPORTED IN MICROSOFT CODING GUIDELINES is not fixed for over a year. You could've re-written the entire driver stack several times over in that time.
This, after forcing sidegrades to new hardware to supposedly support VLANS and Teaming, and you don't even bother to support the features forcing the upgrade. "Yeah, all these networking features missing on Intel Adapters in Windows 10, you can get them if you buy essentially the same card, just newer." "Oh, the features don't work on the new card? I meant the features will work when we bother to code them properly. When will that be? Who knows, it's probably Microsoft's fault!"
I know you are excited about having a team reporting to you, but from my perspective absolutely nothing has been accomplished for a YEAR except false advertising, false promises, and inability to deliver features on a premium network adapter- included on a Realtek NIC.
One thing you have consistently failed to explain, Carl, is how can every other single NIC manufacturer succeed where Intel can only invent excuses? I have 5-year old ASIX USB ethernet adapters with better VLAN support than your brand-new premium NICs. Can you explain that one, Carl?
And yeah, don't bother upsetting your precious release schedule to fix a year-old problem that doesn't affect a competent NIC manufacturer, where you have issued failed promise after poor excuse. Do you recommend we wait until August for the latest batch of excuses, or just buy fully functional Network Adapters from practically anyone else?
BTW, your information page on ANS still lists support for VLANs in Windows 10 when that is known to be a lie. Intel® Advanced Network Services (Intel® ANS)