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-02T11:49:54+00:00

After reading all the threads, and having nothing work for me on my Alienware laptop, I discovered something that might have to do with this problem.

Question:

I was able to update my Gateway laptop, after a lot of attempts and trouble. But it is updated.

In disk management, the gateway PC has a partition to the left of the "C" partition. It's the System Reserved Partition, which I know should be there. It's 100MB, with about 40MB free space.

I looked at disk management on my Alienware PC, and it does not have any partition to the left of "C", or, for that matter, any partition labeled System Reserved.

I know a bit about PCs, but I don't understand this. Can anyone shed some light on this for me? This is the PC that would always hang up at 74% during the update install, fail, and start over again in a deadly loop. Maybe the lack of that partition is causing the problem?

Thanks for reading
Was this answer helpful?

0 comments No comments
Anonymous

2014-05-02T12:07:54+00:00

I know a bit about PCs, but I don't understand this. Can anyone shed some light on this for me? This is the PC that would always hang up at 74% during the update install, fail, and start over again in a deadly loop. Maybe the lack of that partition is causing the problem?

Check the log files under C:\Windows\Logs\CBS that were written during the failing installation.

If the lack of space within the System Reserved Partition is the cause, then you should find entries with the string ERROR_DISK_FULL in the log files.
Was this answer helpful?

0 comments No comments
Anonymous

2014-05-02T12:30:09+00:00

In attempting to update to Windows 8.1 Update 1, I repeatedly received error 80073712 and an occasional 80246007. Researching fixes, many of them asked that I run “DISM.exe /Online /Cleanup-image /Restorehealth” but it would always fail. Looking in the DISM.log file I came across these key lines:

[1964] Mounting new image.

Wim: [\?\GLOBALROOT\device\harddisk0\partition1\Recovery\WindowsRE\Winre.wim]

Mount Path: [C:\WINDOWS\TEMP\521ba401-980a-4c31-ad0c-bef18ee77a82]

[1964] ImageUnmarshallHandle: Reconstituting wim at \?\GLOBALROOT\device\harddisk0\partition1\Recovery\WindowsRE\Winre.wim.

[1964] [0x80070070] ReadWriteDataInternal:(134): There is not enough space on the disk.

Pondering it, I realized that there is no \Recovery folder on my C drive. I assigned a drive letter to the System Reserved partition and low and behold there is a \Recovery folder there. My System Reserved partition was 350MB in size with 1MB free. Using a Partition manager, I shrunk C: and expanded the System Reserved partition to 500MB. While DISM still failed, Windows 8.1 Update 1 installed on the very next try. Checking back into the System Reserved partition, 8MB of data was added.

So, My problem was a insufficiently sized System Reserved partition created by the original installation of Windows 8.1 Preview. This leaves me wondering how big I would need to make the System Reserved partition for the DISM Restorehealth command to complete....

I have tried all solutions posted here - none work - I will say I am a developer and I am running installs of Windows 8.1 from MSDN - which I have read is causing an issue as well. I wanted to check on this lead - my system partition is showing about 40MB out of 350MB free. My DISM log is as follows: (This is from my desktop - my laptop log is similar but there are more garbage characters at the end) On my laptop I get an error 110 on cleaning step with resetbase. Has anyone had any luck with getting a MSDN Windows 8 iso install patched??? I heard Microsoft would be releasing a patch for MSDN installs - but haven't heard when or anything else.

[1904] Caller did not request sparse mount

[1904] Mounting new image.

Wim: [\?\GLOBALROOT\device\harddisk1\partition1\Recovery\WindowsRE\Winre.wim]

Image Index: [1]

Mount Path: [C:\WINDOWS\TEMP\1829cc5c-fe54-47aa-932d-e762ca387c1d]

[1904] Wimserv process started for guid 166903c5-6f68-4c2d-a7a7-c7036a34780b. Id is 1912

[1912] ImageUnmarshallHandle: Reconstituting wim at \?\GLOBALROOT\device\harddisk1\partition1\Recovery\WindowsRE\Winre.wim.

[1912] Mounted image at C:\WINDOWS\TEMP\1829cc5c-fe54-47aa-932d-e762ca387c1d.

[1904] [0x8007007b] FIOReadFileIntoBuffer:(1415): The filename, directory name, or volume label syntax is incorrect.

[1904] [0xc142011c] UnmarshallImageHandleFromDirectory:(511)

[1904] [0xc142011c] WIMGetMountedImageHandle:(2568)

[1904] [0x8007007b] FIOReadFileIntoBuffer:(1415): The filename, directory name, or volume label syntax is incorrect.

[1904] [0xc142011c] UnmarshallImageHandleFromDirectory:(511)

[1904] [0xc142011c] WIMGetMountedImageHandle:(2568)

[1904] ImageUnmarshallHandle: Reconstituting wim at \?\GLOBALROOT\device\harddisk1\partition1\Recovery\WindowsRE\Winre.wim.

[1904] ImageUnmarshallHandle: Reconstituting wim at \?\GLOBALROOT\device\harddisk1\partition1\Recovery\WindowsRE\Winre.wim.

[1904] ImageUnmarshallHandle: Reconstituting wim at \?\GLOBALROOT\device\harddisk1\partition1\Recovery\WindowsRE\Winre.wim.

[1904] ImageUnmarshallHandle: Reconstituting wim at \?\GLOBALROOT\device\harddisk1\partition1\Recovery\WindowsRE\Winre.wim.

[1904] ImageUnmarshallHandle: Reconstituting wim at \?\GLOBALROOT\device\harddisk1\partition1\Recovery\WindowsRE\Winre.wim.

[1904] ImageUnmarshallHandle: Reconstituting wim at \?\GLOBALROOT\device\harddisk1\partition1\Recovery\WindowsRE\Winre.wim.

[1904] ImageUnmarshallHandle: Reconstituting wim at \?\GLOBALROOT\device\harddisk1\partition1\Recovery\WindowsRE\Winre.wim.

[1912] Received unmount request for image with guid 166903c5-6f68-4c2d-a7a7-c7036a34780b.

[1912] Unmount for image at C:\WINDOWS\TEMP\1829cc5c-fe54-47aa-932d-e762ca387c1d complete.

〲㐱〭ⴱ㤲ㄠ㨰㠲〺ⰹ䤠普⁯††††††††䐠卉⁍†䥐㵄㤱㐰吠䑉ㄽ㤷‶敔灭牯牡汩⁹敳瑴湩⁧桴⁥捳慲捴⁨楤敲瑣牯⹹吠楨⁳慭⁹敢漠敶牲摩敤⁮祢甠敳⁲慬整⹲ⴠ䌠䥄䵓慍慮敧㩲䘺湩污潃獮牴捵൴㈊㄰ⴴ㄰㈭‹〱㈺㨸㤰‬湉潦†††††††††䥄䵓†倠䑉ㄽ〹‴䥔㵄㜱㘹匠牣瑡档搠物捥潴祲猠瑥琠⁯䌧尺䥗䑎坏屓䕔偍❜‮‭䑃卉䵍湡条牥㨺異彴捓慲捴䑨物਍〲㐱〭ⴱ㤲ㄠ㨰㠲〺ⰹ䤠普⁯††††††††䐠卉⁍†䥐㵄㤱㐰吠䑉ㄽ㤷‶楄浳潃敲搮汬瘠牥楳湯›⸶⸳㘹〰ㄮ㌶㐸ⴠ䌠䥄䵓慍慮敧㩲䘺湩污潃獮牴捵൴

Thoughts???
Was this answer helpful?

0 comments No comments