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.

No, I think you bring up extremely valid points and excellent questions. The system wide file corruption caused corruption to such a degree to not just 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. I just saw a post from a MVP and Moderator in the past hour referring to using the /source flag to resolve the issue notwithstanding the numerous threads and posts which have demonstrated the corruption extends to not only /Restorehealth but using another image to fix the issue. It appears to me many of these fine folks have a library of "form posts" which they copy and paste on a routine basis. Some posters are fixated on anti-virus programs and post the same form "antivirus" post every time someone has a problem related to installing an update including questions about "Do you or have you ever used a registry cleaner, etc."), others are fixated on other things, but in the end it is a series of canned posts which are repeated sometimes on an hourly basis. The poor user who has no experience in reading posts here assumes the post is designed to fix their particular problem or issue but if they would read a few other threads they would find the post related to "their issue" is nothing but a copy and paste from a collection of canned posts from the computer of the responder which has been posted to several threads. Sometimes the same canned post may appear in five or six threads within a 15 minute period. Unbelievable.

If you review the 6 threads dealing with the 6 main errors users have experienced with KB2919355, you will see the same microsoft employee, who is a moderator himself, post the same /scanhealth /restorehealth troubleshooting steps on majority of the threads. It's ridiculous, even more so when you consider /scanhealth is redundant and not needed as it's read only and is the equivalent of chkdsk c: /scan, a read only error check.

A prime example of a "canned response".

That was an interesting read, shedding light on numerous things I had no clue about. Thanks a bunch :D

cf. http://answers.microsoft.com/en-us/windows/forum/windows8_1-windows_update/error-0x80073712-when-installing-kb-2919355/c5a08cdf-6e41-4b67-b2ae-68f542070840?page=18#LastReply

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-29T00:04:13+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 to not just 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.

I just saw a post from a MVP and Moderator in the past hour referring to using the /source flag to resolve the issue notwithstanding the numerous threads and posts which have demonstrated the corruption extends to not only /Restorehealth but using another image to fix the issue. It appears to me many of these fine folks have a library of "form posts" which they copy and paste on a routine basis. Some posters are fixated on anti-virus programs and post the same form "antivirus" post every time someone has a problem related to installing an update including questions about "Do you or have you ever used a registry cleaner, etc."), others are fixated on other things, but in the end it is a series of canned posts which are repeated sometimes on an hourly basis. The poor user who has no experience in reading posts here assumes the post is designed to fix their particular problem or issue but if they would read a few other threads they would find the post related to "their issue" is nothing but a copy and paste from a collection of canned posts from the computer of the responder which has been posted to several threads. Sometimes the same canned post may appear in five or six threads within a 15 minute period. Unbelievable.
Was this answer helpful?

0 comments No comments
Anonymous

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

If you review the 6 threads dealing with the 6 main errors users have experienced with KB2919355, you will see the same microsoft employee, who is a moderator himself, post the same /scanhealth /restorehealth troubleshooting steps on majority of the threads. It's ridiculous, even more so when you consider /scanhealth is redundant and not needed as it's read only and is the equivalent of chkdsk c: /scan, a read only error check.
Was this answer helpful?

0 comments No comments
Anonymous

2014-05-29T00:11:14+00:00

A prime example of a "canned response".
Was this answer helpful?

0 comments No comments
Anonymous

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

That was an interesting read, shedding light on numerous things I had no clue about. Thanks a bunch :D
Was this answer helpful?

0 comments No comments
Anonymous

2014-05-29T00:52:22+00:00

cf. http://answers.microsoft.com/en-us/windows/forum/windows8_1-windows_update/error-0x80073712-when-installing-kb-2919355/c5a08cdf-6e41-4b67-b2ae-68f542070840?page=18#LastReply
Was this answer helpful?

2 people found this answer helpful.

0 comments No comments