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

Anonymous

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.

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

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

0 comments

Answer accepted by question author

Anonymous

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

0 comments

1,164 additional answers

Anonymous

2014-05-04T14:52:13+00:00

good news. yesterday Susan organised a case for me. I had an email from ms saying expect some help on Monday. ok I thought today I will not keep trying to update. I will listen to my music on Spotify.

just now I could not resit the temptation to try again, only to be welcomed in wu by a box saying we need to restart. checked it was 2919355 and clicked restart now. it fair zoomed along got to 100% restarted and very quickly loaded my lock screen. wow I thought is it a miracle? has it worked after a month of faffing about? yes loaded my charm page with the search and power buttons on the top. desktop has the store charm in the taskbar. it had succeeded by itself on automatically load updates.

now have they at last found the bugs and changed the files? I bet they have.

I wish you all the same success. thank you Susan, you must have sent vibes to my machine. time for me to do some gardening as well!!! cheers mart.
Was this answer helpful?

0 comments No comments
Anonymous

2014-05-04T13:30:52+00:00

Sorry, not a reply but an observation if of any use.

I haven't done anything to my pc since April and have left automatic updates enabled (so it has done the following all by itself);

2 May 2964444 unsuccessful error 80200001

3 May 2964444 installed successfully

3 May 2919355 unsuccessful error 80073712

4 May ditto
Was this answer helpful?

0 comments No comments
Anonymous

2014-05-04T11:01:37+00:00

I've even tried using a Windows 8.1 Enterprise Evaluation DVD (which supposedly has the update) as a source to repair the component store, but I got the same error.

Have you tried diagnosing? Using ProcMon? I hate this stupid code and no information for it! Is there some debug level event log we could use to enhance the diagnostics that people are getting? Isn't closed source blackbox reverse engineering fun? ; }

No, but there's really nothing to diagnose or monitor since the system works fine. SFC /SCANNOW does not show any integrity violations, only DISM. I'm beginning to think that the update breaks DISM somehow and the component store corruption message may be bogus. Again, the alleged corruption only occurs after full disk cleanup or running the DISM start component cleanup syntax. The very same start component cleanup in task scheduler does not cause this issue, even if I run it manually. However, it does NOT cleanup the component store. The results of DISM /online /cleanup-image /analyzecomponentstore are the same before and after it's run; same number of unclaimed packages, etc.

I am also getting a "corruption" error message when researched states corruption of the Win SxS file. Scannow finds NO errors and the DISM intermittently finds errors. I think this is suspect though because I have no problems with any other Windows Update.
Was this answer helpful?

0 comments No comments