We have been informed by VMware with regard to this issue and this is going viral all over the world after the patch updates comes under KB4088875 and KB4088878. This is basically affecting to the Windows 2008 R2 and Windows 7 Virtual Machines with VMXNET3 adapters. VMware is currently investigating and working in their full scope to find a solution for this serious issue. If you are planning to update your Patches please make possible effort to avoid these patches from your List.
You might be getting similar errors if you have DHCP configured
Note: As of right now, VMware & Microsoft do not have official comments or updates as this is relatively new information coming in from the public
As per the feedback we are getting from social media some had to upgrade the Virtual Hardware levels and some had to add the IP information again to those affected Virtual Machines. If you come up with anything different to these steps please feel free to comment on this so we can share it with others.
Another workaround to fix this issue was remove the NIC and re-adding to the Virtual Machine, also reinstalling the driver was one of the workarounds, but at this point there is no guarantee of any of these workarounds to fix your issue. Just try and see.
Please keep your eyes on below external links to get the latest updates, I will update the post as I’m getting the information:
Official Update From VMware (as of 15/03/2018):
Provided Action Plan: If you have been impacted, please note that the following manual fixes have been known to resolve the issue (after the fact):
- Note the name of the new network adapter
- Open “Device Manager” -> “Show Hidden Devices” and delete ALL hidden/phantom network adapters from the list (be sure to NOT delete the drivers)
- Edit the properties of the new NIC and add the applicable IP address configuration. No reboot is required
Please click here to follow the official update.
LATEST UPDATE FROM VMWARE:
VMware has received confirmation that Microsoft has determined that the issue reported in this post is a Windows-specific issue and unrelated to VMware or vSphere. Microsoft is encouraging customers to follow the directions provided in Microsoft KB3125574 for the recommended resolution. All further updates will be provided directly by Microsoft through the referenced KB. This marks the end of further updates to this blog post.
If you found this post as useful please rate the post and share it!