Creators update component store shows corruption but unable to repair

Hi,

You should not be technically moving/removing such packages, but uninstalling them.

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,

gommace said:

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

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.

Hi,

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

Cheers,

fdegrove said:

Hi,

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

Cheers,

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

MonarchX said:

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

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,
DAC324

DonCuthbert said:

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

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

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

Hi,

ibach said:

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

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

Cheers,