KB2919355 (Windows 8.1 Update) Fails (800f0092 and 80073712) on Windows 8.1 Pro w Media Center

     Hard to dispute with the dissatisfaction that many Community members are expressing when the steps outlined in previous posts to this thread fail to correct their issue, especially given the

looming deadline, as non-enterprise users at least are likely somewhat disappointed in the multiple problems in getting KB2919355 to install correctly (providing, of course they have prerequisite updates such as KB2919442 installed, and the appropriate Windows Services are all running). 

     Nevertheless, users determined to eliminate this headache now may wish to attempt the steps for installing KB2919355 on a clean-booted box running only Windows services as outlined by

Thenrik in his May 7 2014 post to page 90 of the thread (as Community Moderator, MVP and renowned patch expert Susan Bradley mentioned on an earlier page, that thread was approaching a "world record" for length - now exceeded by this one's 108 pages) "Windows 8.1 Update 1 Failing to Install with errors 80070020, 80073712 and 0x800f081f".  Given that he reports having performed this successfully on three different builds, it would appear there may be more than mere anecdotal evidence that this approach works; one caution to bear in mind is the reported expenditure of time required, 6-8 hours per machine - which of course reinforces the position of and many other Community members that Microsoft needs to resolve this problem - after all, Windows users have largely come to expect that Windows Update will silently & effortlessly work.  In Microsoft's defense, the volume of notifications I've received about new revisions of KB2919355 would seem to imply that this is the current "hot topic" in the Halls of Redmond (the latest updated package released this week and the fact that the 9 May revision of the accompanying Knowledge base article is the 20th would surely confirm such).

I don't think I attempted the clean boot with the May 5th rendition but I tried it a couple of times with the original to no avail.

I am really surprised, this thread has calmed down so much!?

That is because all people have solved their problema with de 5/5/14 patch, or all have given up?

Not solved here...hopefully MS will call me Monday and be able to resolve it.

A combination of both, I suspect.  There are no new things to try, so we are all left with only the choices to try everything again, reinstall (if we can), or continue to wait and hope there is another patch.