The problem appears to afflict machines configured with static IP addresses.
During the installation of the update the NIC is replaced by another configured for DHCP, potentially knocking the machine off the network.
Administrators are reporting that rectifying the problem requires a little more effort than simply switching back from DHCP since the original NIC may still be present, just hidden.
Microsoft has remained tightlipped on the issue, leaving it to users to work out what part of the update borked their carefully crafted networks.
It seems that the latest MS patches ate my vmxnet3 adapters on Windows 2008R2 . Any one else?#WindowsUpdates #Windows2008R2 #VMware pic.twitter.com/fsOwTo2VVx
— Wouter Hindriks (@Sikorsky78) March 14, 2018