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

Okay, looks like we've made some progress with installing the update, since there's no longer any missing v! marks and we've got another bunch of Component subkeys which it wasn't able to find or are corrupt, along with some more missing Deployment keys which weren't there in the last log.
 

Attachments

Thanks again for your update. Unfortunately still no success, but don't let us give up...
Please find latest logfile, CBS and components file here: Sysnative
 
I thought it might have been easier to provide this as a fix script rather than provide another COMPONENTS hive.

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]
 

Attachments

Thanks, unfortunately same result after install.
This time SFCFixScript failed in the first run (see SFCFix.txt in the dropbox) but was successful in a second try. Please find all relevant files again here: Sysnative
What I am thinking now: End of 01/2022 I have created a System-Image using this "strange" Win7 Backup feature within Win10. This System-Image can still be found within the regular Win10 System-Recovery and is accessible. Since the update-trouble came up around May/June timeframe, maybe the January backup is still healty. Sure, I will have to do quite a bunch of updates/installs but might cost us less efforts than replacing key by key. How do you think? Anything I should watch out?
 
These were the last missing Components mentioned:

Rich (BB code): 
amd64_microsoft-onecore-m..ia-mfpmp-deployment_31bf3856ad364e35_10.0.19041.1806_none_160b741e3113dcdb
amd64_microsoft-windows-a..ev-wow64-deployment_31bf3856ad364e35_10.0.19041.1826_none_f2afca89172a8c30
amd64_microsoft-windows-c..d-wow64-deployment0_31bf3856ad364e35_10.0.19041.1826_de-de_85cf52356dda6aa0
amd64_microsoft-windows-c..d-wow64-deployment0_31bf3856ad364e35_10.0.19041.1826_en-us_2ec0282e5cb87665
amd64_microsoft-windows-c..d-wow64-deployment0_31bf3856ad364e35_10.0.19041.1826_zh-cn_8e46929c43da5077
amd64_microsoft-windows-c..equired-deployment0_31bf3856ad364e35_10.0.19041.1806_de-de_b7e3869925eb79fc
amd64_microsoft-windows-c..equired-deployment0_31bf3856ad364e35_10.0.19041.1806_en-us_60d45c9214c985c1
amd64_microsoft-windows-c..equired-deployment0_31bf3856ad364e35_10.0.19041.1806_zh-cn_c05ac6fffbeb5fd3
amd64_microsoft-windows-c..red-deployment01100_31bf3856ad364e35_10.0.19041.1826_de-de_81ca11a0bcd50440
amd64_microsoft-windows-c..red-deployment01100_31bf3856ad364e35_10.0.19041.1826_en-us_2abae799abb31005
amd64_microsoft-windows-c..red-deployment01100_31bf3856ad364e35_10.0.19041.1826_zh-cn_8a41520792d4ea17
amd64_microsoft-windows-c..uired-deployment010_31bf3856ad364e35_10.0.19041.1806_de-de_137cbe4bfd062d55
amd64_microsoft-windows-c..uired-deployment010_31bf3856ad364e35_10.0.19041.1806_en-us_bc6d9444ebe4391a
amd64_microsoft-windows-c..uired-deployment010_31bf3856ad364e35_10.0.19041.1806_zh-cn_1bf3feb2d306132c
amd64_microsoft-windows-e..oyment-languagepack_31bf3856ad364e35_10.0.19041.1826_de-de_504cb1cda0970fbf
amd64_microsoft-windows-e..oyment-languagepack_31bf3856ad364e35_10.0.19041.1826_en-us_f93d87c68f751b84
amd64_microsoft-windows-e..oyment-languagepack_31bf3856ad364e35_10.0.19041.1826_zh-cn_58c3f2347696f596
amd64_microsoft-windows-h..p-analog-deployment_31bf3856ad364e35_10.0.19041.1826_none_d5840f58cce84325
amd64_microsoft-windows-m..hell-opt-deployment_31bf3856ad364e35_10.0.19041.1806_none_461ee09256d34e49
amd64_microsoft-windows-m..pt-wow64-deployment_31bf3856ad364e35_10.0.19041.1826_none_347c7bf502ba3e91
amd64_microsoft-windows-m..s-merged-deployment_31bf3856ad364e35_10.0.19041.1741_none_34faccc9fae27090
amd64_microsoft-windows-mediaplayer-deployment_31bf3856ad364e35_10.0.19041.1826_none_e657c460f92900f6
amd64_microsoft-windows-notepad-fod-deployment_31bf3856ad364e35_10.0.19041.1741_none_9acf8e7444dc3838
amd64_microsoft-windows-p..oyment-languagepack_31bf3856ad364e35_10.0.19041.1826_de-de_e767e953aa6ae8e2
amd64_microsoft-windows-p..oyment-languagepack_31bf3856ad364e35_10.0.19041.1826_zh-cn_efdf29ba806aceb9
amd64_microsoft-windows-r..-desktop-deployment_31bf3856ad364e35_10.0.19041.1806_none_1cfacd587a262e9e
amd64_microsoft-windows-r..op-wow64-deployment_31bf3856ad364e35_10.0.19041.1806_none_b1eb5817b5df17b8
amd64_microsoft-windows-s..encehost-deployment_31bf3856ad364e35_10.0.19041.1741_none_c3db37b1a5f684e9
amd64_multimedia-mfcore-w..headless-deployment_31bf3856ad364e35_10.0.19041.1806_none_ff57f22002eb529a
amd64_multimedia-mfcore-w..headless-deployment_31bf3856ad364e35_10.0.19041.1826_none_32fc227c150ef746
amd64_multimedia-mfcore-w..ss-wow64-deployment_31bf3856ad364e35_10.0.19041.1806_none_277b2908cb43cbb4
amd64_multimedia-mfcore-w..ss-wow64-deployment_31bf3856ad364e35_10.0.19041.1826_none_f78b85115c151506
amd64_multimedia-restrict..by-wow64-deployment_31bf3856ad364e35_10.0.19041.1826_none_2b65714f20e6f648
amd64_multimedia-restrict..ecsdolby-deployment_31bf3856ad364e35_10.0.19041.1826_none_1d00b2debe4468d8
amd64_multimedia-restrict..headless-deployment_31bf3856ad364e35_10.0.19041.1826_none_6d8037ff72cb0069
amd64_multimedia-restrict..ss-wow64-deployment_31bf3856ad364e35_10.0.19041.1806_none_98d7f7b9bc0d0385

