Yes! So a vanilla install of 16 probably has this critter under the surface waiting to bite us.
Sent from my iPhone On May 22, 2017, at 4:42 PM, Susan E Bradley <[email protected]<mailto:[email protected]>> wrote: https://support.microsoft.com/en-us/help/3020369/april-2015-servicing-stack-update-for-windows-7-and-windows-server-2008-r2 Known issues for this update Restart stuck on "Stage 3 of 3" After you install update 3020369 together with other updates, a restart may be required to complete the installation. During this restart, you may find yourself stuck on "Stage 3 of 3." If you encounter this issue, press Ctrl+Alt+Delete to continue to log on. This should occur only one time and does not prevent updates from installing successfully. On 5/22/2017 12:20 PM, David McSpadden wrote: Since about Novemember last year one of the patches (I have not figured out or researched which) just sits at either 30% or Welcome. Pressing Ctrl+Alt+Del ‘unfreezes the spinning disc of death and things progress nicely after that. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Charles F Sullivan Sent: Monday, May 22, 2017 3:10 PM To: [email protected]<mailto:[email protected]> Subject: RE: [NTSysADM] Long time for reboot after May patching Notice: This email is from an outside source. Please do not open any attachments, click on any hyperlinks, or respond without first confirming the authenticity of the email. So after 7 plus hours the spinning beads began to make me dizzy. I powered off the VM, powered it on and checked. All of the patches installed successfully. There was absolutely no mention of badness in the Event Logs. No unexpected shutdown or dump file. There was a gap in all of the logs from 7:21 to 14:23. The last one in the System Log was, as expected, “The system is shutting down at 7:21”. It’s as if the server wasn’t really running even though it also wasn’t shut down. None of this surprises me much, but it’s a critical server so I didn’t want to take a chance. It runs a parking revenue application, but today is commencement day so they left the arms up on the parking machines. Thus I had all day to get it done. From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Susan E Bradley Sent: Monday, May 22, 2017 1:14 PM To: [email protected]<mailto:[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. This e-mail and any files transmitted with it are property of Indiana Members Credit Union, are confidential, and are intended solely for the use of the individual or entity to whom this e-mail is addressed. If you are not one of the named recipient(s) or otherwise have reason to believe that you have received this message in error, please notify the sender and delete this message immediately from your computer. Any other use, retention, dissemination, forwarding, printing, or copying of this email is strictly prohibited. Please consider the environment before printing this email. This e-mail and any files transmitted with it are property of Indiana Members Credit Union, are confidential, and are intended solely for the use of the individual or entity to whom this e-mail is addressed. If you are not one of the named recipient(s) or otherwise have reason to believe that you have received this message in error, please notify the sender and delete this message immediately from your computer. Any other use, retention, dissemination, forwarding, printing, or copying of this email is strictly prohibited. Please consider the environment before printing this email.
