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-05-06T18:10:39+00:00

I just finished going through the troubleshooting steps. MS Windows Update troubleshooter detected corrupt files--so I assume not fixed. DISM Scan Health said files were repairable. DISM Restore Health failed. I did a manual update and it failed as well.

So I have run 2 automatic updates, one manual update, followed the troubleshooting steps and the update failed each time.

So I guess this is not the fix.

Apparently not. I don't know what they're doing in Redmond...I think they don't know what they are doing.
Was this answer helpful?

0 comments No comments

Anonymous

several error codes including 0x8007045b and 0x80070490, but it is not clear which if either of those is the specific reason why it gives up at the last post. Even though I am a notorious geek, it is still unobvious to me where exactly in the log corresponds to the point where it concludes it has failed and rolls back.

I still think that the best way to "read between the lines" of all of these diagnostics is to use ProcMon to correlate and supplement them.

But since you at least have some details to look at let's start with these.

C:>set /a c =0x45b 1115 C:>net helpmsg %c% A system shutdown is in progress. C:>set /a c =0x490 1168 C:>net helpmsg %c% Element not found.

Pretty sparse clues.

2014-05-01 04:45:00:269 228 34b4 AU WARNING: Failed to get Wu Exemption info from NLM, assuming not exempt, error = 0x80070490

I have no idea what that is supposed to mean. Try ProcMon? Otherwise, are there any Event log entries for that timestamp (e.g. within that second) which either help clarify which element was "not found" or at least which component is complaining about something?

However, if we then look at the context of the code

2014-05-01 04:45:00:191 228 34b4 AU # Will interact with non-admins (Non-admins are elevated (Policy)) 2014-05-01 04:45:00:269 228 34b4 AU WARNING: Failed to get Wu Exemption info from NLM, assuming not exempt, error = 0x80070490 2014-05-01 04:45:00:269 228 34b4 AU The system has been restored. Hence triggering AU detection through DetectNow API.

I would wonder about a possible permissions problem. E.g. perhaps whatever is being allowed by "policy" is not really being allowed and that is what is causing the "element not found"? Again, this hypothesis would be easily tested by using ProcMon.

Good luck

Robert Aldwinckle

I don't think it's the end user's job to find and fix MS' mess up. We don't have problems with every other update that is issued so it's not us...it's MS. I know you're not a MS employee and I appreciate the fact you're trying to help but this doesn't really help us because it lets MS off the hook...imo.

0 comments

Anonymous

2014-05-06T18:53:19+00:00
Robert, if we get to the point that users have to fire up procmon in order to get updates installed, that's when we draw the line and get them into support for two reasons:
1. this is not reasonable to be asking people to do this.
2. Microsoft needs to understand why these systems are getting into this condition in the first place.

As a geeky exercise, that's one thing. As a reasonable request to ask anyone in here to do? I'm going to respectfully say that this is beyond what is reasonable to expect people to do here.
Was this answer helpful?

0 comments No comments