The Windows ecosystem typically deployed in corporate PCs or workstations is often insecure, slow, and poorly implemented, resulting in ongoing issues visible to everyone. Examples include problems with malware, ransomware, and Windows botnets. In corporate environments, IT staff struggle to contain these issues using antivirus software, firewalls, and proxies. These security measures often slow down PCs significantl…
CrowdStrike Update: Windows Bluescreen and Boot Loops
741–750 of 1001 posts
Re: CrowdStrike Update: Windows Bluescreen and Boot Loops
#742When you see the size if the impact across the world, the number of people who will die because hospital, emergency and logistics systems are down… You don’t need conventional war any more. State actors can just focus on targeting widely deployed “security systems” that will bring down whole economies and bring as much death and financial damage as a missile, while denying any involvement…
Re: CrowdStrike Update: Windows Bluescreen and Boot Loops
#743Re: CrowdStrike Update: Windows Bluescreen and Boot Loops
#744Re: CrowdStrike Update: Windows Bluescreen and Boot Loops
#745Why are so many mission critical hardware connected systems connected to the internet at all or getting automatic updates? This is just basic IT common sense. You only do updates during a planned outage, after doing an easily reversible backup, or you have two redundant systems in rotation and update and test the spare first. Critical systems connected to things like medical equipment should have no internet connecti…
This update bypassed all of those settings.
Re: CrowdStrike Update: Windows Bluescreen and Boot Loops
#746It's not the first time they pull something similar...1 month ago: "CrowdStrike bug maxes out 100% of CPU, requires Windows reboots" - https://www.thestack.technology/crowdstrike-bug-maxes-out-10... 75 Billion dollars valuation, CNBC Analysts praising the company this morning on how well the company is run!...When in reality they can't master the most basic of the phased deployment methodologies known for 20 years...…
Re: CrowdStrike Update: Windows Bluescreen and Boot Loops
#747Re: CrowdStrike Update: Windows Bluescreen and Boot Loops
#748Took down our entire emergency department as we were treating a heart attack. 911 down for our state too. Nowhere for people to be diverted to because the other nearby hospitals are down. Hard to imagine how many millions of not billions of dollars this one bad update caused.
We were discharged at midnight by the doctor, the nurse didn't come into our exam room to tell us until 4am. I can't imagine the mess this has caused.
Re: CrowdStrike Update: Windows Bluescreen and Boot Loops
#749It's not the first time they pull something similar...1 month ago: "CrowdStrike bug maxes out 100% of CPU, requires Windows reboots" - https://www.thestack.technology/crowdstrike-bug-maxes-out-10... 75 Billion dollars valuation, CNBC Analysts praising the company this morning on how well the company is run!...When in reality they can't master the most basic of the phased deployment methodologies known for 20 years...…
I'll take it a step further and say that every industry is depressing when it comes to computers at scale.
Rather than build efficient, robust, fault-tolerant, deterministic systems built for correctness, we somehow manage to do the exact opposite. We have zettabytes and exaflops at our fingertips, and yet, we somehow keep making things slower. Our user interfaces are noisier than ever, and our helpdesks are less helpful than they used to be.
Re: CrowdStrike Update: Windows Bluescreen and Boot Loops
#750When you see the size if the impact across the world, the number of people who will die because hospital, emergency and logistics systems are down… You don’t need conventional war any more. State actors can just focus on targeting widely deployed “security systems” that will bring down whole economies and bring as much death and financial damage as a missile, while denying any involvement…
Considering PR review is usually done within the team. A state actor can simply insert a manager, a couple of senior developers and maybe a couple of junior developers into a large team to do the job. Push something in Friday so few people bother to check, gets approved by another implant and here you go.
All people can then leave leisurely.