Update KB4057903 has a bug
Exchage within a Hyper-V VM with Windows Server 2012 r2: Update KB4057903 leads to an almost unresponsive server. I could reproduce the behaviour twice by deinstalling the update. Please, provide a new version of KB4057903 without the bug. Thanks.
See also the discussion in https://social.technet.microsoft.com/Forums/windowsserver/en-US/387da0db-6046-4838-9db7-c8ddcb6810da/update-kb4057903-fails-in-windows-server-2012-r2-hyperv?forum=winserverhyperv
KB4057903 and KB4072650 are detected to be needed by this WSUS server that we have.
Of course I have tryed to install them but after reboot nothing happens....these two updates are still detected as needed.
I don't have run or ever run Exchange on this WSUS server.
Also, this WSUS server it's an VM machine hosted on Hyper-V 2016 Core edition
Microsoft ...please fix this.
Phuong, Nguyen Van commented
I have problem with two KB4057903 and KB4072650 My Exchange 2016 start hung
I never patch VM's now without taking a checkpoint first and after updates are completed and confirmed all is good I delete the checkpoint.
This update put our VM in a perpetual reboot loop. We had to restore from backup.
The problem still exists, just killed an Exchange 2016 server because of this.
Klaus Jakobsen commented
This problem still exist. Why isn't anyone from Microsoft reading these messages?
ame problem with me, the update KB4072650 try 3 time to install is self, after the tird , my server as been rolling back.
Question: Do I need to install the KB4057903 before installing KB4072650, because I hide this marvellous update KB4057903. (Sarcasm)
I realy do not like patching tuesday!!!!
- VM Host Server 2016
- Guest VMs: Server 2012R2 with Exchange 2016 DAG
After installing update the server needs 15 minutes to show login screen.
The exchange services don't work - everyting so slow.
After deinstalling KB4057903 everyting is fine again.
Try to use workaround (disable exchange services before installing update) later.
Update installed and destroyed the hyper-v network adapter. No network on DC means a long startup time for windows. Managed to repair by removing adapter from hardware list and reinstalling using integration services
M$ fix your patches before releasing. Putting a lot of money in SAM to sell more licenses instead of cleaning the mess you did.
We have it too on W2012R2 HyperV VMs WITHOUT any Exchange services running.
In my case the update fails to install. It will revert the installation to before the update after reboot. This happened on a non exchange server.
Had the same problem twice on 2012r2. Only one of the servers is an exchange server.
This happens also on W2012R2 HyperV VMs WITHOUT any Exchange services running.
Had the same problem, Installed KB4057903 system was unresponsive after that, Had to boot into safe mode and uninstall and server came back. 2012r2 with exchange 2013