CrowdStrike fixes start at “reboot up to 15 times” and get more complex from there

This underscores what a terrifying responsibility it is to push out updates. I'm basically shaking when we push out updates to our product, especially because iOS/Android deployments are essentially impossible to debug. At least on desktop, we can get people to go delete a file. We can't even do that on mobile. We rely on a witches brew of safe modes.

I can't tell if CrowdStrike were sloppy in their testing. But in all likelihood, they just tested on systems that were a little too perfectly configured, and when it hit the real world, it exploded. And maybe their rollout wasn't tiered enough.

My sympathies. Having your code be a core driver on many of the world's systems is as awesome as that responsibility can get.
 
Upvote
430 (444 / -14)
It really feels like even just… a moderately passable attempt at best practices with update deployments could avoid all of this? There’s no way all these major enterprises are installing software that can just update itself without telling anybody, right?

Which would mean that somebody, somewhere at most of these companies pushed play on the update without installing it on so much is a single test box first?

Either that, or it was more of a Trojan thing where the issue didn’t start popping up for a while after the update?
 
Upvote
30 (74 / -44)

peterford

Ars Praefectus
4,014
Subscriptor++
At about 3:30pm my admins got me to bypass bitlocker, log on as an admin in safe mode and rename the file. Oddly explorer failed every time I clicked to rename - so I ended up using CMD.exe.

Took about 20 minutes as they knew my bitlocker bypass key. This is a solution that scales horribly.

Funnily enough, today was the best weather of the year so far. Terrible shame for an end user like me. Terrible, terrible shame :)
 
Upvote
301 (304 / -3)

marsilies

Ars Legatus Legionis
23,258
Subscriptor++
Yes the formatting breaks on mobile too
I don't think it's a formatting issue, as the dash in the filename is missing on desktop as well, and as far as I can tell, also in the source.

The "<code>" formatting for the filename is causing a line break, but that's less of an issue than the filename being incorrect.
 
Upvote
29 (29 / 0)
Post content hidden for low score. Show…

LlamaDragon

Ars Centurion
277
Subscriptor++
"Hello, IT. Have you tried turning it off and on and off and on and off and on and off and on and off and on and off and on and off and on and off and on and off and on and off and on and off and on and off and on and off and on and off and on and off and on again?"

Edit: Oops, missed the original several posts up. I'm glad we're all on the same page though. :)
 
Upvote
198 (206 / -8)

iljitsch

Ars Tribunus Angusticlavius
9,000
Subscriptor++
This underscores what a terrifying responsibility it is to push out updates.
Indeed. I've been burned in many much more minor ways by updates and am now extremely reluctant to install any. That's probably too conservative, but where is the sane middle ground??

One thing is for sure: all your eggs in one basket saves on basket costs, but you pay for it dearly at some later point.
 
Upvote
64 (65 / -1)

Fatesrider

Ars Legatus Legionis
22,941
Subscriptor
Microsoft's Azure status page outlines several fixes. The first and easiest is simply to try to reboot affected machines over and over, which gives affected machines multiple chances to try to grab CrowdStrike's non-broken update before the bad driver can cause the BSOD. Microsoft says that some of its customers have had to reboot their systems as many as 15 times to pull down the update.

Is it just me, or did anyone else read this and flash back to the time when their dad kept banging on the side of the old CRT TV's to get it to show a picture?
 
Upvote
106 (107 / -1)

markgo

Ars Praefectus
3,174
Subscriptor++
"We understand the gravity of the situation and are deeply sorry for the inconvenience and disruption," wroteCrowdStrike CEO George Kurtz

“I have returned my bonus from last year and have dedicated the company’s financial reserves to make all affected customers whole again”, he continued.

/jk
 
Upvote
280 (280 / 0)
It really feels like even just… a moderately passable attempt at best practices with update deployments could avoid all of this? There’s no way all these major enterprises are installing software that can just update itself without telling anybody, right?

Which would mean that somebody, somewhere at most of these companies pushed play on the update without installing it on so much is a single test box first?

Either that, or it was more of a Trojan thing where the issue didn’t start popping up for a while after the update?

Best practices fail…for the win!

Too cheap, too lazy, too understaffed, too undertrained; take your pick or the combo meal.

I built a website for a local NPO last year, and wrote them a detailed change control guide and why SSL was not an option, and so on. They have some smart people, including several IT pros. I figured “they got it”. I did wonder if webmaster by committee was a blessing or a curse.

Their entire membership list and passwords were published online last week.

Curse it is.
 
Upvote
93 (96 / -3)