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

Hi,

That's just one side of the issue really.
Deleting the reg keys or running DISM in safe mode amount to the same.Hence, etc. etc.

Bottom line, most systems do not have the problems DISM suggests they have and yes, MS should have fixed this long ago.
And yes, MS should also not rush out such a major release without resolving this first.

Creators Update also comes with other problems that are much more difficult to resolve.

Cheers, *Wink

 

I have to disagree. I don't see either of methods as being solutions.
The registry changes were billed by some as a workaround for that specific package. I see it as hiding the problem and not fixing the root cause.

The offline method of running DISM is a workaround for not being able to fix it online, but it does resolve the root cause.

Neither should be considered final resolutions and should still be fixed by Microsoft.

 

Hi,

Actually, you do agree but do not understand why.
Both workarounds achieve the same thing: DISM is being fooled.

I'd like to hear from people claiming running DISM either way actually and factually resolved anything when sfc /scannow did not throw up an error in the first place.

Best and welcome to this Forum *Wink

 

Been a long-time lurker, decided to actually sign up for this thread. Thank you for the warm welcome.

Can you clarify as to my misunderstanding? How is DISM being fooled when running in an offline capacity?

 

Hi,

It ignores the registry entries, that's why.

Cheers, *Wink

 

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).

 

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[/quote] out of that folder so DISM cannot find it.
After that, no more errors.

Kind regards,

 

Hard disk sentinel
- tends to give good indications and more detailed
Macrorit Diskscanner
- free surface scanner

 

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

 

out of that folder so DISM cannot find it. After that, no more errors.Kind regards,DAC324[/quote] 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.

 

Hi,

I have no reason to doubt your suggestion, especially since I have not tested it myself, but I have just run SFC /SCANNOW and the Registry keys I have deleted have not been restored in my Registry. See posts : 39, 40 and 41 of this thread, please. I have not run DISM again, after that time, but running SFC a few minutes ago has not restored those 2 keys back. Finally, since deleting them I have not faced any issue with my OS. I agree that those should be left in peace (undeleted), though.

EDIT:
I have just run DISM, as well. Those two Reg keys I have deleted (see post 39) have not been restored.






I tend to agree though that this is not an appropriate fix.

 

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.

 

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:\x64\sources\install.esd:2 /ScratchDir:C:\Scratch[/quote] (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.