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-10T19:21:02+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.

I agree that Windows updates should not break systems. In my case, initially I also could not install the KB2919355 update but maybe, just my luck, it just would not install the update. It reverts back the system to previous state and system was as good as it was before I tried the update. If not for the help of Microsoft tech support and of Susan, I also would not have been able to update my HP Envy m4 laptop (which is now working by doing in-place upgrade that does not apply to those without ISO).

There would have been two options for me, as a basic user: 1) I eventually, probably would have tried all the recommendations here, and probably may have succeeded or not with using the ISO to repair (in-place upgrade).... or 2) wait for Microsoft to fix the installation problem and release a different KB patch. For #2, I still would have a working system until it gets broken again... For #1, good chance I would break the system myself... for the "great want" of being able to have the Windows 8.1 Update.

That's why, I'm also sorry for those with good-working systems that got broken by the update.... or even those who now think their systems are broken because the DISM kept failing with "corrupted WinSxS" or some other errors.

Hoping for #2 though and soon... before more machines "break".
Was this answer helpful?

0 comments No comments
Anonymous

2014-04-10T19:19:44+00:00

Well, this is not an issue.

This command lists you only the updates wich are installed (or were once installed).

So it returns nothing, because you will that he return that the update 2919355 is installed but it isn't.

What's about your cbs.log?

CBS log already quoted two posts up from your original post.
Was this answer helpful?

0 comments No comments
Anonymous

2014-04-10T19:17:40+00:00
Throwing my hat in. 4 Windows 8.1 systems. 3 are Surface Pro2's, native windows 8.1. The other is a W8 laptop (OEM) with Media Center upgraded to 8.1 months ago. All working previously. Problem free.

I'm an IT professional. Have tried all the fixes here (except reset and clean install). Can't spend any more time on this. Others pay for my time. I can't give it to MS for free. Would rather not start over. I've seen MS through worse and like everything else this too will pass. Its a shame because these mistakes gravely affect customer satisfaction and opinion. I was an early adopter of W8 and have already deployed many 2012 Servers. I like metro. I'm hoping that patience will win the day.

I managed to upgrade 3 systems via Windows Update automatically with no issues.

I also managed to install the update in 2 offline VMs (one 32 Bit and the other 64 Bit) and one offline system which had only installation with the Windows 8.1 .iso and the generic product key. These had the following installed:

64 Bit

Windows 8.1 Update KB2919442

Windows 8.1 Update 1 KB2919355

32 Bit

Windows 8.1 Update KB2919442

Windows 8.1 Update 1 KB2919355

There were no issues.

Were any of your systems Windows 8.0 and upgraded via the Store?
For e.g. I have here Win 8.1 from MSDN .iso - doesn't work.

Unfortunately I have no system to look up, but maybe you can look at times in this directory, and tell me how the content is there (only on x64 Systems):

%windir%\WinSxS\amd64_microsoft-windows-help-privstatement_r_31bf3856ad364e35_6.3.9600.17031_none_57e5a2f32866988f
Was this answer helpful?

0 comments No comments