I've added them now to the attached COMPONENTS hive. Let's see what happens.

Robby said:
I have created a System-Image using this "strange" Win7 Backup feature within Win10. This System-Image can still be found within the regular Win10 System-Recovery and is accessible. Since the update-trouble came up around May/June timeframe, maybe the January backup is still healty. Sure, I will have to do quite a bunch of updates/installs but might cost us less efforts than replacing key by key. How do you think? Anything I should watch out?
Click to expand...
What do you mean by "strange" though? Is it the Windows Backup feature?
 

Attachments

Thanks for your update, unfortunately same result after install. Please find the latest logfiles here: Sysnative
I said "strange" because a Win7 backup-feature within Win10 gives me an impression of "old" and "outdated". Maybe they simply should have named it differently.
 
You can try and restore to an earlier system image if you would like, I would make a suitable backup of your current image beforehand though. I've attached the latest fix script if you would like to use that as well.

Latest Missing Subkeys:

Rich (BB code): 
HKLM\COMPONENTS\DerivedData\VersionedIndex\10.0.19041.1852 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-windows-e..oyment-languagepack_31bf3856ad364e35_de-de_b9c2e2b20a6a3a74\v!10.0.19041.1826
HKLM\COMPONENTS\DerivedData\VersionedIndex\10.0.19041.1852 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-windows-e..oyment-languagepack_31bf3856ad364e35_en-us_e69f7b9e28c35597\v!10.0.19041.1826
HKLM\COMPONENTS\DerivedData\VersionedIndex\10.0.19041.1852 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-windows-e..oyment-languagepack_31bf3856ad364e35_zh-cn_a092df589d4dcb95\v!10.0.19041.1826
HKLM\COMPONENTS\DerivedData\VersionedIndex\10.0.19041.1852 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-windows-m..pt-wow64-deployment_31bf3856ad364e35_none_aaa0432d386651b2\v!10.0.19041.1826
HKLM\COMPONENTS\DerivedData\VersionedIndex\10.0.19041.1852 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-windows-p..oyment-languagepack_31bf3856ad364e35_de-de_3d45b13d25c477a9\v!10.0.19041.1826
HKLM\COMPONENTS\DerivedData\VersionedIndex\10.0.19041.1852 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-windows-p..oyment-languagepack_31bf3856ad364e35_zh-cn_2415ade3b8a808ca\v!10.0.19041.1826
HKLM\COMPONENTS\DerivedData\VersionedIndex\10.0.19041.1852 (WinBuild.160101.0800)\ComponentFamilies\amd64_multimedia-mfcore-w..headless-deployment_31bf3856ad364e35_none_5b312798386110f3\v!10.0.19041.1806
HKLM\COMPONENTS\DerivedData\VersionedIndex\10.0.19041.1852 (WinBuild.160101.0800)\ComponentFamilies\amd64_multimedia-mfcore-w..ss-wow64-deployment_31bf3856ad364e35_none_f2f87d517773ae29\v!10.0.19041.1806
HKLM\COMPONENTS\DerivedData\VersionedIndex\10.0.19041.1852 (WinBuild.160101.0800)\ComponentFamilies\amd64_multimedia-restrict..headless-deployment_31bf3856ad364e35_none_e3e4f6edd69d589a\v!10.0.19041.1826
 

