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-04-13T05:14:43+00:00

It's clear nothing will change with this until Microsoft is so completely and publicly shamed that they *have* to do something about it -- maybe even a class-action suit, for recklessly destroying so many millions of paying customer's systems with a faulty but *mandatory* update?

Meanwhile, I'm one of those Win7x64-to-Win8ProWMCx64-to-Win 8.1ProWMCx64 customers as well. And I've learned the hard way: ANY time I do a version upgrade, I start with a clean backup image of a virgin installation (in my case, I use Acronis) and update from there. Then I make a brand-new, clean backup image of that new virgin installation for use in future disasters.

I even do this with brand-new OEM systems (including Microsoft Surface Pro 2!). Now that Microsoft has all but abandoned iso's for OEM systems or paid upgrades, it's the only way around Redmond's incompetence.

Spot on! I personally think MS should compensate everyone who has had trouble installing this update. I am not doing anything more until they issue a valid update which I hope is soon since this is a MANDATORY update. I'm totally disgusted. When things like this happen I wonder why I am still with MS when my techie husband keeps encouraging me to move to Linux as he has. When will MS learn?
Was this answer helpful?

0 comments No comments
Anonymous

2014-04-13T05:02:40+00:00

...I'm about to go into a POPCORN COMA here, I've been silent and eating popcorn while reading all these replies up to the point I think someone has found a fix (not yet). I have attempted SOME of these things and I actually got it to try and put on 355

[...]

WHY IS THIS SO COMPLICATED? Get the OS to work right on someone's machine there at Redmond, zip all the files up, and send that out. Good grief.

Is it too soon to turn "355" into a verb? You know, when someone really, REALLY messes something up: "Man, you really 355'd that one"?

Speaking of "good grief," I really do feel like Charlie Brown: Every time I think I'm about to install that update successfully, Sinofsky jerks it out of the way.

@

o o

(

~~~
Was this answer helpful?

0 comments No comments
Anonymous

2014-04-13T05:01:05+00:00

I'm with you and I REFUSE to refresh/re-install because it is MS' fault.
Was this answer helpful?

0 comments No comments