On: CrowdStrike Update: Windows Bluescreen and Boot Lo...

[steelframe]

Oh I rebooted, I just didn't happen to have the right configuration options to invoke the failure when I rebooted. Not every dev workstation was bluescreening, just the ones with the particular feature enabled.

[sateesh → steelframe]

But as someone already pointed out, the issue was seen on all kinds of windows hosts. Not just the ones running a specific version, specific update etc.

[martin-adams → steelframe]

That sounds like it was caught by luck, unless there was some test explicitly with that configuration in the QA process?

[dagmx → martin-adams]

A lot of QA, especially at the system level, is just luck. That’s why it’s so important to dogfood internally imho.

And by internally I don’t just mean the development team, but anyone and everyone at the company who is allowed to have access to early builds.

[account42 → dagmx]

There's "something that requires highly specific conditions managed to slip past QA" and then there's "our update brought down literally everyone using the software". This isn't a matter of bad luck.

[jokab → martin-adams]

Maybe thru luck, they're gonna uncover another xz utils backdoor MS version, but its probably gonna get covered up because, Microsoft