We have a new patch. Install this patch immediately. Whoops, we were just made aware of a bug in that patch, but here is a patch for the patch. Update it immediately. Whoops, guess what? The patch of the patch needs a patch, and as soon as it's available you need to update it immediately."
For any machines you personally use with Windows 10, do you utilize any temporary update blocking/delaying measures, and have they been helpful in heading off ~fixes of fixes~?
Excellent question.
I have two Win10 computers (VMs actually) -- one at work that is part of the company AD domain, and one at home for personal use.
The work VM, being tied to the AD domain, is under control of Corporate IT (of which I'm a member). We have an in-house WSUS server that proxies the updates, and we have a 3-stage process when updates are released. First, we test the updates on a couple "safe" crash-box machines that exist solely for that purpose. Second, we roll out the updates to a few selected "Early Adopter" employees who have bravely volunteered to be guinea pigs. Finally, we roll out the updates to the rest of the company, including my work VM. Problems at any of those stages cause an immediate stop to investigate the issue.
The personal VM at home is only used occasionally, so I generally keep it turned off unless I need to use it. As a result, I can wait until the work computers have been updated and things look good, before firing up the home VM and letting it update from the internet.
Nothing has actually improved for typical users since XP, IMHO.