Creators update component store shows corruption but unable to repair

Page 13 of 15 FirstFirst ... 31112131415 LastLast

  1. Posts : 24
    What do you think?
       #121

    Mkay, this time I managed to reach 88% with DISM, before it was somewhere at 26. Build is 15063.296.
      My Computer


  2. Posts : 2
    Windows 10 Pro
       #122

    Have you tried this fix?


    oh microsoft said:
    Mkay, this time I managed to reach 88% with DISM, before it was somewhere at 26. Build is 15063.296.
    Look at the instructions in bold. They worked for me.

    I was having the same issue with DISM (component store corrupt, repairable) and getting the"Error: 0x800f081f The source files could not be found, etc.In ScanHealth Details - CBS Corrupt MUM - Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.15063.0I mounted the install.wim and did a search for it, no results found.I did a search on my C: drive for it, no results found:I did a search in the Registry and found it at the following 2 locations:
    Go to these two locations, export each branch first then delete the key. You may need to take ownership of the key in order to completely delete it. Let me know if you are familiar with taking ownership of the key.
    1st Loction:[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageIndex\Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~0.0.0.0]2nd Location:[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.15063.0]Exported, then Deleted the 2 Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.15063.0 KEYS ONLYNote: They were already owned by Administrators, but I had to give Administrators Full Control to be able to delete them.No More DISM issues and I have NOT seen any side effects (ie ... event warnings,errors,etc)
      My Computer


  3. Posts : 139
    Windows 10
       #123

    As i said, the issue is fixed now. No need for any workarounds anymore.
      My Computer


  4. Posts : 31,480
    10 Home x64 (22H2) (10 Pro on 2nd pc)
       #124

    s0urce said:
    As i said, the issue is fixed now. No need for any workarounds anymore.
    Then how do you explain this from someone on the latest 15063.296?

    oh microsoft said:
    Mkay, this time I managed to reach 88% with DISM, before it was somewhere at 26. Build is 15063.296.
    Or why mine still fails despite being 15063.296?
      My Computers


  5. Posts : 139
    Windows 10
       #125

    You sure it is the same exact error?

    I also had this problem and since i saw that Microsoft employee post i went to check and it completed successfully. And i'm not alone. Use DISM to Repair Windows 10 Image - Page 48 - Windows 10 Performance Maintenance Tutorials
      My Computer


  6. Posts : 31,480
    10 Home x64 (22H2) (10 Pro on 2nd pc)
       #126

    s0urce said:
    You sure it is the same exact error?
    Yes. From the CBS.log that using DISM just generated....
    Code:
    2017-05-19 22:15:06, Info                  CBS    
    =================================
    Checking System Update Readiness.
    (p) CBS MUM Corrupt   Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.15063.0
    Summary:
    Operation: Detect and Repair 
    Operation result: 0x800f0906
    Last Successful Step: Entire operation completes.
    Total Detected Corruption: 1
     CBS Manifest Corruption: 1
      My Computers


  7. Posts : 139
    Windows 10
       #127

    AFAIK the original error was 0x800f081f
      My Computer


  8. Posts : 1,471
    Win10 Home x64 - 1809
       #128

    For what it's worth, thought I'd check my Insider Build
    Win 10 Pro x64 1703 (16199.1000)

    Deployment Image Servicing and Management tool
    Version: 10.0.16199.1000

    Image Version: 10.0.16199.1000

    [===========================98.5%========================= ]
    Error: 0x800f081f

    The source files could not be found.
    Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see http://go.microsoft.com/fwlink/?LinkId=243077.

    Checking System Update Readiness.

    (p) CBS MUM Corrupt Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.16199.1000
    (p) CBS MUM Corrupt Microsoft-Windows-TestRoot-and-FlightSigning-WOW64-Package~31bf3856ad364e35~amd64~~10.0.16199.1000

    If they did fix it, they broke it again in this version ... lol
      My Computers


  9. Posts : 139
    Windows 10
       #129

    Can't speak for Insider Builds.

    Anyway @Bree, i just tested something here on my end and i could repro your error by blocking internet access to the /restorehealth. So, make sure nothing is blocking the system from reaching the network.

    Blocked network:
    Code:
    Checking System Update Readiness.  
    (p)    CBS MUM Corrupt            Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.15063.0
    
    Summary:
    Operation: Detect and Repair 
    Operation result: 0x800f0906
    Last Successful Step: Entire operation completes.

    Normal network
    Code:
    Checking System Update Readiness.
    (p)    CBS MUM Corrupt    (Fixed)    Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.15063.0
    Summary:
    Operation: Detect and Repair 
    Operation result: 0x0
    Last Successful Step: Entire operation completes.


    Otherwise, try a sfc /scannow.
      My Computer


  10. Posts : 31,480
    10 Home x64 (22H2) (10 Pro on 2nd pc)
       #130

    s0urce said:
    Anyway @Bree, i just tested something here on my end and i could repro your error by blocking internet access to the /restorehealth. So, make sure nothing is blocking the system from reaching the network.
    Interesting... I've just tried it again without changing anything and this time it worked.

    Code:
    Deployment Image Servicing and Management tool
    Version: 10.0.15063.0
    Image Version: 10.0.15063.0
    [==========================100.0%==========================] The restore operation completed successfully.
    The operation completed successfully.
    CBS.log shows...
    Code:
    2017-05-20 10:08:53, Info                  CBS    DWLD: Windows update server URL: http://download.windowsupdate.com/d/msdownload/update/software/tool/2013/08/dummyrepairpackage_cd97f5d6cb54bf63a4e4adc376edadf6f2b8352c.cab
    2017-05-20 10:08:53, Info                  CBS    DWLD:Content is Full-Cab package.
    2017-05-20 10:08:53, Info                  CBS    DWLD: Windows update server URL: http://download.windowsupdate.com/c/msdownload/update/software/tool/2017/05/kb3089227-amd64-neutral-neu-10_2bbf7b24607be526c98e5c7ee3a4fe70e3f42df6.cab
    2017-05-20 10:08:53, Info                  CBS    DWLD:Content is Express package.
    2017-05-20 10:08:53, Info                  CBS    DWLD: Windows update server URL: http://download.windowsupdate.com/c/msdownload/update/software/tool/2017/05/kb3089227-amd64-neutral-neu-10_4a5ac2e79762e347df4df15d435db8eef8abb084.psf
    2017-05-20 10:08:53, Info                  CBS    DWLD:Content is Express package.
    Perhaps the fix was to put something on the update servers and it took its time to replicate across them all?

    I wonder what the ...2013/08/dummyrepairpackage... is?

    Also, there's no kb3089227 that I can find - curious.


    Edit: I've just manually downloaded the .cab file for that kb3089227. It does contain, amongst (many) other things...
    microsoft-windows-testroot-and-flightsigning-package~31bf3856ad364e35~amd64~~10.0.15063.0
      My Computers


 

  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 16:50.
Find Us




Windows 10 Forums