4 ms·
>1. Microsoft themselves could potentially enforce a gradual rollout on updates (did the update go through windows updates?) No. The crash was caused by a "con
by gruez 2y ago
>1. Microsoft themselves could potentially enforce a gradual rollout on updates (did the update go through windows updates?)
No. The crash was caused by a "configuration update", not through code pushed through windows update.
https://www.crowdstrike.com/blog/falcon-update-for-windows-hosts-technical-details/ https://www.crowdstrike.com/blog/falcon-update-for-windows-h...
>2. Have better automatic recovery options, could windows have detected the bad driver and reverted it automatically?
see: https://news.ycombinator.com/item?id=41019743 https://news.ycombinator.com/item?id=41019743
>3. just generally be more resilient, why should one bad driver take everything down?
It's kernel mode. With great power comes great responsibility. Blaming the OS is like blaming linux that you can sudo rm -rf /.