Attachments

Thanks again for your continued support. Unfortunately same result again.
I simply fear to ask too much from you, so let me try the restore as next. Please keep the thread open, I will come back to you in any case. It just may take a little while....
 
Okay no problem, let me know how it goes. If there is no problems with the restore, then you should theoretically be able to simply install the latest cumulative update with no problems?
 
Nope! System image recovery worked without issues and update did lot of installs. Finally error 0x8007000d showed up, that is where we started off. For curiosity I tried Win11. Here update goes without issues to the very end but the whole security center is not working: Defender is off and no buttons do work at all. The suggested security center repair made things even worse.
Anyway, it was worth a try and now I'm back again. I restored the system to Aug 12 evening, put in components file from post #45 and run SFCFixScript from post #47. Here are the logs from the install afterwards: Sysnative
 
There seems to be slight more corruption this time. Please find the amended COMPONENTS hive attached. You might want to start deleting some of the old logs from your online share too, just makes it a little easier to find the latest ones.

Rich (BB code): 
HKLM\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-c..oyment-languagepack_31bf3856ad364e35_10.0.19041.1826_pl-pl_6b6820a95e3d59be
HKLM\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-c..d-deployment0510210_31bf3856ad364e35_10.0.19041.1865_none_bc43ada66b97be27
HKLM\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-c..w64-deployment00110_31bf3856ad364e35_10.0.19041.1865_none_23041b095233b1b0
HKLM\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-c..w64-deployment00120_31bf3856ad364e35_10.0.19041.1865_none_b635f4d8281016ee
HKLM\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-c..w64-deployment00140_31bf3856ad364e35_10.0.19041.1865_none_22e3ab45524c0583
HKLM\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-c..red-deployment01100_31bf3856ad364e35_10.0.19041.1865_pl-pl_2a074b6a19d9c57b
HKLM\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-c..red-deployment01100_31bf3856ad364e35_10.0.19041.1865_en-us_2abeff89abaf5bc0
HKLM\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-c..red-deployment01100_31bf3856ad364e35_10.0.19041.1865_de-de_81ce2990bcd14ffb
HKLM\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-c..red-deployment01100_31bf3856ad364e35_10.0.19041.1865_zh-cn_8a4569f792d135d2
HKLM\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-c..red-deployment01110_31bf3856ad364e35_10.0.19041.1741_pl-pl_2a11762c19d229af
HKLM\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-c..red-deployment01120_31bf3856ad364e35_10.0.19041.1806_pl-pl_2a03337a19dd79c0
HKLM\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-c..red-deployment01130_31bf3856ad364e35_10.0.19041.1806_pl-pl_2a0433c419dc9317
HKLM\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-c..res-deployment03160_31bf3856ad364e35_10.0.19041.1865_none_6969a8faca6fdb99
HKLM\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-c..red-deployment05110_31bf3856ad364e35_10.0.19041.1865_none_97ede8ff09f7819f
HKLM\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-c..red-deployment05160_31bf3856ad364e35_10.0.19041.1865_none_97ed771709f801c4
HKLM\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-c..wow64-deployment000_31bf3856ad364e35_10.0.19041.1865_none_d14d8f2f9404222f
HKLM\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-c..uired-deployment010_31bf3856ad364e35_10.0.19041.1865_pl-pl_bbbbf8a95a09213e
HKLM\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-c..tures-deployment030_31bf3856ad364e35_10.0.19041.1865_none_9d88ea5dde2df77e
HKLM\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-c..ed-deployment051100_31bf3856ad364e35_10.0.19041.1865_none_fb5c626e7f62add1
HKLM\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-c..ed-deployment051140_31bf3856ad364e35_10.0.19041.1865_none_fd227f267e3ebfed

