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-04-23T00:18:26+00:00

    This sounds extremely dangerous for a person that is not a professional. What is the consequence of doing nothing?

    Ya think Microsoft will have a fix?

    Was this answer helpful?

    0 comments
  2. Anonymous
    2014-04-23T00:06:57+00:00

    You could try booting to recovery mode (f8 at windows start and select the first option repair) then select troubleshooting->command prompt and run the following:

    First type DISKPART

    Then you will be at a prompt that says DISKPART> Type list volumes, it should list several. Look for the largest volume on the list, it might be E, C, or D but it will not be X.

    type EXIT

    Then type the following:

    DISM /Image:(Drive letter from previous step): /Remove-Package /PackageName:Package_for_KB2959977~31bf3856ad364e35~amd64~~6.3.1.1

    DISM /Image:(Drive letter from previous step):\ /Cleanup-Image /RevertPendingActions

    So the commands should look like this:

    DISM /Image:E: /Remove-Package /PackageName:Package_for_KB2959977~31bf3856ad364e35~amd64~~6.3.1.1

    DISM /Image:E:\ /Cleanup-Image /RevertPendingActions

    This should clean up any corruption within the component store, but your mileage may vary.

    THE FOLLOWING COMMANDS ARE POTENTIALLY VERY DANGEROUS. RUN AT YOUR OWN RISK

    First, from within windows, check c:\Windows\WinSxS\ Scroll to the bottom of the list, if there are a bunch of pending.xml files (they be called something like pending.xml72743278gh) if you see these files, do the following:

    From the command prompt in recovery mode (see previous step on accessing this)

    First type DISKPART

    Then you will be at a prompt that says DISKPART> Type list volumes, it should list several. Look for the largest volume on the list, it might be E, C, or D but it will not be X

    Then type

    ren (drive letter from previous step):\Windows\WinSxS\Pending.xml* bad.xml

    You might get a duplicate file message. If this happens type:

    ren (drive letter from previous step):\Windows\WinSxS\Pending.xml, then press the Tab key immediately after Pending.xml, and enter a different name such as bad2.xml Kepp doing this until when you press the tab key you receive no other results. So the command should look like this:

    ren e:\Windows\WinSxS\Pending.xml* bad.xml

    PLEASE BE CAREFUL DOING THIS LAST STEP. RENAMING THE PENDING.XML FILE IS GENERALLY A BAD IDEA, BUT IT HAS BEEN KNOWN TO FIX UPDATE ISSUES IN THE PAST.

    For those of you wanting to peruse the warnings, see here.

    Edit: updated warning and procedures

    Was this answer helpful?

    0 comments
  3. Anonymous
    2014-04-22T23:17:29+00:00

    Actually, I just tried again and got this error:

    Microsoft Windows [Version 6.3.9600]

    (c) 2013 Microsoft Corporation. All rights reserved.

    C:\Windows\system32>dism /Online /Cleanup-image /Restorehealth

    Deployment Image Servicing and Management tool

    Version: 6.3.9600.16384

    Image Version: 6.3.9600.16384

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

    The restore operation failed. Either the repair source was not found or the comp

    onent store cannot be repaired.

    Error: 0x800f081f

    DISM failed. No operation was performed.

    For more information, review the log file.

    The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

    C:\Windows\system32>

    I guess my component store cannot be repaired. So my question is, is there a set of instructions to follow that gets you to a point to start over?

    Was this answer helpful?

    0 comments