[SOLVED] Windows 10 (21H2) Windows Update KB5015807 Error 0x8007000d

R

Robby

Active member
Joined
Jul 28, 2022
Posts
40
Hi,
it's the first time I'm experiencing serious problems in installing a Win10 update: KB5015807 runs on my AMD Ryzen Threadripper 3970X for quite some time but finally exits at 100% with error 0x8007000d. DISM, SFC, SFCFix and a couple of other tries could not resolve the issue. I am really desperate now and kindly seek for some help in your forum. Please find enclosed the CBS zipfile. By the way, SFCFix (not using any script file) did not return any errors as well.
Many thanks for your help...
 

Attachments

There doesn't appear to be any errors in current CBS log, could you please provide the entire CBS folder?
 
Thanks for taking care! After endless attempts to get the update through, the CBS-folder was quite messy. So I cleaned it up before running SFC, DSIM, SFCfix. Seems that was not helpful.
What I did now: Cold boot - Windows update - SFC - DSIM - SFCfix
Please find enclosed the resulting CBS-folder.
 

Attachments

SFCFix Script
Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.
  1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
  5. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.
 

Attachments

Thanks, could you please attempt to update again and then provide the CBS logs if it fails?
 
Hmm, there is no persist-log in the CBS folder. Should I run SFC - DSIM - SFCfix again?
 
You could try running DISM and possibly SFC, and then uploading all the CBS logs which are produced.
 
Rich (BB code): 
2022-07-31 18:26:26, Info                  CBS    =================================
2022-07-31 18:26:26, Info                  CBS    Checking System Update Readiness.
2022-07-31 18:26:26, Info                  CBS    
2022-07-31 18:26:26, Info                  CBS    (p)    CSI Payload Corrupt    (n)            amd64_microsoft-windows-notepad_31bf3856ad364e35_10.0.19041.1741_none_e3a8c2b9255aea7e\r\notepad.exe
2022-07-31 18:26:26, Info                  CBS    Repair failed: Missing replacement payload.

Please use the same instructions as before with the provided SFCFix and then run DISM again. If DISM runs successfully with no errors, then please attempt to install the update, otherwise if failure occurs in either case, then please provide the CBS logs.
 

Attachments

SFCFix and DSIM ended with no errors. Unfortunately the update still fails with 0x8007000d. Please find enclosed the complete CBS-folder.
 

Attachments

Could you please provide your COMPONENTS hive using the following instructions:

Retrieve Components Hive
1. Navigate to C:\Windows\System32\Config and locate the COMPONENTS file.
2. Please copy this file to your desktop.
Note: If you receive an error that this file is in-use, simply reboot your computer and try again.
3. Right-click on this file on your desktop and select Send To...Compressed (zipped) folder. This will create a file named COMPONENTS.ZIP on your desktop.
4. The file will likely be too large to upload here so please upload to a file sharing service. Examples of services to upload to are Dropbox or OneDrive or WeTransfer and then just provide the link in your reply.
 
SFCFixScript.txt
Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.
  1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the attached file, SFCFixScript.txt, and save this to your Desktop. Ensure that this file is named SFCFixScript.txt - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFixScript.txt.
  5. Drag the file SFCFixScript.txt onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a log should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.[/list]

    Once successfully imported, then please attempt to install the update once again.
 

Attachments

Thanks for your persistent support, it seems we are making progress. SFCFix came through without errors (see enclosed) and install ended with a new error 0x80073712. If required, please find the link to latest CBS.zip here: Sysnative
 

Attachments

There's very likely going to be a number of missing subkeys from your COMPONENTS hive, could you please follow these instructions so we can identify them:

Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Try updating the system just like you have in the past.
3. Stop Process Monitor as soon as it fails. You can simply do this by clicking the square icon on the toolbar as shown below.
j8MhY5V.png

4. Select the File menu...Save... and save the file to your desktop. This is likely the default location. The name (unless changed) will be LogFile.PML. This is fine.
5. Zip up and provide the link to the LogFile.PML file as well as your CBS.log Examples of services to upload to are Dropbox or OneDrive or WeTransfer.
 
Could you please backup your current COMPONENTS hive and then replace it with the one attached? Once done, then please run the SFCFixScript from post #16 and then attempt to install the update again. If it fails, then please attach the latest CBS logs.
 

Attachments

You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top