Page 1 of 15 12311 ... LastLast
  1.    09 Apr 2017 #1
    Join Date : Dec 2015
    Posts : 28
    Windows 10 Pro x64

    Creators update component store shows corruption but unable to repair


    Since Creators update, whenever I run

    Dism /Online /Cleanup-Image /CheckHealth
    DISM /Online /Cleanup-Image /ScanHealth

    It results in
    "The component store is repairable.
    The operation completed successfully."

    Sfc /scannow shows no errors.


    Now when I use

    "DISM /Online /Cleanup-Image /RestoreHealth" or

    " DISM /Online /Cleanup-Image /RestoreHealth /Source:E:\sources\install.wim" (did with ESD too)

    It results in

    "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 Configure a Windows Repair Source.
    The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log"


    Both clean install and inplace upgrade don't solve the problem

    Also, event viewer shows always these administrative errors with ids 7000 and 37 and I don't know if it is related with this dism issue.
    Last edited by Dyabzhee; 17 May 2017 at 13:39.
      My ComputerSystem Spec
  2.    10 Apr 2017 #2
    Join Date : Jan 2015
    UK, Midlands
    Posts : 11,074
    Win 10 Pro (1703)

    Hi, given the in-place upgrade install failure, try doing basic checks on your disk first. Do you mean the in-place upgrade install completed, but then your OS failed having booted up, or that the in-place upgrade installation failed to complete?

    1. Download and run Crystal Diskinfo (free). It reports Good/Caution/Bad based on SMART params.
    Do not proceed unless Good.

    2. From an admin command prompt
    [Windows key + X, click command prompt (admin)]
    chkdsk C: /F
    Your PC will need to restart.
    Post back the result, which you can get after a restart as follows:
    How do I see the results of a CHKDSK that ran on boot? - Ask Leo!
      My ComputerSystem Spec
  3.    10 Apr 2017 #3
    Join Date : Dec 2015
    Posts : 28
    Windows 10 Pro x64
    Thread Starter

    Quote Originally Posted by dalchina View Post
    Hi, given the in-place upgrade install failure, try doing basic checks on your disk first. Do you mean the in-place upgrade install completed, but then your OS failed having booted up, or that the in-place upgrade installation failed to complete?

    1. Download and run Crystal Diskinfo (free). It reports Good/Caution/Bad based on SMART params.
    Do not proceed unless Good.

    2. From an admin command prompt
    [Windows key + X, click command prompt (admin)]
    chkdsk C: /F
    Your PC will need to restart.
    Post back the result, which you can get after a restart as follows:
    How do I see the results of a CHKDSK that ran on boot? - Ask Leo!

    My os booted fine every time and it seemed ok , it's just these scan and check health always show corruptions.

    I've done chkdsk also but forgot to mention and I am on SSD. It finished in few seconds without any errors found.

    Here are the results of the DISM /Online /Cleanup-Image /RestoreHealth
    Creators update component store shows corruption but unable to repair Attached Files
      My ComputerSystem Spec
  4.    10 Apr 2017 #4
    Join Date : Nov 2015
    Posts : 9
    Windows 10 Professional

    Hello All Members

    Windows 10 Professional x64 (Slovak Language) Version - 1703 / Build 15063.14

    When I use the command in command prompt - sfc /scannow

    Click image for larger version. 

Name:	System Scan.png 
Views:	391 
Size:	8.5 KB 
ID:	129270

    I open Power Shell and write these commands:

    Repair-WindowsImage -Online -CheckHealth

    Repair-WindowsImage -Online -ScanHealth

    Repair-WindowsImage -Online -RestoreHealth
    Some Pictures:

    Click image for larger version. 

Name:	DISM Health Check PS.png 
Views:	390 
Size:	8.7 KB 
ID:	129271

    Click image for larger version. 

