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.

@ RobbieMcLaughlan That post was addressed to JoeM999 Thanks for your information anyway. I think you can get free help with kb2919355 from Microsoft till June,8 We have a little time. You may continue this thread as you wish. Open the folder C:\Windows\System32\Dism in the file explorer in a table mode (interested in the date of changing) and make a screenshot of all files in the folder , please. UPD: also try to - check you computer for viruses & malware - disable Superfetch (SysMain) in control panel - administration - services

Hi I carried out the above and the logs are stored in the following path https://onedrive.live.com/?cid=037B7A0F229FFF0C&id=37B7A0F229FFF0C%215904 I see on the next message you sent me to contact Microsoft support. Should I still do this? Cheers

The best answer... no one knows. Unfortunately, it's unlikely Microsoft will figure it out either, or if they do, it'll be a year or more from now. The only successful way of repairing this error is to do a repair install with the 8.1 installation media (run the installer from inside windows, select keeps all files/settings, and install - you'll also need the generic PK for your version of windows which is available through google). I have a hunch that when the KB2919355 install goes wrong, dism is corrupted. I don't know this for sure, however even if you use the /source flag and point to either the install.wim (install.esd) or a mounted 8.1 installation with no corruption, you'll still receive an error. This, at least to me, points to some sort of corruption within the DISM utility itself. Since DISM is the only program capable of repairing component store corruption, the only way to cure the corruption that is causing this error is a repair install. EDIT: Just something I noticed, the dism log would be found in the dism folder. The cbs log is what SFC writes to, the dism log what dism writes to (unless it also writes to the cbs log). According to a few other forums I checked out, the result would still be the same, with both logs showing no errors and a repair install still required. Please see the eightforums link to see the experience reproduced below: http://www.eightforums.com/tutorials/26512-dism-fixing-component-store-corruption-windows-8-a.html

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 ? Since you posted your reason as as to why Microsoft won't or refuses to deal with this issue, then then perhaps you will address this issue or ask Microsoft why they won't deal with this issue. I receive an error message when using /Restorehealth The restore operation failed. Either the repair source was not found or the component store cannot be repaired. Error: 0x800f081f DISM failed. No operation was performed. For more information, review the log file. *************** After the error message this is what appears in the CBS.log: Checking System Update Readiness. Summary: Operation: Detect and Repair Operation result: 0x0 Last Successful Step: Entire operation completes. Total Detected Corruption: 0 CBS Manifest Corruption: 0 CBS Metadata Corruption: 0 CSI Manifest Corruption: 0 CSI Metadata Corruption: 0 CSI Payload Corruption: 0 Total Repaired Corruption: 0 CBS Manifest Repaired: 0 CSI Manifest Repaired: 0 CSI Payload Repaired: 0 CSI Store Metadata refreshed: True Rather than providing us with conjecture and opinions and reasons why "the company" will not deal with the issue, many of us would appreciate you taking the time to illuminate me and others as to what this means. DISM reports an error but the CBS.log says there is no corruption. Once again, many of us would appreciate someone ACTUALLY addressing why this is the case rather than than posts which relate to suppositions, conjecture and speculation. Again: What does this mean to real users rather than a response with something like "imagine that 10,000 computers are damaged"? I will be anxiously awaiting your analysis and answer.

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-04T13:37:07+00:00

@RobbieMcLaughlan

That post was addressed to JoeM999

Thanks for your information anyway.

I think you can get free help with kb2919355 from Microsoft till June,8

We have a little time.

You may continue this thread as you wish.

Open the folder   C:\Windows\System32\Dism in the file explorer in a table mode (interested in the date of changing) and make a screenshot of all files in the folder , please.

UPD: also try to

-   check you computer for viruses & malware

-   disable Superfetch   (SysMain) in control panel - administration - services
Was this answer helpful?

0 comments No comments
Anonymous

2014-06-04T04:24:41+00:00

Hi

I carried out the above and the logs are stored in the following path

https://onedrive.live.com/?cid=037B7A0F229FFF0C&id=37B7A0F229FFF0C%215904

I see on the next message you sent me to contact Microsoft support.

Should I still do this?

Cheers
Was this answer helpful?

0 comments No comments
Anonymous

2014-06-03T00:10:25+00:00

The best answer... no one knows. Unfortunately, it's unlikely Microsoft will figure it out either, or if they do, it'll be a year or more from now.

The only successful way of repairing this error is to do a repair install with the 8.1 installation media (run the installer from inside windows, select keeps all files/settings, and install - you'll also need the generic PK for your version of windows which is available through google). I have a hunch that when the KB2919355 install goes wrong, dism is corrupted. I don't know this for sure, however even if you use the /source flag and point to either the install.wim (install.esd) or a mounted 8.1 installation with no corruption, you'll still receive an error. This, at least to me, points to some sort of corruption within the DISM utility itself. Since DISM is the only program capable of repairing component store corruption, the only way to cure the corruption that is causing this error is a repair install.

EDIT:

Just something I noticed, the dism log would be found in the dism folder. The cbs log is what SFC writes to, the dism log what dism writes to (unless it also writes to the cbs log). According to a few other forums I checked out, the result would still be the same, with both logs showing no errors and a repair install still required. Please see the eightforums link to see the experience reproduced below:

http://www.eightforums.com/tutorials/26512-dism-fixing-component-store-corruption-windows-8-a.html
Was this answer helpful?

0 comments No comments
Anonymous

2014-06-02T23:57:04+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 ?

Since you posted your reason as as to why Microsoft won't or refuses to deal with this issue, then then perhaps you will address this issue or ask Microsoft why they won't deal with this issue.

I receive an error message when using /Restorehealth

The restore operation failed. Either the repair source was not found or the component store cannot be repaired.

Error: 0x800f081f

DISM failed. No operation was performed.

For more information, review the log file.

***************

After the error message this is what appears in the CBS.log:

Checking System Update Readiness.

Summary:

Operation: Detect and Repair

Operation result: 0x0

Last Successful Step: Entire operation completes.

Total Detected Corruption: 0

CBS Manifest Corruption: 0

CBS Metadata Corruption: 0

CSI Manifest Corruption: 0

CSI Metadata Corruption: 0

CSI Payload Corruption: 0

Total Repaired Corruption: 0

CBS Manifest Repaired: 0

CSI Manifest Repaired: 0

CSI Payload Repaired: 0

CSI Store Metadata refreshed: True

Rather than providing us with conjecture and opinions and reasons why "the company" will not deal with the issue, many of us would appreciate you taking the time to illuminate me and others as to what this means. DISM reports an error but the CBS.log says there is no corruption. Once again, many of us would appreciate someone ACTUALLY addressing why this is the case rather than than posts which relate to suppositions, conjecture and speculation. Again: What does this mean to real users rather than a response with something like "imagine that 10,000 computers are damaged"?

I will be anxiously awaiting your analysis and answer.
Was this answer helpful?

0 comments No comments