Robert, although I appreciate the frustration that has been expressed, I find your posts quite useful. I have tried many of the suggestions proposed by you and others. Unfortunately, I am one of those where there is no 'smoking gun' - no error code and no obvious errors reported in the logs. I am also getting error 0x800f0922 trying to install KB2961908 which may or may not be related - I have a ProcMon trace that I need to analyse.
I am trying to become proficient in using ProcMon. It has a way to trace events early in the boot process which may help identify why the changes are being rolled back, although I wonder if the number of reboots will result in lost trace information. I have contacted the folks at Defrag Tools (they ran a number of tutorials on ProcMon) about using Update 1 as a real-life problem determination case study but have not heard back.
I have a clone of the failing system and plan to try a repair install using a recimg created from a laptop where Update 1 successfully installed. I can also revert the system partition back to April 9th before the trouble happened to see if KB2919355 will install. I suspect the recovery partition on the failing laptop has been corrupted - when I try to create a recovery backup, I do not get the option of including the fully recovery image in the backup. Unfortunately I simply do not have the block of time required to do this testing - I keep hoping Microsoft will pull the rabbit out of the hat.
Now that the cut-off for fixes is once again looming, I am composing a strongly worded email to the Director of Public Relations at Microsoft about the poor communications and support . Microsoft needs to get ahead of this issue before it spirals out of control.