Windows 2012R2: check, ESXi 5.5 Update 2: check, Hardware version 10: check. I patched 4 servers in the same cluster. 2 of them were on a different host that I now see is at 5.5 Update 3, but one was on the same 5.5 Update 2 host and didn’t have the issue, so I guess it’s intermittent. Though it sounds like it’s happening to you every time.
We are in the midst of migrating to ESXi 6.0, thankfully. Thanks, this is good to know. *From:* [email protected] [mailto: [email protected]] *On Behalf Of *Eric Morrison *Sent:* Monday, May 22, 2017 1:53 PM *To:* [email protected] *Subject:* RE: [NTSysADM] Long time for reboot after May patching I have some 2012 and 2012R2 servers running on VMware 5.5u2 and have the exact same issue. I believe it’s because they are hardware version 10. But I’ve confirmed it’s a known bug. I have to go in and hit reset. VM will be fine. I just finished patching this past weekend and have to do this every time until I can complete my migration to Hyper-V. Hit reset and you should be fne. Eric Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10 *From: *Susan E Bradley <[email protected]> *Sent: *Monday, May 22, 2017 12:20 PM *To: *[email protected] *Subject: *Re: [NTSysADM] Long time for reboot after May patching There was a servicing stack update that unless you hit control-alt-delete it would sit there. I would ask myself... self? Do I have a good backup? If I answered yes I would hit a hard reset and see what happens. On 5/22/2017 9:45 AM, Charles F Sullivan wrote: I have a Windows 2012 R2 server that rebooted over 4 hours ago to complete patching and it’s still showing the spinning wheel and the Windows logo. I had 3 others made from the same image that had no issues at all. These are all WMware VMs. I’m not sure if this is the shutdown or startup phase, but I’m guessing startup. Hitting ctrl, alt, del (technically ctrl, alt, insert in the WMware Console) did no good. (I don’t think this is quite the state where that problem applies.) Because there is no network connectivity I feel pretty helpless since I can’t check logs, stop services or send a reboot command. Has anyone else seen this? If so, how long did you wait before you powered off? Or did you not have to? I saw at least one post on the Patch Management list where someone else had the same problem after the May patches. His server came back on its own eventually, but I don’t think it took 4 plus hours. The application is not in use today, which is why they chose it as the patching day, so I probably have another 2 hours before I have no choice but to power off. Thanks.
