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

those would be in:
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\CatalogsToUninstall

Ps:
Thank You MonarchX! Those tools are cool. And... 4.0's OK.

 

Hi,

Tested on only one install so YMMV but deleting the regkeys and moving the offending files to another location it still did not solve the problem.
Windows rewrote a 0 byte file with the same name as the security cat. file back in %Windir% Servicing\Packages. So DISM still did not work properly.

Cheers, *Wink

 

I think what many are not realizing is that both DISM /Online and DISM /Image: (run offline, after booting from install media) do actually repair the component store, if there is any other issue (aside from the FlightSigning package).

The error about not finding the Source files is not very precise, as it may both find and use the Source files for other repairs, even though in the end it complains about not finding the FlightSigning package.

Sometimes only DISM /Online can repair the component store, even though it gives the error due to the FlightSigning package. DISM run offline may not be able to fix it. I choose not to use the /LimitAccess option, as I do want DISM to use Windows Update as a source to replace a corrupt file, if necessary.

The CBS.log tells what DISM fixed or failed to fix.

Running "DISM /Image:" repair, while your Windows is not actually running can run to 100% completion, if the only issue is the missing FlightSigning package.

So if both sfc /scannow and DISM /Image: ... /RestoreHealth (run offline) complete, your Windows is fine. Also, if DISM /Online only shows the FlightSigning package error in the CBS.log, there is no real need to run DISM offline, except simply to see "100% complete", if that makes you feel better about it and you don't feel like reading the CBS.log.

At some point, I think that Microsoft will change whatever is needed to get DISM to quit looking for the FlightSigning package.

 

After some more analysing...
Used MonarchX method to uninstall the package. It did work.
Two more files I've found on HDD afterwords.
C:\Windows\System32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\Microsoft-Windows-TestRoot-and-FlightSigning-WOW64-Package~31bf3856ad364e35~amd64~~10.0.15063.0.cat
AND
C:\Windows\System32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.15063.0.cat

Do not know what to think of them...

... have deleted those too, did Dism /Online /Cleanup-Image /ScanHealth and ended up with healthy image again.

Will try your method on freshly installed image just to check...

Done. Files still here. Deleted them with no bad things happen. Can anyone explain those files remaining after the uninstall?

 

Hi,

I removed those two as well but it did not make any difference.

Cheers, *Wink

 

What is the "but" word for in this sentence? You mean it did not screw up windows, don't you? "and" would be more like it.
Thanks for the post though *Wink

 

Thanks a lot for these useful hints and the references to these programs. These seem to be very powerful tools indeed.

I just tried them on my test machine, however that Microsoft-Windows-TestRoot-and-FlightSigning package was not displayed in CBSEnum. I first imported the two deleted registry entries and put the files back to C:\Windows\Servicing\Packages, then started CBSEnum but the package was not displayed even after Edit -> make all visible.
According to the name, I expected it to be under Microsoft\Windows but it was not there. Switched to Flat List as advised, and it was not there, either.
Perhaps, it is necessary to reboot after importing the registry entries.

For now, I have just removed them again as well as those files. No problems with them re-appearing so far or DISM errors.

Kind regards,

 

That's reassuring to know. Thanks, I'm content to leave it alone until MS get round to as fix.

 

Yap. The moment that grapes start growing on willow trees.
Cumulative Update for Windows 10 Version 1703 for x64-based Systems (KB4016240)
fixed nothing.
BTW it seems that those files are there for a reason. Not the one the one would like. I need to look into it.
Have you noticed TiWorker having a lot of reads and writes with those files during the updates and repairs in last few months, network traffic increase significantly too while working on them... And the absolute lack of data from microsoft side on that particular package. Not a word.
As it seems to have something to do with commands that will enable the system to trust Windows Insider Preview builds that are signed with certificates that are not trusted by default like:Bcdedit /set {bootmgr} flightsigning on/off andBcdedit /set flightsigning on/off
andWHQL Test Signature Program and Microsoft Test Root Authority ,I wonder if testing was done on all of our machines without our knowledge and consent, most probably to find a way to prevent/disable Microsoft Toolkit kms crack of windows. To no avail obviously...

In lass black scenario... after the creators update these updates followed:
1) Cumulative Update for Windows 10 Version 1703 for x64-based Systems (KB4016240)
2) Windows Malicious Software Removal Tool for Windows Insider Preview and Server Technical Preview x64 - April 2017 (KB890830) What the F***?! I've never installed Windows Insider Preview!
3) Security Update for Adobe Flash Player for Windows 10 Version 1703 (for x64-based Systems) (KB4018483)
4) Definition Update for Windows Defender - KB2267602 (Definition 1.241.637.0)

