New
#91
Last edited by ibach; 27 Apr 2017 at 07:53.
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.You should not be technically moving/removing such packages, but uninstalling them.
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,
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?
Last edited by ibach; 28 Apr 2017 at 04:55.
Hi,
I removed those two as well but it did not make any difference.
Cheers,
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
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/offandBcdedit /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.
Last edited by ibach; 28 Apr 2017 at 08:03.