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.

On my opinion systems were damaged before the date when KB2919355 became available. The crash of KB2919355 only indicates the damage that had been hidden. Microsoft is still silent. I try to find out relationships. Corruption may be because of the installation 3-rd party programs, an installation .Net Framework from some external source, an improper installation of Windows updates and so on. The order in which updates were installed, it is very significant. If you upgraded your system in that day when there was the Windows 8 release, you install all updates in series. If you have upgraded your system resently, you may install them in arbitrary order or skip some steps. As you can see, automatic update was on and there is no an obvious reason in this case. It is not the longest soap opera in history yet. Quest with КВ2756872 continued about three months.

If a hypothesis is the crash of KB2919355 only indicates prior damage that had been hidden, then it would have been pretty well hidden damage that didn't show in /restorehealth, /scannow, chkdsk with bad cluster and frees space recovery, or in normal day to day operations. I had no issues with Win 8.1 Pro x64 prior to the KB2919355, and the prior day to attempting 2919355 had run /restorehealth and /scannow with no errors generated during either, as well a chkdsk that evening, again with no errors generated. I had just finished a month long clean install and customization that would culminate in 2919355. I was a day away from doing a WIM of my system since it was customized the way I wanted it and had no errors, with the plan of replacing the Refresh WIM with this custom one. While prior corruption on some systems may have exacerbated the issues surrounding KB2919355, it isn't the source of the problem.

We have only 4 red flags in the TS post here, 10 red flags in the related thread and about 150 red flags in the parent thread. It is too little. If the KB2919355 is the only reason of the problem we would have thousands red flags and Microsoft easily fixed a bug.

I'm not sure what you mean by flags, however you're entitled to your opinions just as everyone is, but don't confuse opinion with facts. The fact is KB2919355 caused corruption on not just a few hundred users' computers and workstations, but thousands. Seeming as the probability of all computers being affected had corruption prior is so high (a ratio of billions to one) it renders such a hypothesis as fundamentally flawed. Its ocam's razor... the most likely cause is the simplest, Microsoft screwed up. You have to give them credit though, they screwed up so bad, that have no idea what caused the screw up. This reminds me a problem I had two weeks ago with ICS sharing from my phone. I'm extremely vigilant about my firewall, and have it locked down extremely well... so well in fact, I wasn't able to create an incoming connection from my device, as I put multiple barriers in place to prevent inbound connections and any software that required an inbound connection was locked down even more so than others. The simplest of answers is almost always the correct answer.

If a hypothesis is the crash of KB2919355 only indicates prior damage that had been hidden, then it would have been pretty well hidden damage that didn't show in /restorehealth, /scannow, chkdsk with bad cluster and frees space recovery, or in normal day to day operations. I had no issues with Win 8.1 Pro x64 prior to the KB2919355, and the prior day to attempting 2919355 had run /restorehealth and /scannow with no errors generated during either, as well a chkdsk that evening, again with no errors generated. I had just finished a month long clean install and customization that would culminate in 2919355. I was a day away from doing a WIM of my system since it was customized the way I wanted it and had no errors, with the plan of replacing the Refresh WIM with this custom one. While prior corruption on some systems may have exacerbated the issues surrounding KB2919355, it isn't the source of the problem. I had the exact same scenario. No problems until after the failed update. Prior to that time no errors were generated using /restorehealth.

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

0x00000000 40,810 Reputation points

2014-06-02T17:44:03+00:00

On my opinion systems were damaged before the date when KB2919355 became available.

The crash of KB2919355 only indicates the damage that had been hidden.

Microsoft is still silent.

I try to find out relationships.

Corruption may be because of the installation 3-rd party programs, an installation .Net Framework from some external source, an improper installation of Windows updates and so on. The order in which updates were installed, it is very significant. If you upgraded your system in that day when there was the Windows 8 release, you install all updates in series. If you have upgraded your system resently, you may install them in arbitrary order or skip some steps. As you can see, automatic update was on and there is no an obvious reason in this case. It is not the longest soap opera in history yet. Quest with КВ2756872 continued about three months.
Was this answer helpful?

0 comments No comments
Anonymous

2014-06-02T18:18:18+00:00

If a hypothesis is the crash of KB2919355 only indicates prior damage that had been hidden, then it would have been pretty well hidden damage that didn't show in /restorehealth, /scannow, chkdsk with bad cluster and frees space recovery, or in normal day to day operations.

I had no issues with Win 8.1 Pro x64 prior to the KB2919355, and the prior day to attempting 2919355 had run /restorehealth and /scannow with no errors generated during either, as well a chkdsk that evening, again with no errors generated. I had just finished a month long clean install and customization that would culminate in 2919355. I was a day away from doing a WIM of my system since it was customized the way I wanted it and had no errors, with the plan of replacing the Refresh WIM with this custom one.

While prior corruption on some systems may have exacerbated the issues surrounding KB2919355, it isn't the source of the problem.
Was this answer helpful?

0 comments No comments
0x00000000 40,810 Reputation points

2014-06-02T18:59:59+00:00

We have only 4 red flags in the TS post here, 10 red flags in the related thread and about 150 red flags in the parent thread. It is too little. If the KB2919355 is the only reason of the problem we would have thousands red flags and Microsoft easily fixed a bug.
Was this answer helpful?

0 comments No comments
Anonymous

2014-06-02T19:55:17+00:00

I'm not sure what you mean by flags, however you're entitled to your opinions just as everyone is, but don't confuse opinion with facts.

The fact is KB2919355 caused corruption on not just a few hundred users' computers and workstations, but thousands. Seeming as the probability of all computers being affected had corruption prior is so high (a ratio of billions to one) it renders such a hypothesis as fundamentally flawed. Its ocam's razor... the most likely cause is the simplest, Microsoft screwed up. You have to give them credit though, they screwed up so bad, that have no idea what caused the screw up. This reminds me a problem I had two weeks ago with ICS sharing from my phone. I'm extremely vigilant about my firewall, and have it locked down extremely well... so well in fact, I wasn't able to create an incoming connection from my device, as I put multiple barriers in place to prevent inbound connections and any software that required an inbound connection was locked down even more so than others. The simplest of answers is almost always the correct answer.
Was this answer helpful?

0 comments No comments
Anonymous

2014-06-02T20:05:55+00:00

If a hypothesis is the crash of KB2919355 only indicates prior damage that had been hidden, then it would have been pretty well hidden damage that didn't show in /restorehealth, /scannow, chkdsk with bad cluster and frees space recovery, or in normal day to day operations.

I had no issues with Win 8.1 Pro x64 prior to the KB2919355, and the prior day to attempting 2919355 had run /restorehealth and /scannow with no errors generated during either, as well a chkdsk that evening, again with no errors generated. I had just finished a month long clean install and customization that would culminate in 2919355. I was a day away from doing a WIM of my system since it was customized the way I wanted it and had no errors, with the plan of replacing the Refresh WIM with this custom one.

While prior corruption on some systems may have exacerbated the issues surrounding KB2919355, it isn't the source of the problem.

I had the exact same scenario. No problems until after the failed update. Prior to that time no errors were generated using /restorehealth.
Was this answer helpful?

2 people found this answer helpful.

0 comments No comments