Creators update component store shows corruption but unable to repair

Page 11 of 15 FirstFirst ... 910111213 ... LastLast

  1. Posts : 16

    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:

    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]
    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageIndex\Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~]

    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.

    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:WIM:Path 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...
    Last edited by ibach; 28 Apr 2017 at 08:49.
      My Computer

  2. Posts : 10

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

    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!
      My Computer

  3. Posts : 14

    Hey everybody. So I wanted to report that, since Microsoft has decided to ignore the issues prevalent in the creators update of Windows 10, I did more digging into the issue. I then found a blog post which confirmed that the corrupt Windows package file is indeed the cause of DISM not working correctly, and it does come that way right out of the box. However, the blog post also offers a solution: Just delete the references to the corrupt package file from the Windows registry. There are a total of 4 registry keys: 2 are located in both
    "[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageIndex" and
    "[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages". You will want to delete the two registry keys which contain the name of the corrupt package file: "Microsoft-Windows-TestRoot-and-FlightSigning-Package". You will have to edit the key permissions in order to do this, as you do not have the permissions by default. Once you delete those keys, then navigate to "C:\Windows\servicing\packages" and either move or delete the 4 files which also contain (and begin with) "Microsoft-Windows-TestRoot-and-FlightSigning-Package". Then, run the scan again and it will continue to completion (at least as long as nothing else is wrong). blog post can be found here:
      My Computer

  4. Posts : 24,494
    10 Home x64 (21H2) (10 Pro on 2nd pc)

    whiggs2 said:
    ... I then found a blog post which confirmed that the corrupt Windows package file is indeed the cause of DISM not working correctly, and it does come that way right out of the box. However, the blog post also offers a solution:...
    You'll never guess where they found that solution. They credit a comment on a German blog for ...
    ...pointing to a forum post. Within this english forum thread someone was able to detect the faulty file within the log file after executing dism
    Click on their link and it takes you to.....

    ...this Thread!

      My Computers

  5. Posts : 128
    Windows 10


    That made me laugh. Thanks
      My Computer

  6. Posts : 16

    Thank you people! Laughing here too!
      My Computer

  7. Posts : 3

    There is a easier way to do this, what's recommended above to take out the corrupt package..........then again I know how to use this program so there is a little learning curve.

    I WOULD recommend that you only take out the corrupt package ONLY and then reinstall windows with the ISO that the program makes for you. THEN if u want to go back and mess with other things , then so be it. I say this because I have played with this program for countless hours and found that if you go taking out a ton of stuff in windows that you don't want........ONE of those "things/ features" you took out could break windows and you will be banging your head to figure out which just take out the one package and then install windows to fix this......I would NOT suggest anyone without some " above basic" computer experience / skills to attempt this..........but I know there are a lot of geeks lol that just have to have this fixed here is your solution. OR wait until MS fixes their continual garbage " so called Windows" mess.
      My Computer

  8. Posts : 16

    Countless years would be more like it to find out what is dependent on what. Microsoft has always failed to publicly document the dependencies... In ntlite Nuhi is tiring to connect the dots for quite a while now, and is doing good job about that, but the trouble is that Microsoft makes the changes in that only too often. I would love to see all cross package dependencies documented by Microsoft. Is there such a document somewhere?
      My Computer

  9. Posts : 24,494
    10 Home x64 (21H2) (10 Pro on 2nd pc)

    This issue remains unchanged after today's cumulative update to build 15063.296, I've just tested it
      My Computers

  10. Posts : 425

    Damn, other that this has anyone else getting other issues with Creators Update, just curious.
      My Computer


  Related Discussions
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 13:10.
Find Us

Windows 10 Forums