Windows 8.1 Update 1 Failing to Install with errors 80070020, 80073712 and 0x800f081f

Anonymous

Original Title: Windows 8.1 Update 1 Failing to Install

I've been trying to get the Windows 8.1 Update 1 to install for a couple hours now. I installed a series of files using windows update earlier in the day. Later I tried installing the update file (KB2919355) that popped up in the Windows Update window. The downloading process look over 45 minutes for a 800 MB file even thought I have an internet connection over 20 MB/s. After that it spent 20 minutes installing the update until it failed giving an error code of 80070020. From that I restarted the computer to see if I could try another stab at it, nothing changed or improved.

Now I looked in the Windows update history to see if the other required updates like KB2919442,**** KB2932046, KB2937592 and KB2938439 were installed and they aren't in the update history. I thought they were installed already for KB2919355 to be installed. Are all of these update files included in the KF2919355 update that pops up in the windows update?

Also, my update history can is only up to date in the control panel and doesn't show any updates installed in the modern PC settings app. Did windows update fail to properly install updates required before trying to install later updates? What can and can't I install right now?

So far I've manually downloaded the links to KB2919355, KB2919442, **** KB2932046, KB2937592 and KB2938439 posted in this thread:

http://answers.microsoft.com/en-us/windows/forum/windows8_1-windows_update/windows-81-update-1/493e4360-1581-4dcd-9211-e4eb725b5f53

I haven't installed anything yet.

Any help on why nothing has worked or installed properly?

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

(Update (5/5/14): A fix for KB2919355 has been released that will resolve some customers receiving Error 80073712 when installing this update. This fix is now included as part of KB2919355 and will install the next time you attempt to install Windows Updates. The troubleshooting steps listed below have been revised to include this additional fix.

You can find additional guidance for troubleshooting problems when installing the update atInstall the latest Windows 8.1 Update.

If you receive Error 80073712 when installing KB2919355:

Swipe in from the right edge of the screen, and then tap Search.

(If you're using a mouse, point to the upper-right corner of the screen, move the mouse pointer down, and then clickSearch.) 2. Enter cmd in the search box, and then right-click or press and holdCommand Prompt. 3. Tap or click Run as administrator**.** 4. In the Administrator: Command Prompt window, type one of the following commands depending on your version of Windows, and then press Enter. Don't include a line break as shown here. - If you're running a 64-bit version of Windows 8.1, type:

dism /online /remove-package /packagename:Package_for_KB2919355~31bf3856ad364e35~amd64~~6.3.1.14

If you're running a 32-bit version of Windows 8.1, type:

dism /online /remove-package /packagename:Package_for_KB2919355~31bf3856ad364e35~x86~~6.3.1.14

If you're running Windows RT 8.1, type:

dism /online /remove-package /packagename:Package_for_KB2919355~31bf3856ad364e35~arm~~6.3.1.14

Type the following command, and then press Enter:

DISM.exe /Online /Cleanup-image /Restorehealth

Type the following command, and then press Enter:

dism /online /cleanup-image /startcomponentcleanup

7.Install the Windows 8.1 Update orWindows RT 8.1 Update.

If you're running Windows 8.1, go to the Microsoft Download Center:

**Windows 8.1 Update** (32-bit version)

**Windows 8.1 Update** (64-bit version)

Be sure to read through the Install Instructions on the download page. The downloaded files must be installed in the proper order, starting with clearcompressionflag.exe, which was recently added to help prevent Error 80073712 from occurring in some cases.

If you're running Windows RT 8.1, try to install Windows RT 8.1 Update **(KB 2919355)**again from Windows Update.

If these steps still fail to resolve your error, pleasecontact Microsoft Supportso that we can further investigate your issue. We thank you for your patience and apologize for any inconvenience.

0 comments

1,053 additional answers

Anonymous

2014-04-19T11:49:52+00:00

5 days gone,all method tested,and still i cant install this update!what are u doing dear mS?!
Was this answer helpful?

0 comments No comments
Anonymous

2014-04-19T13:42:27+00:00

Well, in my DISM log file, nothing of this kind shows up. It is just every **** but in Chinese language

I think that just means it is too big and not decompressing properly. I showed someone how to use Powershell to extract some of the last few lines or how to find the number of lines so they could use more.

<extract>

The DISM log strangeness might be a factor of the Notepad's Font choice. (In the Format menu.) Also, I have seen problems with Notepad when saving, suggesting that the Encoding be changed to Unicode or bits could be lost.   Otherwise I wonder if it is just too big for Notepad? If we had an estimate of the number of lines you could use more <dism.log to skip to somewhere near the end... Heh. I just tried giving it s 999999 to (hopefully) say "There aren't that many lines. There are nnnnn." or something else which might be useful for that use-case. Instead it says "EOF" and exits. Correct but useless functionality, especially for an interactive scenario.

Do you know any Powershell? I think that it could get so many lines from the end and tell us how many there are...   Well, don't file this under "best practices" but this worked for me:

In Powershell:

cd $env:windir\logs\dism

get-content dism.log | measure-object

That apparently shows the number of lines as Count :

So you could use that as a maximum (in a cmd window) for more <dism.log +nnnnn

where nnnnn is the line number that you are guessing you would like to start at and the + is just the syntax which denotes the use of that feature.   Use more /? to see the full command syntax.

Tip: once you know what part you want to capture you can pipe it to clip and then paste that into Notepad and see if it likes that much any better.

</extract>
Was this answer helpful?

0 comments No comments
Anonymous

2014-04-19T14:42:55+00:00

The DISM.log file is not compressed. I have opened it with emacs and I still see the non-ascii characters in some lines. Tried to change the encoding to utf-8, urf-16 (in emacs), etc. This should be plain english text, no?

When I first saw that garbage in the log, I decided to stop trying the different recipes to fix the issue published in this thread.

for KB2919355 I get error 80073712

for KB2936068 I get error 800F081F

But the Windows updates for Windows defender I have received in the last week have all installed fine. (KB2267602), as well as others related to Siverlight.
Was this answer helpful?

0 comments No comments