Only Current Build Business (CBB) will be able to delay updates, but not deny updates.
This isn't as big a deal as it sounds... most user like to look, but end up installing everything anyway (Bing and Silverlight were the exceptions and occasionally an AMD driver need to be corrected). Bing isn't an issue any longer, Silverlight is almost dead (I was offered one SL update in March I think).
Since I download and install anyway, why should it matter. Still there's that part of me that refuses to relinquish update control to any vendor. Under normal circumstances it will work well, it's the one off circumstance that bothers me - when things don't work well and I can't connect because my driver was updated. This is rare - I just grab the copy of the driver from storage and I'm back on line.
The only thing left is the occasional AMD driver issues - not to worry about that though ... 10.0.130 can't get it right.
Seriously, MS has a lot riding on Win10 - the device drivers have to work flawlessly or Win10 will go down in flames.
They're working very hard on this and maybe ... probably ... that's why 10.0.130 has the number of driver issues members are reporting.
This position might change, but MS really wants to have all machines running the same level of code to make their lives (development, support, end user confusion, what ever) and really our lives that much easier.
Will people accept that? We'll see if mankind and machines can adapt to changing conditions or go the way of the dinosaurs.
With all the bad updates we've seen lately, I am glad that I have my WU set to "notify only". I usually wait for a week or even 2 before I install WUs. If they take that control away from me (which it appears they are indeed doing) I will be VERY irritated.
With the new update model, that's what the Slow ring will be for. You only get updates when they have been vetted by the fast ring.