I just updated 50 Windows 10 machines in a training lab with this KB, and I’ve had zero problems.
Folks are often very quick to blame the OS when the underlying hardware is, in fact, the culprit. Hardware is not infinitely extensible.
I'll bet those 50 Win10 lab machines are fairly similar configurations, or perhaps they are 50 instances of a small number of configurations.
The machines that have trouble with updates are most often individual machines with a one-of-a kind configuration of hardware and software.
In other words, the VAST MAJORITY of consumer machines. The ones to which Win10 updates are pushed and installed with prejudice, and on which the users are typically normal non-geek users.
I'm sure you understand that even if 3/4 of the installed Win10 user base reported no problems, that still leaves over 100,000,000 machines with potential problems. If only 1% of those actually experience problems, that's still a million machines.
IMO, Microsoft is again in the position it was in 20 years ago when it started dictating the hardware and BIOS requirements to run Windows 95. They simply cannot do enough testing on the rapid-release candidates to avoid problems caused by unexpected configurations. Period.
Even the "Insider" track stuff doesn't give them enough feedback.
They need to slow the hell down and stop trying to push out updates so damn quickly.
And they should bloody well stop long enough so that their engineers can catch up and UNDERSTAND what's going on inside the OS. You do recall that famous remark in the wake of the Vista release, where one of their top software folks commented that "No one understands what's going on inside Windows. No one." or something to that effect...