Creators update component store shows corruption but unable to repair

fdegrove said:

It ignores the registry entries, that's why.

Well how about that. Guess it makes sense since the hive isn't loaded. Seems like a glaring oversight in DISM to not warn of the fact it has limited abilities in that mode.

In the earlier post crystal diskinfo was recommended. I just downloaded it and it reported drive as good. That contradicts the UEFI diagnostics which indicate a failing drive. The crystal diskinfo is only using the smart test and can mislead users of the software as it only performs one test. The uefi diagnostics use short dst and long dst tests. This computer always passes the uefi smart test. It always fails the short dst test. The long dst can never run as the short one fails. Seatools for windows or the western digital drive tests may be as good as or better than the uefi diagnostics. I am looking for the best way to test internal hard drives as one of my drives has had recent chkdsk errors but all uefi studies have passed. I am wondering whether sanitizing the drive using the bios reduces the number of chkdsk errors (incorrect information in file record segments, attribute records corrupt, orphaned files).

gommace said:

1. 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!!!.
2. 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.

There is one additional step you will have to perform in order to be successful: Move the file

Code:

C:\Windows\servicing\Packages\Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.15063.0.mum

out of that folder so DISM cannot find it.
After that, no more errors.

Kind regards,
DAC324

idk what happened but my system health report is back to normal now. weird.

DAC324 said:

There is one additional step you will have to perform in order to be successful: Move the file

Code:

C:\Windows\servicing\Packages\Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.15063.0.mum

out of that folder so DISM cannot find it. After that, no more errors.Kind regards,DAC324

Although removing the registry keys and/or moving that location may work, it is still not a proper way to get rid of a system package as it can break the OS. You should not be technically moving/removing such packages, but uninstalling them. A good example is Cortana. Moving/deleting/renaming the Cortana package gets rid of SearchUI running in the background, but breaks Metro Start UI AND SFC /ScanNow can restore both - the deleted registry entries and the moved/deleted/renamed package folder.

To properly get rid of a system package like that you should either use WIM_Tweak (very old and outdated, not recommended) or use another more modern method that always worked for me to get rid of all packages I did not want:
- Search Google for NSudo 4.3 (or 4.0, both can be found through MDL forums), search for CBSEnum, and download both packages.
- Run NSudo 4.3 (4.0 may also work) as Admin to launch CBSEnum with All Privelages as Trusted Installer.
- Take ownership of the correct registry entry in CBSEnum (from the Edit button at the top of CBSEnum).
- Use the Flat List to view packages, find the 2 Microsoft-Windows-TestRoot packages, and select/highlight both packages.
- Right-click on highlighted packages, make both packages visible, de-couple both packages, and only then select to uninstall both packages (at once).
- Restart, search for remaining package registry entries, remove the registry entries (which would not be the in same place, but in ToBeUninstalled or similar-named registry folder).
- Restart again and you're done correctly uninstalling the package.
- You can now proceed to safely run DISM RestoreHealth and SFC /ScanNow without fear or having those packages restored and those error re-appearing.

Me too ... but my big concern is what would happen if I needed to repair the system.

Guys like people have said before just wait for Microsoft to fix this issue as well as the other issues they have given us. I have learned that when you try to fix it on your own it just causes more issues down the road.

gommace said:

... but my big concern is what would happen if I needed to repair the system.

Boot from the install media or boot to Advanced Startup. Get the Command prompt and do an offline repair.

Code:

DISM /Image:C:\ /Cleanup-Image /RestoreHealth /Source:ESD:D:\x64\sources\install.esd:2 /ScratchDir:C:\Scratch

(We have DonCuthbert to thank for this)
Use DISM to Repair Windows 10 Image

On my 15063.138 system using DISM offline completes successfully.

Notes:

• use ...esd:1 for Pro, ...esd:2 for Home.
• you have to create the 'C:\Scratch' folder yourself before you try this command.