so it might be Malicious Software Removal Tool trick to fix some malware in unusual way, and Microsoft legendary lack of integrity to fulfill the job of maintaining the updates with no errors in databases. Patch that needs a patch to patch a patch sort of a way.

or ... have you noticed Windows Subsystem for Linux feature / must have developer mode enabled... sort of line for winux? Sounds like Crislam religion does it not? Just kidding, I like that feature. Well, without necessity of developers mode, but it's still beta.

 

Hi,

I mean that DISM is still not working like it should. I should have uninstalled the files iso moving them.

Cheers, *Wink

 

Remove all the files mentioned and registry entries. RESTART is mandatory for the changes in registry to work.
Do the manual or MonarchX way no matter.
so to recapitulate:
all the instances of FILES:
C:\Windows\servicing\Packages\Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.15063.0.cat
C:\Windows\servicing\Packages\Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.15063.0.mum
C:\Windows\System32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\Microsoft-Windows-TestRoot-and-FlightSigning-WOW64-Package~31bf3856ad364e35~amd64~~10.0.15063.0.cat
C:\Windows\System32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.15063.0.cat

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

If used MonarcshX way
under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\CatalogsToUninstall
all Microsoft-Windows-TestRoot-and-FlightSigning related keys are to be deleted after first reboot.
Reboot.

DO
dism /online /Cleanup-Image /StartComponentCleanup /ResetBase

Now do
DISM.exe /Online /Cleanup-image /Restorehealth

If not successful do SFC /SCANNOW if it works
repeat DISM.exe /Online /Cleanup-image /Restorehealth
or better
Dism /Online /Cleanup-Image /RestoreHealth /Source:WIMath to\install.wim:1 /LimitAccess

If still not ok
Reboot to recovery mode CMD amd run
sfc /SCANNOW /OFFBOOTDIR=c:\ /OFFWINDIR=c:\Windows (check the drive letters first with DISKPART)

And than try either

dism /mount-image /imagefile:F:\sources\install.wim /index:1 /mountdir:C:\mount
Where F is dvd drive with windows dvd plus:
Dism /Image:C:\offline /Cleanup-Image /RestoreHealth /Source:c:\mount\windows
do not forget to dismount the image when finished

or simply try this first
Dism /Image:C:\offline /Cleanup-Image /RestoreHealth /Source:WIM:full path to\install.wim:1 /LimitAccess

You probably have more errors than just Creators update one.
AND USE THE 1703 INSTALL IMAGE!!! not the older one, and try that to be MSDN one, not Windows media creation one, they tend to fail in this job!

Hope you never have to reinstall windows again!

If you feel up to it you can use THIS to remove the offending packages from the iso (wim in the iso) too and repack the clean instalation iso for future use and you can also integrate latter updates with NTlite if need be...

 

Thanks for finding more files for those packages in CatRoot directory. I am sure entries for it exist somewhere else. I do know DISM problems were very common to Insider Previews even for Anniversary Edition.

MS either:
- Knew about the TestRoot DISM problem and decided to do nothing about it
- Created the problem on purpose (sinister...)
- Did not know because of whichever reason (poor integrity, often deep-level developers/programmers do not bother with checking out functions that an average user would utilize)


BTW, for those who think its too tedious and time consuming to use DISM commands manually to remove packages, I strongly suggest MSMG Toolkit from MyDigitalLife forums - it does exactly what you want. I would wait for the next version that is days or hours away from being released because at the moment it fully supports only slightly older builds of Creator's Update (15053 or 15043), but that did not prevent me from making a fully...er... semi-fully functional custom Install.wim image with a ton of apps removed using version 6.9. It caused a slight issue with one program because that program does not launch unless System Restore is present, even if System Restore is disabled and non-functional. Removing System Restore was one of the Advanced MSMG Toolkit options with a visible warning, but since I never used System Restore, I chose to have that package removed from Install.wim. Luckily for me MSMG Toolkit maker uploaded the needed System Restore Package CAB files for me and although my custom Install.wim is not perfect for my needs (no System Restore for that ONE important program!), my current OS is fully functional and heavily debloated. MSMG Toolkit suggests certain packages for removal, but you can create a custom list of all packages you want gone and it will remove them along with related associations and registry entries, thus making DISM and SFC happy *Tongue .

I have this idea of acquiring the list of ALL Enterprise LTSB Install.wim package names because LTSB is as raw as it gets and then removing all or most packages from my legit Retail Pro Install.wim that do not exist in LTSB Install.wim. That way I would get all 3 aspects - lean LTSB-like OS, a choice to leave just the packages I want, and having non-feature updates that LTSB does not have because its a LONG TERM branch.

P.S. - I could not respond to PM's because I have not made enough posts to get that feature... Forum rules these days crack me up!