This error appears to be related to expected files, folders or registry paths that are missing. One commonly reported folder being missing is the C:\Users\Default folder. Open the File Explorer, expand C, and expand the Users folder. If there is no folder named Default , create one. If C:\Users\Default exists please use the following guidance: Run the Windows Update Troubleshooter , then open Windows Update and try to install the update again. Then run the DISM tool Swipe in from the right edge of the screen, and then tap Search . (If you're using a mouse, point to the lower-right corner of the screen, move the mouse pointer up, and then click Search.) Enter command prompt in the search box. In the list of results, swipe down on or right-click Command Prompt , and then tap or click Run as administrator . In the Administrator: Command Prompt window, enter the following commands. Press the Enter key after each command: DISM.exe /Online /Cleanup-image /Scanhealth DISM.exe /Online /Cleanup-image /Restorehealth To close the Administrator: Command prompt window, type Exit, and then press Enter. Run Windows Update again. If you have C:\Users\Default and you have used the Windows Update troubleshooter and completed the DISM commands but still experience Error 0x80070003 please contact Microsoft Support so that we can further investigate your issue.

Ok thanks. Does anyone have any information from the Great Software Company as to whether, when or if said company has a solution to this update failing to install on many computers? In addition, does anyone have any idea as to whether, when or if the aforesaid company intends to deal with the corruption or possibly false error messages (take your pick) which affect DISM /Restorehealth? After next Tuesday (which will be the two month anniversary of this mess) will we still be receiving the same answers (which for the most part do not work) to the failed update and no answers to the issues related to the corruption or whatever else is causing DISM to be non-functional? The silence is the most troubling aspect of all of this. It is as if the company has decided to stuff cotton in its figurative ears and allows the "answers", "solutions" and "fixes" to be continued to be posted by the same people who have been posting the same thing since April 8th to no avail. This is surreal. Perhaps that is too much to ask on a forum dedicated to Microsoft products, and in particular to the category of issues related to updates to Windows 8.1. If so, I apologize for wasting everyone's time with this post as perhaps my expectations are well-beyond what the average user expects from a company which for the most part derives its income from selling operating systems. Again maybe the dynamics have changed and people have become accustomed to this sort of incompetence and it is what they expect from most businesses nowadays.

No, I think you bring up extremely valid points and excellent questions. The system wide file corruption caused corruption to such a degree not just to the component store, but dism itself to the point that using the /source flag and pointing to either 8.1 installation media or a working 8.1 install did nothing to solve the dism generated errors and inability to fix component store corruption. The first repair install I did, I ran /startcomponentcleanup after Windows rebooted and the component cleanup took just shy of 5 hours... unheard of.

At this time this is my understanding: KB2919355 has been revised to fix the main cause of failure, the corruption issue. That's that clearcompression flag patch you see in the revised KB2919355. Any of the other threads started to deal with the other known issues (see http://www.infoworld.com/t/microsoft-windows/microsoft-posts-tips-overcoming-windows-81-update-kb-2919355-errors-242603 for the links to posts in this forum) I do not see any action from said software company to fix these automatically. I have been given no information that any automatic fix is coming. As is stated in all of those links, if you are still impacted, you are informed to contact support directly. That's the current "resolution" at this time. On a similar note, may I share a support story? Yesterday I had a problem updating my mini jambox speaker. I called support. Talked to a nice person who I told him all the steps I had done. He said "yes, you've tried everything, let's get you with an escalation case". I received a call back, from a equally nice person, who walked me through a factory reset. The update to the Jambox then took this time. I had to reset the device, but I lost no data. Obviously a jambox speaker is not the same as a Windows 8.1 but I think the problem is exactly what you said at the end "the dynamics have changed and people have become accustomed to this sort of incompetence and it is what they expect from most businesses nowadays. " I was shocked by my good experience of support with the Jambox device. I shouldn't be shocked. I should expect this from all my vendors.

Normally dirty shutdowns leave behind files that aren't yet completed. There's a file that keeps track of what should be installed when and where called pending.xml. If this gets stuck in this condition, it can really mangle up things. http://blogs.technet.com/b/joscon/archive/2011/03/11/why-you-don-t-want-to-edit-your-pending-xml-to-resolve-0xc0000034-issues.aspx While that's for Windows 7, it's a hint of what is going on with the pending.xml file.

This was probably time consuming research and wanted to say thanks =]

Error: 0x80070003 when installing KB 2919355

Anonymous

This error appears to be related to expected files, folders or registry paths that are missing.

One commonly reported folder being missing is the C:\Users\Default folder.

Open the File Explorer, expand C, and expand the Users folder.

If there is no folder named Default, create one.

If C:\Users\Default exists please use the following guidance:

Run the Windows Update Troubleshooter, then open Windows Update and try to install the update again.

