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

Rich (BB code): 
2022-08-18 18:29:55, Info                  CSI    0000039e TLC operation Install incomplete for [Microsoft-Windows-Product-Data-21h1-EKB-Deployment, version 10.0.19041.1889, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}]), missing compositions
    Microsoft-Product-Data, version 10.19043.19041.1889, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}
    Microsoft-Product-Data, version 10.19043.19041.1889, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35}

2022-08-18 18:29:55, Error                 CSI    0000039f@2022/8/18:16:29:55.979 (F) onecore\base\wcp\componentstore\csd_winners.cpp(560): Error STATUS_SXS_ASSEMBLY_NOT_FOUND originated in function CCSDirectTransaction::PerformChangeAnalysis expression: (null)
[gle=0x80004005]

It was a nice and simple one this time, please find attached.
 

Attachments

Thanks for the quick update.
However, install this time ends with new error 0x800736b3. A DSIM afterwards still complains about missing source files. Seems there are still lots of them. Please find all latest logfiles here: Sysnative
 
Rich (BB code): 
2022-08-19 09:01:05, Info                  CBS    FLOW: Enter Installation Stage: Closure Analysis, Current Operation Stage: Installing
2022-08-19 09:01:26, Info                  CSI    000002f2 TLC operation Install incomplete for [Microsoft-Windows-Product-Data-EKB-Deployment, version 10.0.19041.1889, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}]), missing compositions
    Microsoft-Product-Data, version 10.19042.19041.1889, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}
    Microsoft-Product-Data, version 10.19042.19041.1889, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35}

It looks like this error is back, could you please provide your SideBySide subkey as a registry hive using the following instructions?

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.

I'll work on finding the missing files for you as well.
 
And here is the result after running SFCFix from post #64.
Install ends again with error 0x800736b3. You may find latest CBS, components, Logfile and SxS here: Sysnative
Timestamp for all of them is 202208191150. I didn't dare to run DSIM not to destroy something.
 
Please find the second part of the fix attached for the earlier error. Afterwards, you might want to run DISM before attempting to update and check if it runs successfully or not. We probably won't need the Process Monitor logs for now so please feel free not to run it.
 

Attachments

Many thanks for your instructions and update!
DSIM reports the same issue as in post #54 (sources not found). But to me it seems as if only one single provider-dll is missing.
Install ended with known error 0x800736b3. Please find all logs here: Sysnative
Timestamp for all of them is 202208191400.
 
Robby said:
DSIM reports the same issue as in post #54 (sources not found). But to me it seems as if only one single provider-dll is missing.
Click to expand...
There is about 1162 files this time, you have to search for Checking System Update Readiness and then scroll down for the summary section which is the following:

Rich (BB code): 
2022-08-19 13:45:16, Info                  CBS    Summary:
2022-08-19 13:45:16, Info                  CBS    Operation: Detect and Repair 
2022-08-19 13:45:16, Info                  CBS    Operation result: 0x800f081f
2022-08-19 13:45:16, Info                  CBS    Last Successful Step: Remove staged packages completes.
2022-08-19 13:45:16, Info                  CBS    Total Detected Corruption:    1162
2022-08-19 13:45:16, Info                  CBS        CBS Manifest Corruption:    0
2022-08-19 13:45:16, Info                  CBS        CBS Metadata Corruption:    0
2022-08-19 13:45:16, Info                  CBS        CSI Manifest Corruption:    0
2022-08-19 13:45:16, Info                  CBS        CSI Metadata Corruption:    0
2022-08-19 13:45:16, Info                  CBS        CSI Payload Corruption:    1162
2022-08-19 13:45:16, Info                  CBS    Total Repaired Corruption:    0
2022-08-19 13:45:16, Info                  CBS        CBS Manifest Repaired:    0
2022-08-19 13:45:16, Info                  CBS        CSI Manifest Repaired:    0
2022-08-19 13:45:16, Info                  CBS        CSI Payload Repaired:    0
2022-08-19 13:45:16, Info                  CBS        CSI Store Metadata refreshed:    True
2022-08-19 13:45:16, Info                  CBS    Staged Packages:
2022-08-19 13:45:16, Info                  CBS        CBS Staged packages:    1
2022-08-19 13:45:16, Info                  CBS        CBS Staged packages removed:    0

The latest fix batch should be 76.6MB and is available here.
 
Many thanks - understand! You see, I'm not a Sysadm and without your help I would be lost with this issue...
Unfortunately same error as last time. However, along with your instructions I see only two more missing corruptions left.
Please find current logfiles here: Sysnative
Timestamp for all of them is 202208221330.
 
It looks like we've got this error again but with different components this time:

Rich (BB code): 
2022-08-22 13:33:04, Info                  CSI    000014b3 TLC operation Install incomplete for [Microsoft-Windows-UpdateTargeting-ClientOS-21h1-EKB-Deployment, version 10.0.19041.1889, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}]), missing compositions
    Microsoft-EmergencyUpdate, version 10.19043.19041.1889, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}
    Microsoft-UpdateTargeting-ClientOS, version 10.19043.19041.1889, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}

And just the manifest files for the component keys I added back in the last fix, I should imagine that the same is going to apply with the above too:

