Windows 10 - Missing component delta files

[Ferdi Keijzer]

Hello everyone.

I'm working on a Windows 10 device that is unable to install further updates due to some component store corruption. After investigating the issue, it looks like it is missing some delta files for the following components, that it is expecting when trying to process a session.

The components:
amd64_microsoft-windows-c..riencehost.appxmain_31bf3856ad364e35_10.0.19041.5072_none_77954f3202bfbba5
amd64_microsoft-windows-c..riencehost.appxmain_31bf3856ad364e35_10.0.19041.5198_none_778bf72a02c6a40a

I have a VM at my disposal that I have walked through all monthly updates from last year on, up to and including the latest update, taking snapshots after each update along the way. After attempting to emulate the update path of the affected device, I located the identical component versions in the VMs component store and found that it generated a list of delta files, but not all the files that the affected device is looking for. I made sure to disable the TrustedInstaller service immediately after installing the update and rebooting, to ensure it would not clean up the delta files before I could grab them.

I'm trying to understand why the VM only generates some of the delta files that the affected device is expecting and what I can do to generate them, so I can use them as a source when I run a repair on the component store on the affected device. If anyone could point me in the right direction it would be greatly appreciated. My goal is to gain a better understanding of Windows CBS so I can repair WU issues at the company I work for myself.

I have attached a CBS log that shows the result of the device attempting to repair the corruption and then failing due to the missing files. The log is from a few days ago, but the situation has not changed. Please let me know if I can provide anything else that would help with the investigation.

 

[Windows Update Bot]

Hi @Ferdi Keijzer,

Welcome to Sysnative Forums!

If you haven't already, please review the posting instructions here, and attach the requested log files. Without log files, our helpers will not be able to assist, and this will slow down fixing your machine.

If logs have been already been provided, our team of volunteers will analyse the provided log files to build a fix for your system. Please be aware that this may take several days from your initial post, due to the high volume of threads that we receive.


- Sysnative Windows Update Team

 

[Maxstar]

Hi and welcome to Sysnative,

If anyone could point me in the right direction it would be greatly appreciated (...)

amd64_microsoft-windows-c..riencehost.appxmain_31bf3856ad364e35_10.0.19041.5072_none_77954f3202bfbba5
amd64_microsoft-windows-c..riencehost.appxmain_31bf3856ad364e35_10.0.19041.5198_none_778bf72a02c6a40a

Both update are preview updates:

- 19041.5072 (actually 19045.5073) = KB5045594 - October 22, 2024—KB5045594 (OS Build 19045.5073) Preview - Microsoft Support
- 19041.5198 (19045.5198) = KB5046714 - November 21, 2024—KB5046714 (OS Build 19045.5198) Preview - Microsoft Support

After installing both updates in a VM I wasn't able to source the files either! However I've found them when I extracted the baseless.cab / psf file from UUPdump.

Step 1. Download

SFCFix and save it to your desktop.

Warning: This fix was written specifically for this system. Do not run this fix on another system.

• Save any work you have open, and close all programs.
• Download the attachment SFCFix.zip and save it to your desktop.
• Drag the SFCFix.zip file over the SFCFix.exe executable and release it.

• SFCFix will launch, let it complete.
• Once done, a file will appear on your desktop, called SFCFix.txt.
• Post the logfile (SFCFix.txt) as attachment in your next reply.

Step 2. Run the following DISM command and post the result. If it fails attach a new copy of the CBS log.

DISM /online /cleanup-image /RestoreHealth

 

[Ferdi Keijzer]

Hi Maxstar. Thank you for the assistance!

Thanks to you I was able to repair the aforementioned packages. Once those were fixed it wanted the differentials for a later version, as well. I was not aware of UUPDump before this but was able to locate the baseless version of the patch and used it to successfully repair it.

Unfortunately, it looks like it's now missing a whole range of binaries that it doesn't pick up as corruption during a /ScanHealth. I might be able to make a list of all the components that are missing binaries and simply reinstall those but due to the amount them it looks like it might not be worth the effort. They show up in the CBS log when I try to install the latest patch. I've attached a log illustrating the issue.

It ends the attempt by saying it failed on the "Microsoft-Windows-RSATClient-Services-Package~31bf3856ad364e35~amd64~en-US~10.0.14393.6611" package. I'm hoping all the missing binaries are part of that and will try to reinstall it while I await your response.

Please let me know if you have a more efficient way of resolving this issue.

Thank you.

 

[Maxstar]

It ends the attempt by saying it failed on the "Microsoft-Windows-RSATClient-Services-Package~31bf3856ad364e35~amd64~en-US~10.0.14393.6611" package.

2025-04-15 12:03:31, Error                 CSI    00000d00 (F) HRESULT_FROM_WIN32(ERROR_INVALID_DATA) #40908420# from Windows::COM::CComponentStore::InternalTransact(...)[gle=0x8007000d]
2025-04-15 12:03:31, Error                 CSI    00000d01 (F) HRESULT_FROM_WIN32(ERROR_INVALID_DATA) #40884879# from Windows::ServicingAPI::CCSITransaction::ICSITransaction2_AddFiles(Flags = 17, a = @0x1b73470b370, fn = @0x1b73470bb70, fp = @0x1b73470c370, disp = 0, op = 0)[gle=0x8007000d]
2025-04-15 12:03:31, Info                  CBS    Failed to add to transaction package: Microsoft-Windows-RSATClient-Services-Package~31bf3856ad364e35~amd64~en-US~10.0.14393.6611 [HRESULT = 0x8007000d - ERROR_INVALID_DATA]
2025-04-15 12:03:31, Error                 CBS    Failed to stage execution package: Microsoft-Windows-RSATClient-Services-Package~31bf3856ad364e35~amd64~en-US~10.0.14393.6611 [HRESULT = 0x8007000d - ERROR_INVALID_DATA]

Hi,

I don't know what you've been doing, but it seems you have applied components for build 14393.xxxx Windows 10 1607 on this 19041 +++ build.

 

[Ferdi Keijzer]

That's what I found when I tried locating the package. Could this be a remnant of a feature update from 1607 to 22H2? I believe they upgraded all the clients right before I started working here. I certainly didn't install any packages from older Win 10 builds

I found the patch that the package is supposedly from, but it looks like the 1607 patches have a different naming scheme for their cat/mum pairs so I'm not sure how to locate the correct set.

 

[Maxstar]

Hi,

Download

ComponentsScanner and save it to your desktop.

• Right-click ComponentsScanner.exe and select "Run as administrator", click Yes on the UAC (User Account Control) prompt which appears.
• Follow the on-screen instructions.
• Once complete, a report will be saved to your desktop called ComponentsScanner.txt.
• Post the logfile ComponentsScanner.txt as attachment into your next reply.

 

[Ferdi Keijzer]

I've attached the scan result. I did edit out my username, so security doesn't kill me.

 

[Maxstar]

Please run the following command in an elevated prompt and copy paste the result in your next post.

DISM /online /cleanup-image /AnalyzeComponentStore

 

[Ferdi Keijzer]

Component Store (WinSxS) information:

Windows Explorer Reported Size of Component Store : 9.16 GB

Actual Size of Component Store : 8.81 GB

Shared with Windows : 5.92 GB
Backups and Disabled Features : 2.89 GB
Cache and Temporary Data : 0 bytes

Date of Last Cleanup : 2025-04-16 19:18:41

Number of Reclaimable Packages : 0
Component Store Cleanup Recommended : No