Name:	DISM Health Repair PS.png 
Views:	10 
Size:	20.6 KB 
ID:	129272

    Propably i have same problem as Dyabzhee. And we are not alone with this issue. Yesterday i used google to found something informations about this issue and found this topic on the Sysnative.com - https://www.sysnative.com/forums/windows-update/22510-creators-update-dism-repairable-but-cannot-find-source-files-sfcfix-zero-errors.html
      My ComputerSystem Spec
  5.    10 Apr 2017 #5
    Join Date : Nov 2015
    Posts : 9
    Windows 10 Professional

    Here is small information from CBS.log - when i use command prompt and this commands:

    Dism.exe /Online /Cleanup-Image /AnalyzeComponentStore

    Dism.exe /online /Cleanup-Image /StartComponentCleanup

    DISM.exe /Online /Cleanup-image /Scanhealth
    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: 0x800f081f
    Last Successful Step: Entire operation completes.
    Total Detected Corruption: 1
    CBS Manifest Corruption: 1
    CBS Metadata Corruption: 0
    CSI Manifest Corruption: 0
    CSI Metadata Corruption: 0
    CSI Payload Corruption: 0
    Total Repaired Corruption: 0
    CBS Manifest Repaired: 0
    CSI Manifest Repaired: 0
    CSI Payload Repaired: 0
    CSI Store Metadata refreshed: True

    Total Operation Time: 89 seconds.

    2017-04-08 22:58:40, Info CBS CheckSur: hrStatus: 0x800f081f [CBS_E_SOURCE_MISSING], download Result: 0x800f0948 [CBS_E_SOURCE_MISSING_FROM_WU_CAB]
    2017-04-08 22:58:40, Info CBS Count of times corruption detected: 1
    2017-04-08 22:58:40, Info CBS Seconds between initial corruption detections: -1
    2017-04-08 22:58:40, Info CBS Seconds between corruption and repair: -1
    2017-04-08 22:58:40, Info CBS Failed to run Detect and repair. [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]
    2017-04-08 22:58:40, Info CBS Reboot mark cleared
    2017-04-08 22:58:40, Info CBS Winlogon: Simplifying Winlogon CreateSession notifications
    2017-04-08 22:58:40, Info CBS Winlogon: Deregistering for CreateSession notifications
    2017-04-08 22:58:40, Info CBS Exec: Processing complete, session(Corruption Repairing): 30585002_2974887044 [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]
    2017-04-08 22:58:40, Error CBS Session: 30585002_2974887044 failed to perform store corruption detect and repair operation. [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]
    2017-04-08 22:58:40, Info CBS Session: 30585002_2974887044 finalized. Download error: 0x800f0948 [CBS_E_SOURCE_MISSING_FROM_WU_CAB], Reboot required: no [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]
    2017-04-08 22:58:40, Info CBS Failed to FinalizeEx using worker session [HRESULT = 0x800f081f]
    2017-04-08 22:58:40, Info CBS Releasing offline store key
    2017-04-08 23:00:41, Info CBS Trusted Installer is shutting down because: SHUTDOWN_REASON_AUTOSTOP
    2017-04-08 23:00:41, Info CBS TiWorker signaled for shutdown, going to exit.
    2017-04-08 23:00:41, Info CBS CbsCoreFinalize: ExecutionEngineFinalize
    2017-04-08 23:00:41, Info CBS Ending the TiWorker main loop.
    2017-04-08 23:00:41, Info CBS Starting TiWorker finalization.
      My ComputerSystem Spec
  6.    10 Apr 2017 #6
    Join Date : Aug 2016
    S/E England
    Posts : 4,526
    10 Home x64 (1709) (10 Pro on 2nd pc)

    Quote Originally Posted by Derelict View Post
    Propably i have same problem as Dyabzhee. And we are not alone with this issue.
    I can confirm that. Both the systems I have upgraded, one an x86 Pro 15063.13 the other x64 Home 15063.13, report "The component store is repairable" when using:
    DISM /Online /Cleanup-Image /ScanHealth

    The commands...
    Dism /Online /Cleanup-Image /RestoreHealth
    Dism /Online /Cleanup-Image /RestoreHealth /Source:esd:<full path to install.esd>:1
    DISM /Online /Cleanup-Image /RestoreHealth /Source:esd:<full path to install.esd>:1 /limitaccess
    (where install.esd is the one from the install USB made by the MCT and used to perform the upgrade)

    ..fail with:
    Code:
    C:\WINDOWS\system32> DISM /Online /Cleanup-Image /RestoreHealth /source:esd:d:\x64\sources\install.esd:1 /limitaccess
    
    Deployment Image Servicing and Management tool
    Version: 10.0.15063.0
    
    Image Version: 10.0.15063.0
    
    [===========================90.1%====================      ]
    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.
    The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log
    C:\WINDOWS\system32>

    Other than that, there are no apparent issues. Both systems appear fully functional.
    Last edited by Bree; 10 Apr 2017 at 07:53.
      My ComputersSystem Spec
  7.    10 Apr 2017 #7
    Join Date : Aug 2016
    S/E England
    Posts : 4,526
    10 Home x64 (1709) (10 Pro on 2nd pc)

    Apparently....

    Hi ,

    Your discovery is valuable. We sincerely appreciate your taking time to provide your feedback and thank you for the collected data. We have submitted it to system product team via our internal feedback tool, you could also use the built-in feedback hub to submit on your side....

    ...

    This is a problem created by Microsoft Windows 10 newly updates in both RTM and Insider Previews.
    We shouldn't have to try to fix it.
    In fact I doubt anyone outside MS Development Team can fix it.
    This problem started at least 4 builds back....
    https://social.technet.microsoft.com...in10itprosetup
      My ComputersSystem Spec
  8.    10 Apr 2017 #8

    Even more interesting: /checkhealth gives my recent upgrades a clean bill of health while /scanhealth gives the error that Bree reports:
    Click image for larger version. 

Name:	good-bad-dism.jpg 
Views:	378 
Size:	52.5 KB 
ID:	129319
    Bottom line: I concur that this is a problem with the 15063.13 image that's now standard for recent upgrades/clean installs. Hopefully, MS will fix it sooner rather than later. I'm upvoting Bree's feedback hub post, if I can find it (if you post the title to your feedback hub input, that will help, Bree: TIA).
    --Ed--
      My ComputersSystem Spec
  9.    10 Apr 2017 #9
    Join Date : Aug 2016
    S/E England
    Posts : 4,526
    10 Home x64 (1709) (10 Pro on 2nd pc)

    Quote Originally Posted by EdTittel View Post
    I'm upvoting Bree's feedback hub post, if I can find it ....
    You won't, I don't have an MS account so can't post one
    Robert Richter, the OP of the thread I linked to may have posted one...
      My ComputersSystem Spec
  10.    10 Apr 2017 #10
    Join Date : Jul 2015
    Posts : 51
    10Pro x64 [1703]

    hi all, same for me
      My ComputerSystem Spec

 
Page 1 of 15 12311 ... 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:06.
Find Us
Twitter Facebook Google+ Ten Forums iOS App Ten Forums Android App



Windows 10 Forums