Windows 10: Creators update component store shows corruption but unable to repair

Since Creators update, whenever I run

Dism /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth

It results in
"The component store is repairable.
The operation completed successfully."

Sfc /scannow shows no errors.


Now when I use

"DISM /Online /Cleanup-Image /RestoreHealth" or

" DISM /Online /Cleanup-Image /RestoreHealth /Source:E:\sources\install.wim" (did with ESD too)

It results in

"The source files could not be found.
Use the "Source" option to specify the location of the files that are required to restore the feature.
For more information on specifying a source location, see Configure a Windows Repair Source.
The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log"


Both clean install and inplace upgrade don't solve the problem

Also, event viewer shows always these administrative errors with ids 7000 and 37 and I don't know if it is related with this dism issue.

:)

 

Windows 10 - Checking for Updates too slow

And by the way, DISM is not working actually. You can check reports here: Creators update component store shows corruption but unable to repair - Windows 10 Forums

and here: Use DISM to Repair Windows 10 Image

Seems that Creators Update is a mess at this moment.

 

Windows 10 Creator Update 1703 build 15063.138 has a package with wrong signature, causing DISM to fail while trying to RestoreHealth.

Hallo,

possibly, there is a solution here:
https://www.tenforums.com/performance-maintenance/81413-creators-update-component-store-shows-corruption-but-unable-repair-post991296.html#post991296

Affected is the package Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.15063.0 . There are two occurrences of that package in the registry.

For some reason, DISM is unable to load it from a mounted install.wim or install.esd.

Also note the "Test" in the name of the file. Apparently, it is a remnant from a previous testing build.

The suggestion therefore is to delete these two registry keys (export them first in case you need them back later):

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageIndex\Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~0.0.0.0]

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.15063.0]

In addition, the file with names starting with Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64 have to be moved out of the folder c:\Windows\Servicing\Packages so that DISM will not find it any more.

After these measures, there are no more errors when running DISM /online /cleanup-image /restorehealth .

Kind regards,

 

Hi, given the in-place upgrade install failure, try doing basic checks on your disk first. Do you mean the in-place upgrade install completed, but then your OS failed having booted up, or that the in-place upgrade installation failed to complete?

1. Download and run Crystal Diskinfo (free). It reports Good/Caution/Bad based on SMART params.
Do not proceed unless Good.

2. From an admin command prompt
[Windows key + X, click command prompt (admin)]
chkdsk C: /F
Your PC will need to restart.
Post back the result, which you can get after a restart as follows:
How do I see the results of a CHKDSK that ran on boot? - Ask Leo!

 

My os booted fine every time and it seemed ok , it's just these scan and check health always show corruptions.

I've done chkdsk also but forgot to mention and I am on SSD. It finished in few seconds without any errors found.

Here are the results of the DISM /Online /Cleanup-Image /RestoreHealth

 

Hello All Members

Windows 10 Professional x64 (Slovak Language) Version - 1703 / Build 15063.14

When I use the command in command prompt - sfc /scannow





I open Power Shell and write these commands:

Some Pictures:









Propably i have same problem as Dyabzhee. And we are not alone with this issue. Yesterday i used google to found something informations about this issue and found this topic on the Sysnative.com - https://www.sysnative.com/forums/windows-update/22510-creators-update-dism-repairable-but-cannot-find-source-files-sfcfix-zero-errors.html

 

Here is small information from CBS.log - when i use command prompt and this commands:

 

I can confirm that. Both the systems I have upgraded, one an x86 Pro 15063.13 the other x64 Home 15063.13, report "The component store is repairable" when using:
DISM /Online /Cleanup-Image /ScanHealth

The commands...
Dism /Online /Cleanup-Image /RestoreHealth
Dism /Online /Cleanup-Image /RestoreHealth /Source:esd:<full path to install.esd>:1
DISM /Online /Cleanup-Image /RestoreHealth /Source:esd:<full path to install.esd>:1 /limitaccess
(where install.esd is the one from the install USB made by the MCT and used to perform the upgrade)

..fail with: Code: C:\WINDOWS\system32> DISM /Online /Cleanup-Image /RestoreHealth /source:esd:d:\x64\sources\install.esd:1 /limitaccess Deployment Image Servicing and Management tool Version: 10.0.15063.0 Image Version: 10.0.15063.0 [===========================90.1%==================== ] Error: 0x800f081f The source files could not be found. Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see Configure a Windows Repair Source. The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log C:\WINDOWS\system32>[/quote]
Other than that, there are no apparent issues. Both systems appear fully functional.

 

Apparently....

https://social.technet.microsoft.com...in10itprosetup

 

Even more interesting: /checkhealth gives my recent upgrades a clean bill of health while /scanhealth gives the error that Bree reports:



Bottom line: I concur that this is a problem with the 15063.13 image that's now standard for recent upgrades/clean installs. Hopefully, MS will fix it sooner rather than later. I'm upvoting Bree's feedback hub post, if I can find it (if you post the title to your feedback hub input, that will help, Bree: TIA).
--Ed--

 

You won't, I don't have an MS account so can't post one *Smile
Robert Richter, the OP of the thread I linked to may have posted one...

 

More interesting data: reading up on using DISM I learned that it sometimes has more difficulty with esd files than with wim files. The install file in the Media Creation Tool version of 1703 is install.esd. So I hied me off to MSDN and downloaded the latest and greatest ISO file from there and found exactly the same repair issue from that supposedly more usable, DISM friendly version:



I'll be blogging about this tomorrow, but it seems pretty clear that whatever is causing the issue with component store corruption is (a) coming from Microsoft and (b) not currently fixable through ordinary DISM measures. I've now tried both the ESD file from the media I used to upgrade my OS and the WIM file from the MSDN ISO, both with the same failure.
Very interesting!
--Ed--

 

Yeah. Could you also check administrative event viewer errors If it is not a problem? I keep getting them on every install

 

I just checked my Windows logs looking for Critical, Error, and Warning items and I have very little (almost no) overlap with what I see showing in your post. No DCOM items following the upgrade to Creators Update, in fact.
HTH,
--Ed--

 

No change after today's Cumulative Update KB4015583 Windows 10 v1703 Build 15063.138

Code: C:\WINDOWS\system32> DISM /Online /Cleanup-Image /RestoreHealth Deployment Image Servicing and Management tool Version: 10.0.15063.0 Image Version: 10.0.15063.0 [===========================98.7%========================= ] Error: 0x800f081f The source files could not be found.[/quote]