Rich (BB code): 
amd64_microsoft-windows-c..red-deployment01100_31bf3856ad364e35_en-us_f363c6967af556de\v!10.0.19041.1865
amd64_microsoft-windows-c..red-deployment01100_31bf3856ad364e35_de-de_c6872daa5c9c3bbb\v!10.0.19041.1865
amd64_microsoft-windows-c..red-deployment01100_31bf3856ad364e35_zh-cn_ad572a50ef7fccdc\v!10.0.19041.1865
 

Attachments

Thanks for components update. Still same error after install. Please find the latest logfiles here: Sysnative
Sure, I have deleted all files from the fileshare except the last one. Hope that's o.k.
 
Thanks, oddly enough, there doesn't appear to be any missing subkeys related to the usual suspects as before. I'm going to check the COMPONENTS hive using one of my own tools for a few things, in the meantime, it may be worth trying the usual DISM command and then checking if it throws any errors.

Rich (BB code): 
DISM /Online /Cleanup-Image /RestoreHealth
 
DSIM took quite long time and ended with error 0x800f081f. Please find output and DSIM-log enclosed.
The missing folders like "0F419473-A32D-41B3-B9EE-61E4070C1031" do simply not exist at that location nor anywhere else on drive C:.

Not sure whether inportant: After the recovery from post #50 I've also executed Microsoft Update & security > Troubleshoot > Additional troubleshooters > Install. It reported to have done some modifications but ended in the known situation.
 

Attachments

Could you please provide the CBS log as well?

Robby said:
Not sure whether inportant: After the recovery from post #50 I've also executed Microsoft Update & security > Troubleshoot > Additional troubleshooters > Install. It reported to have done some modifications but ended in the known situation.
Click to expand...
Hmm, it probably didn't do much to be honest, those troubleshooters aren't only typically good at resolving very simple problems.
 
Thank you, there's seems to be lots of missing files! I sort of expected this to be honest, since we've replaced lots of the missing keys from the COMPONENTS hive, the servicing stack has probably now been able to find the payload files it was looking for, however, has noticed that they've been corrupted. I'll probably break this fix down into multiple parts for you otherwise SFCFix can take hours to run.

Rich (BB code): 
2022-08-17 12:03:51, Info                  CBS    Summary:
2022-08-17 12:03:51, Info                  CBS    Operation: Detect and Repair 
2022-08-17 12:03:51, Info                  CBS    Operation result: 0x800f081f
2022-08-17 12:03:51, Info                  CBS    Last Successful Step: Remove staged packages completes.
2022-08-17 12:03:51, Info                  CBS    Total Detected Corruption:    696
2022-08-17 12:03:51, Info                  CBS        CBS Manifest Corruption:    0
2022-08-17 12:03:51, Info                  CBS        CBS Metadata Corruption:    0
2022-08-17 12:03:51, Info                  CBS        CSI Manifest Corruption:    537
2022-08-17 12:03:51, Info                  CBS        CSI Metadata Corruption:    0
2022-08-17 12:03:51, Info                  CBS        CSI Payload Corruption:    159
2022-08-17 12:03:51, Info                  CBS    Total Repaired Corruption:    0
2022-08-17 12:03:51, Info                  CBS        CBS Manifest Repaired:    0
2022-08-17 12:03:51, Info                  CBS        CSI Manifest Repaired:    0
2022-08-17 12:03:51, Info                  CBS        CSI Payload Repaired:    0
2022-08-17 12:03:51, Info                  CBS        CSI Store Metadata refreshed:    True
2022-08-17 12:03:51, Info                  CBS    Staged Packages:
2022-08-17 12:03:51, Info                  CBS        CBS Staged packages:    0
2022-08-17 12:03:51, Info                  CBS        CBS Staged packages removed:    0
 
Excelent, thanks a lot!
Please feel free to to provide the mising files in such way which is most convenient for you. A runtime of several hours would be no problem either...
 
The folder isn't that big actually, should be okay; please find the fix script below.

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

Many thanks for your script.
SFCFix was successful. Install this time took somehow longer towards the end but finally failed with new error 0x800736b3. CBS looks to me as if only minor things are failing. Please find the logs 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