I agree that "bricked" was too strong a word for the problem but if a person did not know how to get out of the BSOD how would they be able to patch the patch? I agree though that for the average person, they may be better off doing automatic updates but I still think "Give me recommended updates the same way I receive Important updates" should be unchecked in settings.
Personally, I wait a week before I do any updates to see how things shake out.
I guess all I'm saying is that I've seen BSOD situations very rarely from an official Microsoft Windows Update, and only rarely has an official Windows update caused me any issues. I've had one during the months since Windows 10 rolled out but that's the only one I remember in years. It was also interesting to see just how quickly the glitchy update that was the original Fall Update (1511) was stopped dead in its tracks by Microsoft when telemetry told them within a few hours that something just wasn't right. Having been a developer (not for Microsoft) for years I am only too familiar with the far-too-common approach of IT management that, "There's always time to do it over, but seldom time to do it right in the first place," when it comes to release deadlines. That's one of the reasons I don't program for a living anymore, I just couldn't stand the endless fire fighting because we were never allowed to delay releases that we developers knew should have waited anywhere from a couple of extra days to, possibly at the extreme, several months before they would actually be "ready for primetime." When the use of telemetry wasn't even in existence yet, you ended up having your entire user base, or close to it, crash and burn and had to try to pick up the pieces afterward. We've come a long way since then in averting meltdown when something gets rushed out that shouldn't have been rushed out.
Seriously, I don't even know where that setting you refer to is located under Windows 10. I've certainly never been able to find anything similar. I know it from Windows 7, and I think it exists in 8/8.1, but Microsoft changed approach with Windows 10 and now the only choices I have are whether to go full automatic or let me schedule restart and whether or not I get updates for other Microsoft products when I get updates for Windows.
No matter which way MS would have gone with this there would have been hell to pay. Windows 10 was still nowhere near to "ready for primetime" at it's July 2015 release date and those of us with a long history with MS knew that this would be the case. But issues have been fixed far more quickly, and sometimes before an update roll-out was anywhere near to complete, than they ever have been before. Having been "on the Microsoft side of the fence" in the past, I can understand entirely why they want to have the OS as "perfectly consistent" as they can across all installations. One of the reasons I always encouraged my clients to apply all critical and important updates was because, in the event that something went wrong and you hadn't, Microsoft's first response when you sought support was, "apply all the updates and see if that fixes it." Often times that did "fix it." The average user is not well-equipped to monitor updates and make decisions on whether to apply them, thus, I get entirely why MS decided to go this route. They did so in the full knowledge that a certain contingent of their users, power users who constitute a tiny minority of their embedded base, were going to be furious. They did a cost-benefit analysis and made their choice.
Edited by britechguy, 13 February 2016 - 12:18 PM.
Brian AKA Bri the Tech Guy (website in my user profile) - Windows 10 Home, 64-Bit, Version 1803, Build 17134
. . . the presumption of innocence, while essential in the legal realm, does not mean the elimination of common sense outside it. The willing suspension of disbelief has its limits, or should.
~ Ruth Marcus, November 10, 2017, in Washington Post article, Bannon is right: It’s no coincidence The Post broke the Moore story