Want to know what really happened? As a Windows Developer, I've put together an explanation of the CrowdStrike IT outage. It covers kernel mode, the driver, how it happened and how to fix it! If you find it interesting please share it!

is it possible to get a comment on this? i look up to you specifically with your intertwining with autism and microsoft windows' development cycle, and to see shit like the concern being raised here really hurts

Well, it could be worse, it could have been a Windows Update! But it wasn't, it was in third party software, so not as painful as it might have been.

Why does Microsoft allow kernel access (by EU regulation apparently) but Apple don’t need to allow access with the MAC?

Say a prayer for the people who have to fix the ones with Bitlocker installed, they are cursing it right now...

That's the technical explanation of the issue. The other part is why so many companies and institutions use CrowdStrike and not something else.

What should they use instead?

Some rookie mistakes in this vid made me look at your credentials a little harder… I did not know you used to run those ”your computer is at risk” scams! WTH dude?! Also found out many of your videos are not exactly truthful either, taking credit from others ppl. Unsubscribed.

Hey Dave, @markrussinovich suggests prioritizing Rust projects over C/C++. How would using Rust in kernel development address this driver-related issue? As far as I understand, the problem lies not in the driver implementation itself but in a file that feeds the driver. The flaw was already present, and the update merely triggered it, metaphorically speaking.

@markrussinovich I'd say a bigger win would be modern C++ usage so that you don't have to learn a new language, like Rust. Master the one you already know. Never allocate memory or use raw pointers, and you're 99% of the way there already.