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

Thanks, components replacement and SFCFix were successful. Unfortunately install now ends with error 0x800f081f.
Please find the latest CBS.zip here: Sysnative
 
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]

    Afterwards, please attempt to install the update again.
 

Attachments

Please follow the same instructions as before. There should hopefully be very few errors now.
 

Attachments

Please use the same instructions as before, if it fails again, then please provide the CBS logs along with the latest version of your COMPONENTS hive and I'll see if I can find all the missing v! marks at once.
 

Attachments

Thanks for the script. Unfortunately still error 0x800f081f after install.
Please find latest CBS.zip and components.zip here: Sysnative
 
Thanks for your support! Microsoft obviously provided new updates today. KB890830, KB5012170 and KB5016616 were due for installation. Fortunately the first two installed without issues. But the last one resulted again in error 0x800f081f with a very similar error-footprint in CBS.log as before. Seems to be a hard nut to crack...
Please find the lastest CBS.zip and components.zip here: Sysnative
 
There just seems to be lots of missing subkeys from your COMPONENTS hive. Could you please try the attached version?
 

Attachments

Thanks, but still no success. This time install ends with error 0x80073712.
Please find latest CBS.zip and components.zip here: Sysnative
 
It looks like the missing components error has returned from earlier in this thread, most likely because we added the missing ComponentFamilies back; could you please provide a Process Monitor trace as you did before?

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. Examples of services to upload to are Dropbox or OneDrive or WeTransfer.
 
Please find another amended version attached. It's probably best to run Process Monitor again on your next install attempt as well.
 

Attachments

Strange! I've replaced the components file with your latest version and did a reboot. Procmon said no events are detected and install ended with the known error. Logfile was more or less empty. Exiting and starting Procmon again ended with a "driver not found" error. A reboot resulted in a blueish screen for 1,5h (!) saying windows is being prepared and not to switch off the computer. Afterwards the computer started normally and another install ended with the known error. I suspect some issue with your latest components file and an automatic system-recovery to an earlier checkpoint.
Please find logfiles (1st and 2nd), CBS and components here: Sysnative
 
The Process Monitor issue is odd, that shouldn't happen unless it wasn't able to start correctly. The COMPONENTS hive is usually only loaded during an update and it shouldn't cause any boot issues since it isn't a boot-critical hive. You can boot without a COMPONENTS hive altogether.

There did seem to be less missing keys this time so hopefully we're coming to a conclusion here.
 

Attachments

Many thanks for your explanation and the new components file! This time, no odd things happened but install still exits with error 0x80073712. To my understanding only one error is left now.
Please find latest logfile, CBS and components file here: Sysnative
 
It seems to be consistently failing on the same error each time and we seem to have added all the components from my VM which has the update you're trying to install, successfully installed too.

Rich (BB code): 
2022-08-12 21:37:56, Error                 CSI    000000a9 (F) HRESULT_FROM_WIN32(14098) #4346140# from Windows::ServicingAPI::CCSITransaction::ICSITransaction_EnumMissingComponents(Flags = 0, ppe = NULL, disp = 0)[gle=0x80073712]
2022-08-12 21:37:56, Error                 CSI    000000aa (F) HRESULT_FROM_WIN32(14098) #4346139# from Windows::ServicingAPI::CCSITransaction_ICSITransaction::EnumMissingComponents(flags = 0, enum = NULL, disp= 0)
[gle=0x80073712]
2022-08-12 21:37:56, Info                  CBS    Failed to get enumerator for missing components. [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2022-08-12 21:37:56, Error                 CBS    Failed to complete component closure [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]

Export SideBySide
  1. Click on the Start button and in the search box, type regedit
  2. When you see regedit on the list, right-click on it and select Run as administrator
  3. When regedit opens, using the left pane, navigate to the following registry key and select it by clicking on it once.

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide
  4. Once selected, click File > Export....
  5. Change the Save as type: to Registry Hive Files (.)
  6. Name this file SxS (with no file extension) and save it to your Desktop.

Once done please upload this file via Dropbox or OneDrive or SendSpace.
 
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]

    Please ignore the previous post regarding the WinSxS hive for now.
 

Attachments

Thanks for your update. SFCFixScript worked without issues, however install ended with the same error again.
Please find enlosed SxS (which I took before SFCFixScript) and latest logfile, CBS and components file here: Sysnative
 
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