LATEST UPDATE:
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.MINOR UPDATES:
- Please see Microsoft’s updated guidance and recommended work-around regarding this issue
- I am removing reference to “VMware VMXNet3” in the title of this post to reflect Microsoft’s latest updates to their KB. Yes, the issue still exists when using VMXNet3 for VMs, but it no longer appears that this issue is specific to “VMXNet3” virtual network adapters.
- We are still working with Microsoft to conduct a comprehensive Root-Cause Analysis, and we will provide further updates as new information (or a resolution) becomes available.
Microsoft recently released a “Convenience Update” patch for Windows 7 and Windows Server 2008 R2 SP1. This update has incompatibility issues with virtual machines running on the VMware vSphere virtualization platform. This incompatibility is confined to one specific configuration scenario – It impacts VMs that use the VMware VMXNet3 virtual network adapter type.Here is the incompatibility issue as described in Microsoft’s announcement of the Update:
Known issue 1
Symptoms
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.
ResolutionTo resolve this issue, uninstall the convenience rollup.
Status
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.
VMware is aware of this issue and we are actively investigating the root causes and possible fixes. While this effort progresses, VMware is advising customers to delay applying the Microsoft “Convenience Update” to any virtual machine that uses the VMXNet3 vNIC type.
VMware will provide further updates as they become available.
| Tweet |
Pingback: Windows 7, Server 2008 'Convenience' update is anything but – it breaks VMware networking – The Register | Farmissy
Pingback: Microsoft Convenience Update and VMware VMXNet3 Incompatibilities | Virtual Allan
Pingback: Don't install the new win7/2k8 "convenience" update
Pingback: Microsoft’s Convenience Update breaks VMware VMXNet3 vNICs - Mike Tabor
To avoid rolling back that 479MB Security Rollup convenience package and installing many windows updates.
Until a fix is ‘figured out’. It may be viable to use the device manager show non present devices option in KB315539.
When you select to view “hidden devices” in device manager. This will allow you to see that “old NIC” for uninstall and then you can reconfigure the “new NIC” if it needs it.
It is a hassle and inconvenience to say the least, but at least you won’t have to wait for the roll back removal and re-apply many updates to get up to that level.
Especially if you are building a fresh install or updating a server that has NOT been updated in a while.
Does VMWare know if this occurs once? OR Does it occur after every reboot of the VM?
This happens even after a reboot. Oddly enough this happen on physical servers as well running server 2008, it was not just vmware vms.
As you stated you can view the disabled adapter by selecting the view option, but unfortunately the only two fixes we found was to roll the update back or simply re-enter the ip information.
Fail on MS and VMware imo. Again this did happen on a Dell r610 running server 2008 in our environment, it wasn’t just vms.
Pingback: Microsoft Update – VMxnet3 Uyumsuzluğu | VMware Virtualization Blog
Before applying the Convenience update, change the default alias name of the vNIC to another name, which can avoid the new vNIC to replace the existing vNIC and settings.
For hundreds of servers SunLee? That isn’t a solution – sorry.
Do you have hundreds of servers that have been unpatched for years? You have bigger problems that a rollup patch glitch.
Very annoying indeed. I have to update 300 VM servers next weekend that have never been patched. This update would have cut down on the time by about 90%.
Why wasn’t this tested properly!!!
Please fix in the next few days!
“Why wasn’t this tested properly!!!”
Why are you asking VMW? This is a question for Microsoft as they are the ones who release the faulty patch.
Well, yes and no. It is also VMware’s fault. As a company that has close connections with Microsoft, they didn’t receive any release candidate or something to test out their products to see if any issues?
Good server security you got there!
Hello to all,
if the patch has been applied that can be an issue, but if you will planning to patch your servers then just do not certify this patch, I could not understand why it will be a issue, or wait for the fix from MS.
Hope it will help.
SA
Which KB can i hold/decline via WSUS?
Pingback: VMware vSphere and Microsoft patch roll-up issue - Thomas Duryea Blog
Pingback: How to Disable Windows 10 Upgrade For All Versions
Microsoft information about the issue: https://support.microsoft.com/en-us/kb/3125574
Pingback: MS Update KB312557 & VM 2k8 et W7 avec VMxnet3 : Attention | VroomBlog
I was curious if you ever thought of changing the structure of your
website? Its very well written; I love what youve got to
say. But maybe you could a little more in the way of content so people
could connect with it better. Youve got an awful lot of text for only
having one or 2 pictures. Maybe you could space it out better?
I don’t know if it’s just me or if everyone else experiencing problems with your website.
It appears as if some of the written text within your content
are running off the screen. Can someone else please comment and let me know
if this is happening to them too? This may be a problem
with my browser because I’ve had this happen before.
Kudos
Are you on a desktop, laptop or mobile? It looks ok to me from here.