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.

I simply don't know... I'm a novice at best, and only discovered the joy of using command line frequently late last year. I know more than the average user and love customizing my system directly from the registry, but I lack the internal technical knowledge of how windows operates. What I do know however is KB2919355 issues have plagued both users with and without prior issues in Windows. Why is a very good question... and I think it probably does have to do a lot with Ms. Bradley's hypothesis that it's affecting those users who upgraded to Windows 8 from a prior OS, especially since these issues aren't being replicated on machines running server editions of windows. Not all users fall into this group, but a significant portion probably do. Those that don't may fall into the category of accidental or forced shutdown of windows without realizing Windows Update was running in the background. This is more than likely what caused my issue with installing KB2919355.

We can easily imagine that 10,000 computers are damaged. I think it would be about 0.01% of all Windows 8.1 installations, and Microsoft will not even make a patch for them. Look at this page, for example http://answers.microsoft.com/en-us/windows/forum/windows8_1-winapps/issues-with-apps-not-loadingopening/6da2249b-c218-4f69-8046-8f7ac72138ea?page=3 The file CNBJ2530.DPB of prncacla.inf is corrupted. The date of this post - January 2014 This error is often repeated in other forums. The KB2919355 error leads us to the same packages. Is there the some relationship? The file CNBJ2530.DPB is not a compressed one while others are compressed in this package. Why? Do you remember the ClearCompressionFlag.exe ?

This speaks to the failure of Microsoft, not end users. This was caused by Microsoft, whichever way you slice it. I do believe you make an excellent point that probably plays fairly highly into the issues surrounding KB2919355, however, upgrading from multiple platforms is not the fault of consumers. Microsoft made it impossible to clean install Windows 8 onto a HDD unless it contained a previously installed windows OS, and even then they were pushing upgrades and not selling system build discs except at 4x the price of their initial upgrade price. This took a bit of finagling to get around, and although a simple fix was discovered fairly shortly after Windows was RTM, most users wouldn't have been aware of it. Only those of us with experience in the pros of doing a clean install over an upgrade would have searched and found that if you installed a previous Windows OS on a HDD once, you could reformat the drive to your heart's content and clean install 8 as many times as you wanted. I ended up discovering this a day after multiple failed attempts at installing 8 on a brand new Momentus XT. The problem has always been Microsoft and their wish washy leadership and message with Windows 8, which was rushed to market earlier than it should of been and Microsoft suffered a huge backlash for it. End users can not be blamed for upgrading from multiple platforms when Microsoft was the reason they had to.

I've personally patched way too many machines to agree that the cause is 2919355 itself. What I see is that the majority of the impacted folks have upgrade from multiple platforms. I am not seeing massive issues in the Server skus because they never got a 'free upgrade' and thus never went from build to build to build like the consumer skus did. If the root cause was merely KB2919355 I'd see issues in TechNet and much more widespread than I am. It is a concern that we still are not getting to a root cause and the best bet is a repair install.

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

Anonymous

2014-06-02T22:48:04+00:00

I simply don't know... I'm a novice at best, and only discovered the joy of using command line frequently late last year. I know more than the average user and love customizing my system directly from the registry, but I lack the internal technical knowledge of how windows operates.

What I do know however is KB2919355 issues have plagued both users with and without prior issues in Windows. Why is a very good question... and I think it probably does have to do a lot with Ms. Bradley's hypothesis that it's affecting those users who upgraded to Windows 8 from a prior OS, especially since these issues aren't being replicated on machines running server editions of windows. Not all users fall into this group, but a significant portion probably do. Those that don't may fall into the category of accidental or forced shutdown of windows without realizing Windows Update was running in the background. This is more than likely what caused my issue with installing KB2919355.
Was this answer helpful?

2 people found this answer helpful.

0 comments No comments
0x00000000 40,810 Reputation points

2014-06-02T22:24:23+00:00

We can easily imagine that 10,000 computers are damaged.

I think it would be about 0.01% of all Windows 8.1 installations, and Microsoft will not even make a patch for them.

Look at this page, for example

http://answers.microsoft.com/en-us/windows/forum/windows8_1-winapps/issues-with-apps-not-loadingopening/6da2249b-c218-4f69-8046-8f7ac72138ea?page=3

The file CNBJ2530.DPB of prncacla.inf is corrupted. The date of this post - January 2014

This error is often repeated in other forums.

The KB2919355 error leads us to the same packages. Is there the some relationship?

The file CNBJ2530.DPB is not a compressed one while others are compressed in this package. Why?

Do you remember the ClearCompressionFlag.exe ?
Was this answer helpful?

2 people found this answer helpful.

0 comments No comments
Anonymous

2014-06-02T20:29:43+00:00

This speaks to the failure of Microsoft, not end users. This was caused by Microsoft, whichever way you slice it.

I do believe you make an excellent point that probably plays fairly highly into the issues surrounding KB2919355, however, upgrading from multiple platforms is not the fault of consumers. Microsoft made it impossible to clean install Windows 8 onto a HDD unless it contained a previously installed windows OS, and even then they were pushing upgrades and not selling system build discs except at 4x the price of their initial upgrade price. This took a bit of finagling to get around, and although a simple fix was discovered fairly shortly after Windows was RTM, most users wouldn't have been aware of it. Only those of us with experience in the pros of doing a clean install over an upgrade would have searched and found that if you installed a previous Windows OS on a HDD once, you could reformat the drive to your heart's content and clean install 8 as many times as you wanted. I ended up discovering this a day after multiple failed attempts at installing 8 on a brand new Momentus XT.

The problem has always been Microsoft and their wish washy leadership and message with Windows 8, which was rushed to market earlier than it should of been and Microsoft suffered a huge backlash for it. End users can not be blamed for upgrading from multiple platforms when Microsoft was the reason they had to.
Was this answer helpful?

1 person found this answer helpful.

0 comments No comments
Anonymous

2014-06-02T20:14:40+00:00

I've personally patched way too many machines to agree that the cause is 2919355 itself. What I see is that the majority of the impacted folks have upgrade from multiple platforms. I am not seeing massive issues in the Server skus because they never got a 'free upgrade' and thus never went from build to build to build like the consumer skus did.

If the root cause was merely KB2919355 I'd see issues in TechNet and much more widespread than I am.

It is a concern that we still are not getting to a root cause and the best bet is a repair install.
Was this answer helpful?

2 people found 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