S
Setsunaaa
This is also happening on 2012 and 2012 R2: Since the November/December update the server gets stuck at "preparing", and shows no percentage.
Today I had this happen with a virtual Server 2016 (running on Server 2016 Hyper-V host) when setting up an Active Directory. What happened? Microsoft decided to download and get updates ready in the background. So when the management console made the reboot required when creating a new AD windows tries to install those as well. Really bad timing, really bad design.
After 20 minutes I did a hard reboot of the virtual server since there was no HDD activity. I this case I was lucky, the AD creation worked fine, and I could install the updates which blocked everything afterwards without issues.
In another case four days ago I wasn't. With a Server 2012 R2 with exchange 2013 installed, and since "F8" got removed I had to hard-kill the server (hard switch off hyper-v console) three times in a row during reboot to make the emergency menu appear, boot up in safe mode, prevent those updates from installing, clear out "SoftwareDistribution", and then it booted up normally again.
Those failures to install updates at shutdown happens in Q4 2016 way too often, specially bad when it happens on a server, this is a nightmare created by Microsoft.
So two things need fixing / changing: Bring back "F8" for servers at least, there is no issue with an extra second wait during reboot. Prevent updates from installing if any role which requires a reboot was changed or any AD setup which requires a reboot was made.
Activating the "legacy" boot option with BCDedit does not Work for Server 2016 / Windows 10 / Server 2012 R2. It does for the other MS-OSes, but not for those three. So please, if you want to reply that, save your time.
Continue reading...
Today I had this happen with a virtual Server 2016 (running on Server 2016 Hyper-V host) when setting up an Active Directory. What happened? Microsoft decided to download and get updates ready in the background. So when the management console made the reboot required when creating a new AD windows tries to install those as well. Really bad timing, really bad design.
After 20 minutes I did a hard reboot of the virtual server since there was no HDD activity. I this case I was lucky, the AD creation worked fine, and I could install the updates which blocked everything afterwards without issues.
In another case four days ago I wasn't. With a Server 2012 R2 with exchange 2013 installed, and since "F8" got removed I had to hard-kill the server (hard switch off hyper-v console) three times in a row during reboot to make the emergency menu appear, boot up in safe mode, prevent those updates from installing, clear out "SoftwareDistribution", and then it booted up normally again.
Those failures to install updates at shutdown happens in Q4 2016 way too often, specially bad when it happens on a server, this is a nightmare created by Microsoft.
So two things need fixing / changing: Bring back "F8" for servers at least, there is no issue with an extra second wait during reboot. Prevent updates from installing if any role which requires a reboot was changed or any AD setup which requires a reboot was made.
Activating the "legacy" boot option with BCDedit does not Work for Server 2016 / Windows 10 / Server 2012 R2. It does for the other MS-OSes, but not for those three. So please, if you want to reply that, save your time.
Continue reading...