Want to know what really happened? As a Windows Developer, I've put together an explanation of the…
@davepl1968112K followers
264,871 views
9 Comments
Comments from the original post on X (Twitter)

@defaultium
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
32 likes

@davepl1968
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.
7 likes

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

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

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

@davepl1968
What should they use instead?
2 likes

@pokpok
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.
5 likes

@betancour
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.
4 likes

@davepl1968
@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.
14 likes
