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-04-23T03:23:02+00:00

    OK.  After 355 would not install with the 80037312 error,  I restored to a March 29 Restore Point and have completed the first part of step 3 (RestoreHealth) and it returned the following:

                 [==========================100.0%==========================]

                 The restore operation completed successfully. The component store corruption was

                  repaired.

                 The operation completed successfully.

    There is mixed results on this thread with the startcomponentcleanup command.  Some say it causes corruption.  Given the result above, what should my next step be?

    Thanks.  Steve

    The DISM /online /cleanup-image /restorehealth command will always say that the store corruption was repaired, even if there was no corruption.  This just appears to be its normal syntax.

    To be sure, run DISM /online /cleanup-image /scanhealth and it should state "no corruption found".

    I found that on my old image, created before I tried the 355 update, running the startcomponentcleanup DISM command did NOT corrupt the component store.  But the 355 update installs a new version of DISM, perhaps even if the update fails to completely install.  If your March 29 restore point is still clean, you can try the startcomponentcleanup and it should work OK, unless system restore is not restoring the original version of the DISM utility.  To check, the updated version of DISM is 6.3.9600.17031 so if you have the older version in your Windows/System 32 folder you should be safe.

    However, if you end up successfully installing the 355 update, I would stay away from that startcomponentcleanup command as well as Disk Cleanup with system files and windows update checkbox enabled.  Good luck.

    By the way, here is a post explaining this in more detail:

    http://thehotfixshare.net/board/index.php?showtopic=21423&mode=threaded&pid=27090

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2014-04-23T02:53:52+00:00

    (Update (4/16/14):  A couple workarounds have been found to resolve most customers who are receiving this error.  Please first try these steps:

    1)   Open an elevated command prompt.  (Enter command prompt into Search.  In the list of results, swipe down on or right-click Command Prompt, and then tap or click Run as administrator.)

    2)    a) If you’re running a 64-bit version of Windows, enter the following command into the Administrator: Command Prompt window and press the Enter key:

     

    dism /online /remove-package /packagename:Package_for_KB2919355~31bf3856ad364e35~amd64~~6.3.1.14

    b)   If you’re running a 32-bit version of Windows, enter the following command into the Administrator: Command Prompt window and press the Enter key:

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

    c)   If you’re running Windows RT 8.1, enter the following command into the Administrator: Command Prompt window and press the Enter key:

    dism /online /remove-package /packagename:Package_for_KB2919355~31bf3856ad364e35~arm~~6.3.1.14

    3)  Then enter the following commands and press the Enter key after each command:

    DISM.exe /Online /Cleanup-image /Restorehealth

    dism /online /cleanup-image /startcomponentcleanup  

    4)  Run Windows Update again and try to re-install KB2919355

          

    5)  If Windows Update still fails to install the update, Windows 8.1 customers should try to install it manually from the Microsoft Download Center.  You can find the download links here:

        32-bit versions of Windows 8.1: http://www.microsoft.com/en-us/download/details.aspx?id=42327

        64-bit versions of Windows 8.1:  http://www.microsoft.com/en-us/download/details.aspx?id=42335

    6)   If neither of these solutions resolves your error, please contact Microsoft Support so that we can further investigate your issue.  We thank you for your patience and apologize for any inconvenience.

    OK.  After 355 would not install with the 80037312 error,  I restored to a March 29 Restore Point and have completed the first part of step 3 (RestoreHealth) and it returned the following:

                 [==========================100.0%==========================]

                 The restore operation completed successfully. The component store corruption was

                  repaired.

                 The operation completed successfully.

    There is mixed results on this thread with the startcomponentcleanup command.  Some say it causes corruption.  Given the result above, what should my next step be?

    Thanks.  Steve

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2014-04-23T01:55:30+00:00

    For what it's worth.. this worked for me after several days of unsuccessful attempts.

    Disable Internet Explorer 11 from Control Panel - turn Windows features on and off

    reboot

    download and install KB2919355 (not using Windows update)

    computer rebooted and update installed

    using Windows Update select check for new updates- 2 were located KB2933809 and KB2919355 (the file size for KB2919355 was smaller than the original download but I don't remember exact size)

    let Windows Update install the 2 located updates.

    Enable Internet Explorer 11 from Control Panel - turn Windows features on and off

    Windows update history shows KB2919355 is successfully installed

    This fixed it for my case as well!  I had tried everything else re commend to get KB2919355 installed except for uninstalling Internet Explorer 11.  I can't believe that worked, but it did

    Why did uninstalling Internet Explorer 11 before installing KB2919355 solve the issue?  Would turning off any of the Windows features have fixed the problem?

    I managed to complete the updating of KB2919355 successfully after I used Turn Windows Feature On/Off to remove IE 11.  However, I cannot get IE 11 back by turning Windows Feature On again.  Anyone having the same issue?

    I have heard of issues with IE11 after this update was applied.  I don't know what the answer is.  I can say however that when I disabled IE 11 I was STILL not able to install this problematic update.

    Was this answer helpful?

    0 comments No comments