Not that I don't feel your pain, because I do, but what's happened to you (and the others in the articles you cite) can occur for a multitude of reasons that have nothing to do, at least not directly, with the content of a Microsoft update. That's not saying it isn't a result of that, either, but at least when it is the current use of system health telemetry allows Microsoft to know, and very promptly, that there is some characteristic pattern of malfunction that may not have been seen during their testing. Given the untold millions of computers that are running Windows 10, many of which were never officially certified to do so by their own manufacturers, it is absolutely impossible for Microsoft, or any third party software maker, to test every possible hardware configuration along with installed software configurations that will be encountered "in the wild."
I've been doing technical support for a long time now, and the number of messes I've had to clean up that I felt were clearly the direct result of someone blocking updates because they heard/read somewhere that these cause problems far outnumber the issues I've had to fix that were secondary to an update. Even in those cases where a fix, usually a roll back to a previous restore point, was necessary the update ended up being patched after the problem was identified by enough people calling Microsoft technical support that it could be recognized that a failure pattern was occurring. It took a lot longer in those days to collect enough incidents and with enough specificity to determine that there was a bug or bugs in updates. Now most of that is done via system health telemetry and several different updates, including the major ones, have occasionally had their roll-outs stopped so that an unexpected issue could be fixed before the roll-out continued.
There is no perfect system for doing updates, but letting end users decide, most of whom have absolutely no idea what they're deciding about, has already been proven a recipe for disaster. When you add to that the fact that any software maker, including Apple among others, will ask as the first question when you call support, "Is the system up to date and all updates applied?," the automatic update scheme for Windows Home users in particular makes abundant sense. I've known people who were infuriated when support will not work with them on a problem when they answer, "No," and it ends up taking forever to apply a backlog of updates that never should have been blocked in the first place. You need to have confidence that what you're working with "out there" is as close to what you have to work with in your office when doing support as possible.
It is not accurate to characterize the new update scheme as having to do with "what Microsoft needs." Any, and I do mean any, OS maker expects that you will have the most up to date version of a currently supported operating system installed and most are set up to apply updates, at least what Microsoft used to class as either critical or important updates, automatically as well.
Were I in your shoes I would follow the progression I've given you until you have reached a stable state on your system. That advice is, of course, predicated on the presumption that your hardware is certified for Windows 10 in the first place. If it isn't that is a whole different can of worms. You may need to reinstall some specific device drivers if you have "odd pieces" of hardware as part of your computer. On my laptop, for instance, there is an AMD utility that monitors the device drivers for the AMD components and updates them as necessary. It will override what Windows might choose if, by chance, the database Microsoft is using has not yet been updated and an older driver ends up being installed by Windows update.
Edited by britechguy, 20 March 2017 - 12:17 PM.