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-15T19:25:05+00:00

Look, I'm just an amateur user of windows 8.1 and I have no idea what all the techno jargon is all about. As far as I'm concerned, DISM means Don't Install Software from Microsoft.

So long as my 8.1 continues working and Microsoft continues to support it without the 355 update then I'm fine with that. However, if they think that I am going to mess around with all this mumbo jumbo then this will be the last Microsoft product I buy, and rest assured my name will be included in the soon to come class action law suit.
Was this answer helpful?

0 comments No comments
Anonymous

2014-04-15T19:01:06+00:00

Thanks for the guidance. Everything went well until the offline install which, for probably the 7th or 8th time, failed after going through the entire config exercise. I somehow doubt Microsoft are bothered about their private customers, else they'd have already pulled this update, as they did for their corporate customer base.

Microsoft generously decided to share the pain with corporate customers too see here and here. Error codes are the same as 8.1. All Microsoft did was pull it from WSUS.

They pulled it from WSUS for corporate customers because they discovered there was a client side issue with communicating with WSUS after installation due to an incompatible SSL protocol. I run WSUS, but do not use SSL for communications, which is the workaround for the issue. However, not every corporate customer is willing or able to just switch from the use of SSL to the use of non-SSL.
Was this answer helpful?

0 comments No comments
Anonymous

2014-04-15T18:46:51+00:00

Thanks for the guidance. Everything went well until the offline install which, for probably the 7th or 8th time, failed after going through the entire config exercise. I somehow doubt Microsoft are bothered about their private customers, else they'd have already pulled this update, as they did for their corporate customer base.

Microsoft generously decided to share the pain with corporate customers too see here and here. Error codes are the same as 8.1. All Microsoft did was pull it from WSUS.
Was this answer helpful?

0 comments No comments