I disabled TLS 1.0 and 1.1 on my Windows Server 2016 today. After the restart, I found I couldn't remote back in, but luckily had some remote software to re-enable 1.1 for troubleshooting. Now, my server has been showing 'Getting Windows ready' for about 45 minutes with no updates or progress bar. I'm working on this after hours and really need it up and running by tomorrow morning. I can ping the server and access the console in VMware, so I'm just stuck looking at this blue screen. How long should I wait before hitting the reset button?
5 Answers
Server 2016 really tests your patience! I used to manage Hyper-V clusters with it, and update nights were the worst.
Just a heads up, many folks break RDP by disabling those TLS protocols. It’s a common mistake, just be cautious.
Just so you know, reboots on Server 2016 can take anywhere from 30 minutes to 2 hours when applying updates. Check the logs at \servernamec$windowslogscbscbs.log to confirm if things are still processing. Just be patient and think about upgrading to a newer version if you can!
Lol, you're not alone! I posted here once and then miraculously, after 50 minutes, it went through. It’s stressful, but sometimes you just have to give it time.
I’ve had similar moments. In the background, everything might still be running fine even if that screen appears. I once forced a hard reboot and it came up right away.
Honestly, just hang tight! I've dealt with a few Server 2016 setups that can take ages to restart—once it took 2 hours for no apparent reason. It's frustrating, but sometimes it's just how it goes.
Same here! Every Server 2016 I've worked on seemed to have those long reset times, especially after updates. Switched to 2022 this year, and I haven't looked back.
Yeah, I know the feeling! It’s such a time-sensitive situation; here I am in my work clothes, home and waiting, but I made dinner while stressing over the server!