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

Anonymous
2014-04-08T22:28:41+00:00

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?

Windows for home | Previous Windows versions | Windows update

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
2014-05-14T20:01:15+00:00

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

Was this answer helpful?

10 people found this answer helpful.
0 comments
Answer accepted by question author
Anonymous
2014-04-18T23:21:11+00:00

(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:

  1. 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

  1. Type the following command, and then press Enter:

DISM.exe /Online /Cleanup-image /Restorehealth

  1. 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.
  1. 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.

Was this answer helpful?

3 people found this answer helpful.
0 comments

1,053 additional answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2014-04-13T18:19:09+00:00

    I have three questions about this very interesting post about the steps suggested by darora10:

    1. were they recommended by MS for a specific contextual reason, or just as a general targeted solution to error 80073712?
    2. this was  the error code I had originally, but how can you determine the error code when a subsequent attempt gets right to the configuring windows updates (after restart), decides it has failed, and then undoes configuration changes, and you wind up back at the log-in screen as  if nothing had happened; is it stored in a log file somewhere?  I have looked in \Windows\WindowsUpdate.log, but nothing leaps out from the verbose logging of my last attempt (as well as the stuff it has done automatically in the background since)
    3. much has been made of the recommended order - KB2919355, KB2932046, KB2937592, KB2938439, and KB2934018 - but I have never got further than the attempted re-start after KB2919355; is anyone suggesting that you would run all five packages _before_ the restart requested  by the first KB2919355 element?

    Hi mr.stern:

    I will try to answer your questions, although it will just be my opinion - I am not an expert on Windows. I am just a user trying to avoid re-installing windows starting at Win 8.0 and losing software I've had for years that I may not be able to re-install.

    1. The steps in darora10's solution are similar to, but differ in the DISM commands used in the MS recommended solution you can find at this link:

    http://support.microsoft.com/kb/957310/en-us

    The MS recommended solution did not work for me - The "scanhealth" command reported the windows components were repairable, but the "restorehealth" command reported a failure to restore the corrupted or missing windows components. Therefore I searched this forum and others until I found one that worked for my system - it may not work for some of the others.

    1. The fact that you were able to use Windows Update and get to the restart point implies that the installer found something else wrong when it tried to integrate the update into your operating system.  What that problem was is, as you put it, documented "in a log file somewhere". It probably is, but understanding the log files takes a person who is intimately familiar with the Windows OS.  There is probably not one single person at Microsoft who knows every detail of the entire Windows OS. When I was using Windows Update I never got to the point of restart - Windows Update always failed, so that is why I downloaded the individual components of the update and saved them for a manual install.
    2. If you downloaded the individual components as your post suggests you did, you do not have to do a restart after installing each component.  You can install each one separately, one after the other, just click the "restart later" button until the last component is installed. Then do a restart if all components install successfully. Just make sure you install them in the proper order, but before you install anything make sure the previously released component KB2919442 is installed on your system.  You can check this by running Windows Update and selecting to look at your update history, or by running Control Panel and selecting a list of all installed updates.  If KB2919442 is not there you will have to search for it online at MS Support and install it before installing any of the update components mentioned above.  When you finally do the restart you should be home free, unless the problem you had in 2, above, is still there.  Good luck.

    LeicaIIIf

    Was this answer helpful?

    0 comments
  2. Anonymous
    2014-04-13T18:50:00+00:00

    OK, here is what the MS tech guy did to get my system to install 8.1 Update. I had all the usual **** happen you have been reading here. Failed to install many times. Did all the DISM stuff. Then got a MVP person to boot me up the ladder to MS tech support.

    Seems the installation was Partially installed and still sitting in que. Just failed , so had to remove the partially installed 355 download. Apparent;y when it fails, it doesnt remove whatever I tried to install...just sits there.

    That is why they removed the partial 355 file.

    Need to get to Command Prompt at elevated admin level.

    ==============================

    This is from the log they kept of what we did.

    As requested below mentioned are the commands we executed to get the update installed on the machine:

    Command to remove the traces from the previous installation

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

    Remove unrequired components from WinSXS (For more information on the below mentioned command refer to:

    http://technet.microsoft.com/en-us/library/dn251565.aspx

    dism /online /cleanup-image /startcomponentcleanup

    =====================

    But this may not be something you want to attempt .....nor did I. Too much DOS stuff that is scary. The problem is the Windows Component Store has lots of what they called "orphaned files" that need to be cleaned and removed. Anytime you install or update something it leaves stuff in there and is supposed to be cleaned out over time. Read about the SXS file above at that link. Looks to me that MS needs to put some type of script in their install package that looks for and cleans up that Component Store when giving out big updates like this.

    Finally!!!

    I did as this said ,rebooted,ran the update I had downloaded and saved.Voila it worked first time.

    Worked for me too!  Finally...  thank you Mr. Bill.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2014-04-13T19:10:58+00:00

    I receive the error code 0x8024200D.

    Tried numerous DISM-Fixes and MS-FixIts to solve this. Nothing worked. Also tried installing the .msu file of the update - it also fails.

    Was this answer helpful?

    0 comments