network setting changed from static ip to DHCP after install patch kb4088875 and kb4088878

network setting changed from static ip to DHCP after install patch kb4088875 and kb4088878
 

Question Info


Last updated September 11, 2019 Views 7,270 Applies to:
Reply In reply to deleted message
yes,we have issue after install kb4088875 and kb4088878 on windows server 2008 r2

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Reply In reply to deleted message
hello ,could you please help me

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

I have this issue too. Any attempt to reset network config fails. 

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

This is a problem with VMware vmxnet3 adapters on Windows 2008R2. The adapter settings are being removed by the security patch.

DO NOT INSTALL KB4088875 or KB4088878 UNTIL MICROSOFT ADDRESSES THIS ISSUE

In the "Known Issues" section of KB4088875 Microsoft states:

IP address settings are lost after applying this update. Microsoft is working on a resolution and will provide an update in an upcoming release.

(See https://support.microsoft.com/en-us/help/4088875/windows-7-update-kb4088875)

See also these news threads about this problem:

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

https://www.techrepublic.com/article/microsofts-windows-server-2008-r2-patches-took-some-servers-offline/

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

To fix your problem it depends on whether your server subnet has DHCP scopes enabled (in which case your server was just given a new IP address and probably re-registered in DNS and you DON'T EVEN KNOW YOU HAVE A PROBLEM). If you don't have DHCP scopes you server was given a 169.x.x.x IP address by the built-in resolver in Windows and you HAVE NO NETWORK CONNECTIVITY. You will need to launch a console session from vCenter to update the network adapter to the previously set static IP address, subnet mask, and default gateway.

Hey Microsoft, when will you fix KB4088875?

6 people were helped by this reply

·

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.