Page 10 of 15 FirstFirst ... 89101112 ... LastLast
  1.    27 Apr 2017 #91
    Join Date : Oct 2015
    Posts : 16
    10

    Quote Originally Posted by MonarchX View Post
    - 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).
    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.
    Last edited by ibach; 27 Apr 2017 at 07:53.
      My ComputerSystem Spec
  2.    27 Apr 2017 #92
    Join Date : Oct 2015
    Posts : 2,048
    Windows 10 Pro X64

    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,
      My ComputersSystem Spec
  3.    27 Apr 2017 #93
    Join Date : Jul 2015
    Posts : 58
    Windows 10

    Quote Originally Posted by gommace View Post
    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.
      My ComputerSystem Spec
  4.    28 Apr 2017 #94
    Join Date : Oct 2015
    Posts : 16
    10

    To MonarchX... some more files I've found... What of them?


    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.
      My ComputerSystem Spec
  5.    28 Apr 2017 #95
    Join Date : Oct 2015
    Posts : 2,048
    Windows 10 Pro X64

    Hi,

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

    Cheers,
      My ComputersSystem Spec
  6.    28 Apr 2017 #96
    Join Date : Oct 2015
    Posts : 16
    10

    Quote Originally Posted by fdegrove View Post
    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
      My ComputerSystem Spec
  7.    28 Apr 2017 #97
    Join Date : Apr 2017
    Posts : 2
    Windows 10 Creator's Update

    Quote Originally Posted by MonarchX View Post
    - 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
      My ComputerSystem Spec
  8.    28 Apr 2017 #98
    Join Date : Aug 2016
    S/E England
    Posts : 4,526
    10 Home x64 (1709) (10 Pro on 2nd pc)

    Quote Originally Posted by DonCuthbert View Post
    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.
      My ComputersSystem Spec
  9.    28 Apr 2017 #99
    Join Date : Oct 2015
    Posts : 16
    10

    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
    and
    Bcdedit /set flightsigning on/off
    and
    WHQL 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.
      My ComputerSystem Spec
  10.    28 Apr 2017 #100
    Join Date : Oct 2015
    Posts : 2,048
    Windows 10 Pro X64

    Hi,

    Quote Originally Posted by ibach View Post
    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,
      My ComputersSystem Spec

 
Page 10 of 15 FirstFirst ... 89101112 ... LastLast


Similar Threads
Thread Forum
Windows 10 Creators Update and Creators Update SDK are Released
Source: Windows 10 Creators Update and Creators Update SDK are Released - Building Apps for WindowsBuilding Apps for Windows :arrow: Windows 10 Creators Update version 1703 (build 15063) now available from Windows 10 Update Assistant. ...
Windows 10 News
STORE cache corruption
Store apps work fine yet STORE apps troubleshooter reports that "Windows STORE cache may be damaged/corrupted." Despite the following measures the error is "not fixed." STORE has been reset (WSRESET). STORE apps have been reregistered....
Software and Apps
KB3194496 - Corrupts Component Store?
Hi. I've been trying to install update KB3194496, but without success. Before installing it, DISM /CheckHealth reports "No component store corruption detected.". When trying to install the update, DISM aborts giving the error code 0x80073712...
Windows Updates and Activation
bios post screen shows incoherent component info
i boot up the computer and the bios post screen shows normal except for 4 keyboards 2 mice 2 hubs. when i only have 1 keyboard and 1 mice connected. what is this all about? idk what hubs is. maybe the dvd rom drive?
Drivers and Hardware
Solved DISM failure cannot repair corruption, error 0x80070570
I am unable to repair some filesystem corruption after upgrading from Windows 7 to Windows 10. Both sfc and DISM fail to fix the issues. I've attached the CBS.log and dism.log files if anyone would be willing to help me figure this out, thanks! ...
Performance & Maintenance
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 12:07.
Find Us
Twitter Facebook Google+ Ten Forums iOS App Ten Forums Android App



Windows 10 Forums