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

Anonymous
2014-04-05T00:19:46+00:00

I am running Windows 8.1 Pro with Media Center. It is a 64-bit edition.

I downloaded the Windows 8.1 Update from MSDN. Installed it on two machines with no problems.

Update is a series of 6 updates packed in a single zip file. Unzipped the files. Went to install the first recommended update (KB2919442). Dialog box indicated it was already installed.

Went to install the second update (KB2919355). It ran through the dialogs and said installation completed. It indicated that a reboot was necessary. Rebooted. It began to install the update after the reboot. Got about 60% of the way through, then said it couldn't complete. Error message 800F0092.

Had successfully installed on two other machines, one a VM and one a Samsung tablet. Only difference is this computer is 1) Media Center, and 2) was running WebRoot antimalware agent.

Uninstalled WebRoot.

Retried the install. Got about 98% through the dialog (green progress bar almost at 100%), went it stopped and the dialog said Update Failed.

Error message in the update history is now 80073712.

Windows for home | Previous Windows versions | Install and upgrade

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments
Answer accepted by question author
Anonymous
2014-05-14T20:02:09+00:00

Hello all,

We wanted to take a moment to thank you for coming to the Microsoft Community to get the answers you need tosuccessfully install the Windows 8.1 Update.

We have published guidance for troubleshooting some known problems at*Install the latest Windows 8.1 Update*.

In order to give your questions the attention they deserve, we are opening new threads that will focus on solving each error individually:

If you are receiving the error ‘We couldn’t complete the updates, Undoing changes. Don’t turn off your computer’ please post to this thread foundhere

If you are receiving Error 0x800F0922 when installing KB 2919355 please posthere

If you are receiving Error 0x800F0923 when installing KB 2919355 please posthere

If you are receiving Error 0x80070003 when installing KB 2919355 please posthere

If you are receiving Error 0x80070005 when installing KB 2919355 please posthere

If you are receiving Error 0x80070490 when installing KB 2919355 please posthere

If you are receiving Error 0x80073712 when installing KB 2919355 please posthere

If you are having an issue not mentioned above, please*start a new thread*so that we can investigate your issue.

In order to keep these threads productive and prevent fellow customer’s questions from being lost we ask that you please keep any posts made to these threads on topic and constructive.

We are going to go ahead and lock this thread to prevent questions being posted in the wrong area and not getting the attention they deserve.

Thank you for your understanding

Was this answer helpful?

60+ people found this answer helpful.
0 comments
Answer accepted by question author
Anonymous
2014-04-17T17:17:17+00:00

Please note that's 64bit only

To make that work on 32bit do:

Also note AMD does not mean this only works on AMD chipsets.  AMD invented the 64bit platform, so even if you are running 64bit intel, that amd64 notation is still valid.

sfc /scannow

DISM /online /get-packages /format:table | findstr KB2919355

DISM /online /remove-dism /online /remove-package /packagename:Package_for_KB2919355~31bf3856ad364e35~x86~~6.3.1

DISM /Online /Cleanup-Image /ScanHealth

DISM /Online /Cleanup-Image /RestoreHealth

DISM /online /cleanup-image /startcomponentcleanup /resetbase

cleanmgr.exe

@echo off

Echo Cleanup complete

pause

Was this answer helpful?

50+ people found this answer helpful.
0 comments

1,164 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2014-05-03T15:06:24+00:00

    Hi Dazed&Confounded,

    I'm with you, for those having to struggle with this failed update on a Microsoft (stock) Surface, it's even worse!

    At least this is a clear example that the reason of this failure totally comes from Microsoft updates, this time they cannot say that it's OEMs' fault...

    Totally agree.  Of my four computers, the only one that did not take the 355 upgrade was my stock Surface Pro 2 purchased in Dec 2013.  After about a week of following this forum I was able to get the upgrade thanks to the advice posted by several of the experts here.

    BTW: The other three OEM computers, originally upgraded from Windows 7, all upgraded automatically to 355 as they should, including a little Acer netbook that I gave to my grandkids after I bought the Surface.  Point being, they were not aware, nor did they care that there had been a critical update.  They just expect things to work.  Might be a lot of other users unaware and surprised down the road. 

    I'm 76 and have been a Microsoft customer for a long time because I never had a problem with the product.  After the recent 355 fiasco, and several earlier issues following the original upgrade from 8.0 to 8.1, I am paranoid and have to check each computer every morning to see what may have gone wrong overnight.   It's like driving an older car that has failed a couple of times in heavy traffic.  You lose faith and start thinking it's time for change.

    Thanks for listening.

    BTW2:  The Bluetooth keyboard on the Surface sucks.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2014-05-03T12:51:01+00:00

    Hi Dazed&Confounded,

    I'm with you, for those having to struggle with this failed update on a Microsoft (stock) Surface, it's even worse!

    At least this is a clear example that the reason of this failure totally comes from Microsoft updates, this time they cannot say that it's OEMs' fault...

    Was this answer helpful?

    0 comments
  3. Anonymous
    2014-05-03T12:00:44+00:00

    I have a Microsoft Surface Pro and Microsoft automatically failed to install KB2919355 on 21 April, then on 26 April, twice on 28 April, and three times on 29 April. Then I had a message on the startup screen that told me there is an issue - I was blissfully unaware until then! Since then it has failed to install again on 29 April, three times on 30 April, once on 1 May, and four times today....

    What issue?

    Try posting in this Surface Pro-specific forum for assistance: http://answers.microsoft.com/en-us/surface/forum/surfpro-surfupdate 

    PA Bear

    I do hope that you're joking! Regardless, it seems sensible to me to stay with a thread that is concerned with people's inability to get update 1 rather than be diverted to another thread that may quietly fizzle out. I would hope that after so many posts on this thread that Microsoft sit up and take notice. Other posts here refer to the Surface Pro so it seems like a good place to be.

    Over the years it appears that pc's can have so many permutations of all of their component gubbins that they can be faced with a particular permutation that needs a particular fix. In my case I have a stock Surface Pro that has plenty of space on it and I haven't got the wit to do anything like create a new partition etc.

    What I find particularly galling is that MS automatically updated my (stock) SPro, it has tried many more times, I have tried a few more times, I have no idea what all of these attempts have done to it, yet MS tells me that if I have not updated by May 13 then I will not have any more of their fixes or tweaks (which ironically might be a good thing if they cause all of this angst).

    I find it odd that this issue isn't more prevalent in the media but even stranger that MS didn't get it right for their own hardware.

    Forgive me but I'm not in a joking mood at this moment.

    Was this answer helpful?

    0 comments