I'm wondering if anyone else has run into issues with Windows 2019 servers, especially on AWS, becoming unresponsive after updating to Crowdstrike version 7.27 over the last day. We've encountered this with four of our AWS instances running Windows 2019. They stopped responding to RDP and all the services they were running. Oddly enough, I could still perform TCP connection tests, such as checking the RDP port, but the RDP connection just wouldn't work. We ultimately had to forcibly stop and restart these servers to regain access.
3 Answers
We've noticed similar issues, but thankfully it only impacted one of our older Windows Server 2012 R2 setups. It seemed localized, not widespread like you mentioned.
I had a 2016 server on an on-prem Hyper-V that faced the same problems. It was completely unresponsive to RDP, PowerShell Remoting, and even remote monitoring tools. I couldn't do anything through the console either, but it still responded to pings. A hard reset was needed to get it back online.
Sounds like a kernel-level glitch. It’s strange that TCP connections were open but RDP wouldn’t budge. I had similar symptoms but with pings disabled, so I had to tackle it differently.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures