Just checked my machines on Azure. They’re all okay—because I stopped and deallocated them to turn off billing, LOL! I still use them to teach classes, but I’m not teaching this month. Also, I don’t use Hillary’s Crowdstrike crap.
Meanwhile, on Service Health Emerging Issues page is the following (with a fix proposed):
Emerging issues
1 issue
Awareness - Virtual Machines
We have been made aware of an issue impacting Virtual Machines running Windows Client and Windows Server, running the CrowdStrike Falcon agent, which may encounter a bug check (BSOD) and get stuck in a restarting state. We approximate impact started around 19:00 UTC on the 18th of July. Additional details from CrowdStrike are available here: Statement on Windows Sensor Update - crowdstrike.com Update as of 10:30 UTC on 19 July 2024: We have received reports of successful recovery from some customers attempting multiple Virtual Machine restart operations on affected Virtual Machines. Customers can attempt to do so as follows: Using the Azure Portal - attempting ‘Restart’ on affected VMs Using the Azure CLI or Azure Shell (https://shell.azure.com) https://learn.microsoft.com/en-us/cli/azure/vm?view=azure-cli-latest#az-vm-restart We’ve received feedback from customers that several reboots (as many as 15 have been reported) may be required, but overall feedback is that reboots are an effective troubleshooting step at this stage. Additional options for recovery: We recommend customers that are able to, to restore from a backup from before 19:00 UTC on the 18th of July. Customers leveraging Azure Backup can follow the following instructions: How to restore Azure VM data in Azure portal Alternatively, customers can attempt repairs on the OS disk by following these instructions: Troubleshoot a Windows VM by attaching the OS disk to a repair VM through the Azure portal Once the disk is attached, customers can attempt to delete the following file: Windows/System32/Drivers/CrowdStrike/C00000291*.sys The disk can then be attached and re-attached to the original VM. We can confirm the affected update has been pulled by CrowdStrike. Customers that are continuing to experience issues should reach out to CrowdStrike for additional assistance. Additionally, we’re continuing to investigate additional mitigation options for customers and will share more information as it becomes known.
Oh please, don’t even get me going on “Cloud” technology. The only reason for keeping things in the “cloud” is so someone else can control your data, your computing experience. I’ve always been an advocate for keeping my data close at hand, locally on an external storage device. I also keep that data safely kept ina Faraday bag/container. This is just a foreshadow of things to come. Trust me on that.