英特尔NIC Teaming在Windows 10 RS51809破裂

刚刚更新，我的团队也被打破，似乎每次发布一个大的Windows更新时都会发生这种情况。
因为英特尔似乎懒得去那里的驱动程序团队进行测试，所以更新仍然处于测试阶段，因此当微软的更新上线时，英特尔可以让一个驱动程序退出。



以下为原文

just updated as well and my teaming is broken as well seems like this is going to happen every single time a big windows update is released. because Intel seems to be to lazy to get there driver team to test well the updates are still in beta so Intel can have a driver cranked out when the update from Microsoft goes live.

这里的Windows 10 RS5团队问题也是如此。
创建的团队被禁用，两个适配器（I211 / I218v）都处于非活动状态。
启用说启用，但事实并非如此。
设备管理器中找不到幻像适配器。



以下为原文

Windows 10 RS5 teaming problem here too. Created team is disabled and both adapters (I211/I218v) inactive. Enabling says enabled but it's not. No phantom adapters found in Device Manager.

不仅是Teaming，而且所有的VLAN都以相同的方式被破坏。
我想这会在所有功能更新后发生。
上次接近2个月需要修复，让我们看看这个时间....



以下为原文

Not only Teaming, but again all the VLANs are broken the same way. I guess this will happen now after all feature updates. It took last time close to 2 month to fix, let's see this time....

同样的问题！



以下为原文

Same problem!

我是一样的，我只希望这次不用格式化。



以下为原文

I'm the same, I just hope I do not have to format this time.

你好，
在这里添加说我也遇到了这个问题。
对我来说，这至少是向前迈出的一步，因为我在尝试创建VLAN时有1803的蓝屏死机。
现在我已经达到了创建VLAN适配器但永远保持禁用状态的程度。



以下为原文

Hello,
 
Going to add here to say that I also run into the issue here.
 
For me this is at least a step forward considering I had blue screens of death with 1803 when attempting to create a VLAN.
 
Now I have also gotten to the point where the VLAN adapter gets created but will forever stay on disabled.

同样在这里。
英特尔i350，更新后团队破产，无法重新安装。
司机＆amp;
适配器已删除，重新启动，重新安装，但没有成功。
实际上，团队适配器给人的印象是它可以启用，但它不能。
似乎英特尔的MS通信线路确实存在很大问题（反之亦然......）



以下为原文

Same here. Intel i350, team is broke after update and cannot be reinstalled. Driver & adapters removed, reboot, reinstalled, but no success. Indeed, the team adapter gives the impression that it can be enabled, but it can't.
Seems Intel does have a big problem with their MS communication line (or vice versa...)

HelloChrisk2305，感谢您发布在英特尔有线以太网社区。
一旦我们获得支持Windows 10 RS5 1809版的英特尔以太网驱动程序和软件的发布信息，我们将尽快为您提供帮助。感谢您的耐心等待。最诚挚的问候，Daniel DIntel客户支持



以下为原文

Hello Chrisk2305,

Thank you for posting in Intel Wired Ethernet Communities.  We will update you as soon as we have the release information for the Intel Ethernet drivers and software supporting Windows 10 RS5 version 1809.  Thank you for your patience.

Best regards,
Daniel D
Intel Customer Support

谢谢Daniel，
但我认为问题的第二部分是为什么这种情况继续发生？
英特尔正在做些什么来确保其产品能够按时更新微软的更新？
这正在影响英特尔的声誉。



以下为原文

Thanks Daniel,
 
But I think the 2nd part of the question is why does this keep happening? What is Intel doing to ensure it's product work with Microsoft's updates on-time?
 
This is affecting Intel's reputation.

谢谢你的更新，丹尼尔。
在这些较大的微软版本发布之前，英特尔不会做些什
当然，您可以与Microsoft合作，并确保在这些更新使其具有普遍可用性之前支持您的驱动程序。
即使英特尔不再对微软有任何影响力，当然你们也可以使用Windows Insider程序来解决这个问题。
我选择使用英特尔网卡的服务器主板，了解英特尔在与Novell，然后是Banyan和现在的微软的服务器网络方面拥有数十年的经验。
我意识到将Windows 10作为SOHO服务器运行是这里的问题的一部分，因为它不是设计为服务器，并且不被英特尔或微软这样对待，但它创建了一个很好的家庭自动化系统和驱动程序支持
当我们建造这些系统时就在那里。
如果英特尔无法摆脱这个问题，那么我想我们应该考虑改变我们的购买决策，尽管这不是我的首选。



以下为原文

Thanks for the update, Daniel. Won't Intel do something to provide support before these larger Microsoft releases? Certainly you folks have the capability to work with Microsoft and ensure support for your drivers before these updates make it to general availability. Even if Intel no longer had any leverage with Microsoft, certainly you folks could use the Windows Insider program to get ahead of this problem.
 
I went out of my way to select server boards with Intel NICs knowing the decades of experience that Intel has in server based networking with Novell and then Banyan and now Microsoft. I realize that running Windows 10 as a SOHO server is part of the problem here, as it was not designed to be a server and is not treated as such by either Intel or Microsoft, but it makes a fine home automation system and the driver support was there when we built these systems. If Intel cannot get ahead of this issue, then I guess we should consider changing our purchasing decisions, though it isn't my first choice. 

来自英特尔的人发布了一个问题，当春季更新导致一个问题时，英特尔不会认为这是一个问题，直到更新正式发布。
因此，即使微软发布测试版，所以人们和公司可以预先测试这种东西英特尔不会测试它们，他们不会测试，直到最终版本出来，然后人们抱怨有问题。
因为英特尔顽固地测试驱动程序，所以每次有更新的Windows团队和vlans将在更新后至少4-8周被打破。



以下为原文

nope someone from intel posted that when the spring update was causing an issue that intel dont consider it a problem until the update is officially released. so even though Microsoft releases a beta so people and companies can pre test this kind of stuff intel wont test with the beta they wont test until the final release is out and then people complain there is a problem. so pretty much everytime there is an update for windows teaming and vlans will be broken at least 4-8 weeks after the update due to Intel's stubbornness to test there driver.

我有同样的问题我有一个双LAN（英特尔1211-V和1219）主板，并在1809推出之前团队合作......我正在尝试重新创建团队，并看到英特尔高级网络服务协议不会
加载，当团队创建时....它加载1211和1219，但不加载团队，所以它不创建虚拟局域网....你试图启用团队，它说它已启用，
但......显示已禁用....
我们可以期待一个Hotfix或补丁的任何想法？



以下为原文

I am having same issue I have a dual LAN ( Intel 1211-V and 1219)  motherboard and had teaming working prior to the  1809 rollout... I am trying to re-create the Team and see that Intel Advanced Network Services Protocol will not load, when the Team is created.... It loads for both the 1211 and the 1219, but not for the Team, so its not creating the virtual LAN.... You try to enable the Team and it says its enabled, but... shows Disabled....
Any Ideas when we can expect a Hotfix or patch ?