I heard back from Microsoft Premier Support this morning and they are receiving more cases on this issue and it has been sent to the Product Team. Please see below.
Jeff C. Watts
Microsoft Premier Support Case response dated 05/27/2016
In the last couple of days we have received a few more cases with the same issue that you are facing with regards to this case.
As of now, the only fix is to not install the convenience rollup update KB3125574 or if it is already present, uninstall it. KB3125574 has some issues with NIC.
Another point that is noticed is that in all the cases this issue has occurred on a VMware machines and no issues are reported with hyper-v or physical machines.
This issue has been reported to the product team. Any update from here on this would be provided by the product team.
Just for the community information, this is in which ESXi version?
I tested this in my LAB with the following versions.
ESXi v5.0.0 Build 1311175
ESXi v5.5.0 Build 3116895
VMware Workstation Pro 12.1.1 Build 3770994
Also, Microsoft updated the KB3125574 Knowledge Base Article
Known issue in this convenience rollup
Known issue 1Symptoms
A new Ethernet vNIC may be created with default settings in place of the previously existing vNIC, causing network issues. Any custom settings on the previous vNIC are still persisted in the registry but unused.
To resolve this issue, uninstall the convenience rollup.
Microsoft is investigating this issue to determine proper course of action with VMWare. To resolve this issue uninstall the convenience rollup. Further information will be posted here as the investigation continues.
Need to send this information to our Windows Team.
Last meeting I heard some complains about similar issues. I was waiting for your feedback to check if is the same issue.
I've 'solved' it by removing the vNIC from VM and adding a new one, that new vNIC keeps its settings after reboots
Yes VMware states that if remove the vNIC and add again, it will pick up the old interface settings. The same after we remove the Windows Update.
But for environment that have around 1000 Windows VMs(like we have) this is not a solution.