Carl,
Can you advise if you are seeing any regressions with the latest Cumulative Update (KB3147458) that appears to supersede KB3140743?
The superseding order (as best I can tell) seems to be as follows:
KB3140743 (March 1st, https://support.microsoft.com/en-us/kb/3140743)
KB3140768 (March 8th, https://support.microsoft.com/en-us/kb/3140768)
KB3147458 (April 12th, https://support.microsoft.com/en-us/kb/3147458)
For instance, I currently have the following KBs installed on my Windows 10 Pro (Version 1511 / OS Build 10586.218) box:
[01]: KB3124262
[02]: KB3124263
[03]: KB3135173
[04]: KB3139907
[05]: KB3140741
[06]: KB3140743
[07]: KB3140768
[08]: KB3154132
[09]: KB3147458
Notice that the last (09) update I have installed, is the newest generation of the KB3140743 update.
Also notice I do NOT have KB3140745 installed. When I try to to install it manually (downloading the package via the steps from https://support.microsoft.com/en-us/kb/3140745 and trying to install) I get an error stating "The update is not applicable to your computer". I'm assuming (although, I could be wrong) that this is because I have newer KBs installed that superceed it.
The reason I'm concerned about a possible regression is that I am not able to create a team using the built-in Windows libraries (i.e., not via Intel software). When I run the command:
new-NetLBFOTeam [TEAMNAME] “[NIC1]”, “[NIC2]”
(Source: How To: Enable NIC Teaming in Windows 8, 8.1 and 10 | YourITSource)
Which before November 2015 worked, I'm still getting an error and am not able to built a team using the Windows Teaming solution.
Perhaps I'm off-base, but I guess I'm under the impression if the underlying issues with Windows 10 itself are fixed, should I not be able to create a team using the built in OS functionality? Or does Intel's software rely on other faculties of the OS that are now patched - *even with the latest updates*?
Since it was a seemingly routine update that Microsoft delivered in November which "broke" this previously working functionality in Windows 10 (using the new-NetLBGOTeam cmdlet), I guess I'm not putting it past them to have accidentally (or purposefully) break it again with the latest cumulative update(s). My hope is the Intel ANS software will work even when net-NetLBFOTeam seems to continue to fail with the latest updates.
Any insight you can provide would be most appreciated!