why windows 2008 R2 network adapter needs to be reconfigured after patch update?

[umarzuki]

ESXI 6.0

After auto update of windows 2008 R2, VM detects new card and got APIPA network. Old NIC detected as disabled.

Any KB on this?

[MBreidenbach0]

Well... you're not the only one.

https://www.theregister.co.uk/2018/03/14/microsoft_secures_the_servers_of_the_world/

https://www.reddit.com/r/sysadmin/comments/84cw3n/kb4088875kb4088878_and_vmxnet3/

https://www.reddit.com/r/sysadmin/comments/843w0w/patch_tuesday_megathread_20180313/dvof0z8/

[msripada]

I think its a known issue as per the below Microsoft article

https://support.microsoft.com/en-us/help/3125574/convenience-rollup-update-for-windows-7-sp1-and-win...

Thanks,

MS

[NJKwork]

This fix is a bit confusing to me.  If I run the VBS file on a test machine by itself (without installing the MS patch along with it), it produces the same results as the problematic MS March patch  - it removes the NIC and creates a new one using DHCP.  So how can the fix for the patch cause the same problem as the patch itself?  I tried on two different machines and got the same result - both machines lost the NIC with the static IP information.

Thanks

NK

[NJKwork]

***NOTE*** This worked in MY environment.  Please TEST in non-production before trying anything!!!***

I think I figured out what is going on.  We installed the MS hot fix Windows6.1-KB2550978-x64 on our templates many years ago to address the issue of VMXNET3 adapters incrementing the NIC number when deploying from template: VMware Knowledge Base

If this hotfix is already installed AND I install the March 2018 rollup, I dont have any problems.  No loss of NIC.

On older machines that never had that hotfix installed, I need to run the VBS script first before installing the March rollup - otherwise you lose the NIC.

The problem I had, was I tried to run the VBS script on a machine that already had the KB2550978 hotfix on it - and that caused the NIC to be lost too.

So, if you already have KB2550978 installed...do NOT run the VBS file.  At least for me, it dropped the NIC.  Only run the VBS file if the machines does NOT have the KB2550978 hotfix.

NK

[MohamadAlhousse]

Hi umarzuki​,

Please check the below KB article from VMware,

RUSH POST: Microsoft Convenience Update, KB4088875 and KB4088878 vNIC Incompatibilities - Virtualize...

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.

Regards,

[VishShah]

New Microsoft patches causing Windows VM's with vmxnet3 adapters to lose IP address information.

Heads up that some recent Microsoft patches released appear to lose IP address information for Windows (2008 R2 and 7) virtual machines with vmxnet3 adapters present.

Patches potentially impacting:

• https://support.microsoft.com/en-ca/help/4088875/windows-7-update-kb4088875
• https://support.microsoft.com/en-ca/help/4088878/windows-7-update-kb4088878

External thread(s):

https://www.reddit.com/r/sysadmin/comments/84cw3n/kb4088875kb4088878_and_vmxnet3/

https://www.reddit.com/r/sysadmin/comments/843w0w/patch_tuesday_megathread_20180313/dvof0z8/

https://twitter.com/Sikorsky78/status/973725753421516800

[tdubb123]

is there a MS patch released that will not cause the nic to go offline or removed. I want to keep deploy the ms patches w/o having to manually fix each 2008 vm

[VishShah]

Microsoft admits problem with KB4088875 & KB4088878 and "will provide an update in an upcoming relea...