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 No 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 No 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 No comments

1,164 additional answers

Sort by: Most helpful
  1. Anonymous
    2014-05-05T18:48:54+00:00

    Susan is a star. Through her I have been contacted by an MS engineer who has managed to get update 1 installed on my SPro. I have sent Susan details of what seems to have been done to my SPro via remote access and hopefully she will be able to translate it into language that will make sense for all others here.

    A most unusual step was that when I needed to reboot the engineer insisted that I shut down and then start up again - he was explicit that 'update and restart' is to be avoided after doing some DISM things.

    Many thanks to all that have contributed to this forum. I sincerely hope that all others still to get this update to work will do so soon.

    I'll be disabling my automatic updates around July just in case

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2014-05-05T18:46:37+00:00

    Dave, I agree with all you say, but with one exception:  you say, "Why, of almost all Microsoft products, does only Windows Update tell you nothing about what actually went wrong?", but in my experience, the most common error response from *any* Microsoft (or other) software application is, "<<big hex number>> An unexpected error has occurred."  Really, now.

    LOL!  :-D

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2014-05-05T18:41:23+00:00

    One question I'd like to ask anyone involved in Windows Update: Why are the diagnostics from Update so totally useless? They tell you absolutely nothing about what's gone wrong.  Back when I was a student, a friend of mine created an app that, mostly as a joke (or possibly just because he was lazy), when it failed, printed "Bang" and exited. That's how WU fails, it throws up a dialog box that says "Bang" and then exits. The only step you can take beyond this is to plug the message into Google, which turns up dozens of threads from other people who have had the same "Bang" error code and don't know what to do either.

    Looking at some of the nearly 1000 posts here, it looks like people are having to resort to finding causes using Windows Internals tools and debuggers, when Windows Update knows exactly why things failed. The update doesn't fail because wuauclt.exe has a headache, it fails for a very specific reason, and Windows Update knows what it is, but all it displays for the users is "Bang". Why, of almost all Microsoft products, does only Windows Update tell you nothing about what actually went wrong?

    The bottom line is that they honestly don't care.  All they care is about the profit however in the long run there will be no more profit and by that time it will be too late.

    Was this answer helpful?

    0 comments No comments