Genius move to push an potentially bricking update to every single client machine in one go!
My employer has many millions of embedded (not Windows) devices with updates of one sort or another going out pretty regularly. All of those updates go through some kind of “Canary” phase – deploy to internal alpha/beta, then to a small population, and then rollout to the entire population while monitoring various metrics. It’s not rocket surgery.
Anything that ends up affecting code like bootloaders – where bricking a device is a real possibility – gets huge amounts of care taken over it – everyone’s nightmare is waking up to a slack message from someone you’ve never met before asking you to join an urgent 2am call.
On the one hand, I do feel a lot of sympathy for whoever it was made whatever change it was that did this, and I’m sure it won’t be much fun being that person, or writing the RCA.
On the other hand, they’ve got a huge market cap, and insane valuation so they must have huge amounts of cash sloshing around so surely they could afford to do a better job than they did, and foresee this kind of thing and defend against it?
As a wise old engineer once said to me when I was a young whippersnapper, “If it hasn’t been tested, it doesn’t work”.