Rich (BB code): 
2022-08-22 13:27:49, Info                  CBS    (p)    CSI Manifest Corrupt    (n)            wow64_microsoft-product-data_31bf3856ad364e35_10.19042.19041.1889_none_017b556e442e013f
2022-08-22 13:27:49, Info                  CBS    Repair failed: Missing replacement manifest.
2022-08-22 13:27:49, Info                  CBS    (p)    CSI Manifest Corrupt    (n)            amd64_microsoft-product-data_31bf3856ad364e35_10.19042.19041.1889_none_f726ab1c0fcd3f44
2022-08-22 13:27:49, Info                  CBS    Repair failed: Missing replacement manifest.
 

Attachments

Thanks for the new update, things now get somehow different:
DISM says "successfully restored files" and no more corruptions are reported in CBS. However, install still ends with error 0x800736b3.
Please find current logfiles here: Sysnative
Timestamp for all of them is 202208221855.
 
It looks like DISM is clear which is good, however, unfortunately it seems that you've got another few of these errors:

Rich (BB code): 
2022-08-22 18:54:39, Info                  CSI    00000a69 TLC operation Install incomplete for [Microsoft-Windows-UpdateTargeting-ClientOS-EKB-Deployment, version 10.0.19041.1889, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}]), missing compositions
    Microsoft-EmergencyUpdate, version 10.19042.19041.1889, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}
    Microsoft-UpdateTargeting-ClientOS, version 10.19042.19041.1889, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}

Please find the attached fix script.
 

Attachments

Many thanks for yoz fix, this time things went much different. Install finalized and asked to reboot the PC. The message was that updates are being installed and the computer did restart two times. At the end it was reported that the update could not be finalized and will be uninstalled again. I already thought we are trough...
Please find the latest CBS_202208241510 here: Sysnative
 
Let's take a look at what is happening over the update using Process Monitor, please follow these instructions:

Capture Process Monitor BootLog
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Select the Options....Enable Boot Logging option. A Enable Boot Logging dialog will come up. Just click OK.
3. Create a folder on your desktop named BootLog.
4. Attempt to install the update just like you have in the past. Let the machine reboot and revert just like it has in the past.
5. After the machine has rebooted and come back up to the desktop, open Process Monitor again. A message box will come up telling you that a log of boot-time activity was created and ask if you wish to save it. Click Yes and save to the BootLog folder on your desktop.
6. This may take some time as it converts the boot-time data. Allow it to finish.
7. Zip up the entire BootLog folder on your desktop and upload to a file sharing service of your choice for my review. Examples of services to upload to are Dropbox or OneDrive or SendSpace
 
Thanks for your crystal clear instructions. Please find the resulting BootLog here: Sysnative
Just for information: In the meantime I ran Windows update troubleshooter and DISM. But, as you said, there was indeed absolutely no change in update behavior visible.
 
Unfortunately, I can't seem to find any obvious errors from the ProcMon boot trace or your CBS logs. Are you trying to install KB5015807 still?

FRST Registry Search
1. Click your Start button and type in cmd.
2.After you find the Command Prompt, right click on it and select Run as Administrator.
3. Copy and paste the following into the Command Prompt:

reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS

4. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
5. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
6. Copy and paste KB5015807 into the Search box and click the Search Registry button.
7. When the scan is complete a notepad window will open with the results. Please attach this to your next reply. It is saved on your desktop named SearchReg.txt.
 
Indeed, we started with KB5015807 failing persistently. However, as reported in post #29, Microsoft has provided new updates on Aug 10th. KB5015807 was no longer visible to me and obviously replaced by new KB5016616. This one was failing again with the same error message and CBS-output as the previous KB5015807. Meanwhile we have KB5016616 being installed nicely but removed again after the re-boot procedure showing error 0x800f0841.

To my understanding the current CBS log (CBS_202208241510.ZIP) however shows one error:
2022-08-24 15:12:01, Error CBS Package "Package_for_KB5008295~31bf3856ad364e35~amd64~~22000.318.1.1" requires Servicing Stack v10.0.22000.190 but current Servicing Stack is v10.0.19041.1852. [HRESULT = 0x800f0823 - CBS_E_NEW_SERVICING_STACK_REQUIRED]
How do you think? Is it serious?

Please find enclosed SearchReg.txt for KB5015807 and KB5016616.
 

Attachments

The issue is resolved !

I have used Microsoft Media Creation Tool to generate a fresh boot-stick with my current Windows version. Then running Setup.exe and chosing Win10 installation while keeping apps and user data. After 30 minutes my computer was up again and did install all available updates without any issues.

Anyway, many thanks to you for your time and dedication you have put into this issue! Your help was highly appreciated! A donation will follow shortly. Please feel free to close this threat now.
 
Robby said:
To my understanding the current CBS log (CBS_202208241510.ZIP) however shows one error:
2022-08-24 15:12:01, Error CBS Package "Package_for_KB5008295~31bf3856ad364e35~amd64~~22000.318.1.1" requires Servicing Stack v10.0.22000.190 but current Servicing Stack is v10.0.19041.1852. [HRESULT = 0x800f0823 - CBS_E_NEW_SERVICING_STACK_REQUIRED]
How do you think? Is it serious?
Click to expand...
That's quite a common false flag you see with Windows 10 machines, I've seen it in a few CBS logs and it doesn't actually cause issues. I believe it happens because with the later Windows 10 updates there is some cross-over with Windows 11 so it believes that you need the servicing stack version for Windows 11 despite the fact that you're on the latest version for Windows 10.

Robby said:
Anyway, many thanks to you for your time and dedication you have put into this issue! Your help was highly appreciated! A donation will follow shortly. Please feel free to close this threat now.
Click to expand...
Thank you very much! I've marked this thread as solved for you. I'm glad you got everything resolved in the end.
 
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