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

• I followed the procedure explained by Eagle51 and found it successfull. After doing that, everything was perfect: CheckHealth, ScanHealth, Restore Health, sfc ... everything related with DISM. So, many thanks and congratulations to Eagle51!!!.
• Just to make a double-check, I imported back to the registry the two keys mentioned by him:

• [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]
  

and previously exported to my Desktop, as Eagle51 explained ... and the DISM RestoreHealth error was again there.

But, what I would like to know is if someone has found a definitive solution (without having to edit the registry) until MSFT decide to repair this problem in any way.

 

Hello *Smile

I'd like to give Eagle51's recommendation a try but... how can I delete those two keys after exporting them? I do not have the right to do so, it says...

?

 

Right click on the Registry key that you want to delete (the ones mentioned above), select Permissions, choose Administrators, tick Full Control and Accept

 

Okay, I will try it!

Just to be crystal clear here, though, are these the two keys I should first export and then delete?








And so, I export the key (left pane) and then I delete that entire key from the left pane of the Registry Editor, after gaining Administrative rights? Do I delete the highlighted key(s), as shown in my screenshots or just the underlined values?

I have clean-installed the Creators Update using the ESD-ISO, which I got from the Media Creation Tool. Will Eagle51's method work for me?

Thank you.

 

Yes, this is the way.
Keep in a safe place the exported Keys, because you can import them Again if somthing goes wrong.
You have to delete the entire key (s). I mean the highligthed one (s).

 

Okay, thank you very much, I'll definitely try this at some point in time today, a bit later though, even though I've just finalized my clean installation of the Creators Update, and everything -besides DISM- is functioning perfectly!

Please, reply to my last inquiry: I used the ESD-ISO from the Media Creation Tool, and thus I have the install.esd on my thumb drive.

- Will this method work for me, as well?

Thanks a lot!

 

Yes, of course. I am completly sure because it is the same way i've used for my instalation.
And sorry about my bad english, I am spanish, living in Madrid.

 

The method also work for me! Else I wouldn't be able to use Chrome to write this message anyway.
CheckHealth still says my component store is repairable though. I wanted to do a clean install of creators update, but I have no idea how to do that and if it will affect my documents, programs etc.
Anyone who knows a good guide to do so?

 

Well... *Sad unfortunately *Sad it does not work for me...

I think it has to do with the fact that I am using the install.esd file from my ESD-ISO.

Here are the results of DISM, after exporting the two Registry keys I've shown above, deleting them, and rebooting.

After rebooting, SFC /SCANNOW does not find any integrity violation. But DISM still fails...................






Note_1: Guys, is it sure that I have deleted the appropriate Registry keys? Because one key from those I have deleted is not the same as Eagle51's... The point is, that I have not found the keys he mentions in my Registry. That is why I've posted screenshots of my Registry, and asked... Have I removed the appropriate keys then, or not? Why is DISM not working in my system, with this trick?

Note_2: Since DISM is not working with this trick, I decided to add (restore) the 2 deleted keys back in my Registry. I cannot! When I double-click on them, they are saved on my Desktop, I get an error "Error accessing the registry". This is happening when I try to import those 2 keys from inside RegEdit, as well....

 

Sorry about the misunderstanding. I was using my iPhone to see your previous post and I could´nt see it clearly. Now in my PC I can see that the second key you deleted is not correct. So, please, import to your registry the saved keys and repeat tehe procedure with exactly the two following keys:

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

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

Good luck!

 

Regarding your note 2, you have first to give administrative rights to the folder that contains the keys you have deleted:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageIndex,
So, right click, properties, permissions, administrator, full control.
After that you can import your two saved key.
Dont to go back when the importation finished and restore the old permisions (unchek Administrators/Permissions/Full Control)
Goog luck!

 

Awesome, it works, thank you very much!!! *Biggrin *Biggrin

1) I restored both of the exported-deleted Registry keys, thanks @gommace for the reg-tricks!
2) After rebooting I exported+deleted the right keys this time!
3) I rebooted.

The results:






Thank you @Eagle51 and @gommace for your solution and support! *Smile
@Brink, wouldn't you like to have a look at this? *Smile

 

It's still not really working as expected.
1. I also first deleted the wrong keys. Although browsers were working fine again, dism failed;
2. Replaced, correct ones deleted. But reboot got stuck at 'configuring windows' - > hard reboot. Then performance issues, but dism restore worked. And now Browsers won't work again...

 

Hi,

Did you import the exported keys afterwards (I now see you did) and run DISM again ?
I'm asking because this trick sounds like side-stepping the issue. With all due respect to the person proposing it, it does not make sense to me.

Cheers, *Wink

 

I completely agree. If we come to understand the problem better, define it as ignorable, I'm okay with a workaround to allow DISM to complete its tasks. I don't think this is the case.

I'm going to dig into PowerShell and have it show all installed packages/components. Perhaps this will yield some results while removing/including the Insiders program