Re: Microsoft to blame, surely?
> No, I don't know why a virus definition file would need to be embedded in the kernel.
Well, exactly, Microsoft allow this kind of insanity.
So many people are coming to the defence of microsoft with this excuse.
"But yeah, it failed because it's a kernel driver"
As if it is somehow a good idea to allow a third party to add and update a driver in the frikkin kernel on your operating system without you actually bothering to add systems which check it's not going to screw everything up. I don't care how damn complicated or expensive or time consuming it may be to have end-to-end tests checking this shit, even if it takes 24 hours to run them.
It's better than a global outage that will result in billions of lost revenue.
This is ABSOLUTELY the fault of Microsoft, because it's a design flaw in the OS, or rather, it's a design decision that is bat shit crazy.
"Oh, sure, yeah, we trust loads of third party companies to shove kernel driver updates into automatic windows updates, without us checking. What could possibly go wrong?"
"Uh, end to end tests for any updated kernel drivers? No, we can't do that, we have thousands of vendors pushing code. What could possibly go wrong?"
I'm not saying other OS's are immune to this - of course they aren't - but you sure hope there's a level of sanity that prevents a third party from updating your OS at a kernel level without you having any oversight of it.
FFS!