Then run the DISM tool

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

(If you're using a mouse, point to the lower-right corner of the screen, move the mouse pointer up, and then click Search.)

Enter command prompt in the search box.
In the list of results, swipe down on or right-click Command Prompt, and then tap or click Run as administrator.
In the Administrator: Command Promptwindow, enter the following commands. Press the Enter key after each command:
1. DISM.exe /Online /Cleanup-image /Scanhealth
2. DISM.exe /Online /Cleanup-image /Restorehealth
To close the Administrator: Command prompt window, type Exit, and then press Enter.
Run Windows Update again.

If you have C:\Users\Default and you have used the Windows Update troubleshooter and completed the DISM commands but still experience Error 0x80070003 please contact Microsoft Support so that we can further investigate your issue.

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

99 answers

Anonymous

2014-05-28T23:36:29+00:00

Ok thanks.

Does anyone have any information from the Great Software Company as to whether, when or if said company has a solution to this update failing to install on many computers? In addition, does anyone have any idea as to whether, when or if the aforesaid company intends to deal with the corruption or possibly false error messages (take your pick) which affect DISM /Restorehealth?

After next Tuesday (which will be the two month anniversary of this mess) will we still be receiving the same answers (which for the most part do not work) to the failed update and no answers to the issues related to the corruption or whatever else is causing DISM to be non-functional?

The silence is the most troubling aspect of all of this. It is as if the company has decided to stuff cotton in its figurative ears and allows the "answers", "solutions" and "fixes" to be continued to be posted by the same people who have been posting the same thing since April 8th to no avail. This is surreal.

Perhaps that is too much to ask on a forum dedicated to Microsoft products, and in particular to the category of issues related to updates to Windows 8.1. If so, I apologize for wasting everyone's time with this post as perhaps my expectations are well-beyond what the average user expects from a company which for the most part derives its income from selling operating systems. Again maybe the dynamics have changed and people have become accustomed to this sort of incompetence and it is what they expect from most businesses nowadays.
Was this answer helpful?

2 people found this answer helpful.

0 comments No comments
Anonymous

2014-05-28T23:48:38+00:00

No, I think you bring up extremely valid points and excellent questions.

The system wide file corruption caused corruption to such a degree not just to the component store, but dism itself to the point that using the /source flag and pointing to either 8.1 installation media or a working 8.1 install did nothing to solve the dism generated errors and inability to fix component store corruption.

The first repair install I did, I ran /startcomponentcleanup after Windows rebooted and the component cleanup took just shy of 5 hours... unheard of.
Was this answer helpful?

2 people found this answer helpful.

0 comments No comments
Anonymous

2014-05-28T23:58:04+00:00

At this time this is my understanding:

KB2919355 has been revised to fix the main cause of failure, the corruption issue. That's that clearcompression flag patch you see in the revised KB2919355.

Any of the other threads started to deal with the other known issues (see http://www.infoworld.com/t/microsoft-windows/microsoft-posts-tips-overcoming-windows-81-update-kb-2919355-errors-242603 for the links to posts in this forum) I do not see any action from said software company to fix these automatically. I have been given no information that any automatic fix is coming. As is stated in all of those links, if you are still impacted, you are informed to contact support directly.

That's the current "resolution" at this time.

On a similar note, may I share a support story? Yesterday I had a problem updating my mini jambox speaker. I called support. Talked to a nice person who I told him all the steps I had done. He said "yes, you've tried everything, let's get you with an escalation case". I received a call back, from a equally nice person, who walked me through a factory reset. The update to the Jambox then took this time. I had to reset the device, but I lost no data. Obviously a jambox speaker is not the same as a Windows 8.1 but I think the problem is exactly what you said at the end "the dynamics have changed and people have become accustomed to this sort of incompetence and it is what they expect from most businesses nowadays. "

I was shocked by my good experience of support with the Jambox device. I shouldn't be shocked. I should expect this from all my vendors.
Was this answer helpful?

2 people found this answer helpful.

0 comments No comments
Anonymous

2014-05-29T00:00:33+00:00

Normally dirty shutdowns leave behind files that aren't yet completed. There's a file that keeps track of what should be installed when and where called pending.xml. If this gets stuck in this condition, it can really mangle up things.

http://blogs.technet.com/b/joscon/archive/2011/03/11/why-you-don-t-want-to-edit-your-pending-xml-to-resolve-0xc0000034-issues.aspx

While that's for Windows 7, it's a hint of what is going on with the pending.xml file.
Was this answer helpful?

2 people found this answer helpful.

0 comments No comments
Anonymous

2014-05-29T00:01:38+00:00

This was probably time consuming research and wanted to say thanks =]
Was this answer helpful?

2 people found this answer helpful.

0 comments No comments