Windows 10: Creators update component store shows corruption but unable to repair

Page 15 of 15 FirstFirst ... 5131415
  1.    4 Weeks Ago #141

    Sadly, It's Not Fixed Here


    I've been following this issue for some time, as I have one machine (of 20+) that has this issue. Like many here I've just been living with it, but now that it's supposedly fixed I'm revisiting it.

    I must have tried ten permutations, but every one of them generates the same 0x800f081f error. These are the last three (some non-significant CRs and bumpf removed for brevity):

    PS C:\WINDOWS\system32> dism /online /cleanup-image /restorehealthDeployment Image Servicing and Management toolVersion: 10.0.15063.0Image Version: 10.0.15063.0[===========================96.1%======================= ]Error: 0x800f081fThe source files could not be found.The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log
    PS C:\WINDOWS\system32> dism /online /cleanup-image /restorehealth /source:esd:"e:\sources\install.exe":1Deployment Image Servicing and Management toolVersion: 10.0.15063.0Image Version: 10.0.15063.0[===========================96.1%======================= ]Error: 0x800f081fThe source files could not be found. The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log
    PS C:\WINDOWS\system32> dism /online /cleanup-image /restorehealth /source:esd:"e:\sources\install.exe":1 /limitaccessDeployment Image Servicing and Management toolVersion: 10.0.15063.0Image Version: 10.0.15063.0[===========================87.0%================== ]Error: 0x800f081fThe source files could not be found.The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log


    One thing that is immediately weird is the following line in CBS.log (my italics):

    Info CBS Exec: Addsource called, Session: 30612363_730643781, Client: DISM Package Manager Provider, from GPO: No, Path: C:\WINDOWS\system32\esd:e:\sources\install.exe:1

    Note the path is entirely FUBAR. I cannot see that I've made a syntax error in the /source: parameter (see bolded text in final try above), and e:\sources\install.exe definitely exists, with the first image being the Win 10 Pro, which is what is on this machine. The entire .iso was downloaded hours ago using the Media Creation Tool, and I selected the option to auto-detect the right version (which is x64 English International, a.k.a. EN-GB.) Can anyone see why the path to windows would be prepended to the esd specification?

    PS: I've just tried without the quotation marks around the path, but get the same error in the log. In any case, there are lots of examples here of it working fine with the quotes.

    PPS: This machine is behind a strict firewall, but I've opened it entirely for the above test. There is also a WSUS server managing updates, and some update-related policies in the GPO, but nothing unusual.
      My ComputerSystem Spec

  2.    4 Weeks Ago #142

    Stupid Typo in Command, But No Improvement


    So for I moment I was kicking myself, as I noticed I was specifying install.exe rather that .esd. I had been suspicious (and still am) that it's just a stupid error that I keep overlooking, and was more than optimistic that the problem would be resolved.

    Depressingly, no. The same error, and message in the log, happen with install.esd as well.

    Code:
    dism /online /cleanup-image /restorehealth /source:esd:e:\sources\install.esd:1 /limitaccess
    Code:
    Info                  CBS    Exec: Addsource called, Session: 30612497_1691536918, Client: DISM Package Manager Provider, from GPO: No, Path: C:\WINDOWS\system32\esd:e:\sources\install.esd:1
    Warning               CBS    The alternate source path directory could not be accessed [HRESULT = 0x8007007b - ERROR_INVALID_NAME]
    Info                  CBS    Failed to add new file source [HRESULT = 0x8007007b - ERROR_INVALID_NAME]
    Info                  CBS    Failed to add alternate file source [HRESULT = 0x8007007b - ERROR_INVALID_NAME]
    Info                  CBS    Failed adding alternate source directory [HRESULT = 0x8007007b - ERROR_INVALID_NAME]
    Info                  CBS    Failed to Add Source using worker session [HRESULT = 0x8007007b]
    In fact, looking back, I see that all my earlier attempts were with the (correct) .esd specification; it's only the ones I did to reproduce the issue for the above post that were wrong. So the problem still stands.

    Note that the path is still getting mangled between my command and what is listed in the log file. I have no idea why this could be.
      My ComputerSystem Spec

  3.    4 Weeks Ago #143

    Update: I've tried all kinds of permutations for the /source parameter. Anything that includes any characters over and above a standard path show as rejected in the log. Thus
    Code:
    /source:esd:e:\sources\install.esd
    /source:esd:e:\sources\install.esd:1
    /source:e:\sources\install.esd:1
    all generate an INVALID_NAME error in the log.
    Code:
    /source:e:\sources\install.esd
    doesn't work either; it generates ERROR_DIRECTORY instead.

    The whole thing seems to be a dog's breakfast in this release.
      My ComputerSystem Spec


 
Page 15 of 15 FirstFirst ... 5131415

Related Threads
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. ...
STORE cache corruption in Software and Apps
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....
KB3194496 - Corrupts Component Store? in Windows Updates and Activation
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...
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?
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! ...

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 05:08.
Find Us