I've seen this video and chose not to post it here because like so many news stories, it amplifies things way beyond the reality of most peoples' experience. "Bricked a quarter of all of the systems out there... well maybe not that bad...". Also they do not issue faulty fixes on purpose, which Mister Barnacules says in so many words (It's their fault because.....). Like so many media outlets, he's using shock and outrage to boost his channel. There is another side to the story which I got from a highly placed long time friend who worked for Microsoft for many many years. I'm not going to pass that along since it is essentially internal strategy and tactics.
The net result is what we all see, a decrease in the reliability of builds. How it's happening is secondary. We can hope that they do better in the future. Also we need to keep in mind that the OS technologies that are in use for astronomy (USB, COM) are not heavily used elsewhere in computing. Who else would get hit by a USB interruption at 2AM?? "My mouse froze for 1 second" "So what?" Who else strings long USB cables around with shaky power bricks for DC and not much attention to EMI shielding? One Update error last year affected DCOM, a really obscure OS service which no one uses... but is in ASCOM drivers solely to support the old TeleAPI plugin for TheSky 5/6 which used DCOM 20 years ago for its Internet Automation Software (IAS, long gone). But the WinUpdate DCOM botch affected COM and knocked out a large number of astronomers. It was easy to overcome and MS reversed the goof up in a few weeks with their subsequent update. So astronomy operates on the fringes anyway.
Microsoft is extremely aware of the quality decline at the highest levels, and they know it only takes a few of these sorts of things to permanently damage their position. Furthermore, they are hell bent on supporting the Linux ecosystem. They have really gone all out in this regard.