[SOLVED] Server 2022 Can't install CU - CBS Error HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING

vinda53

vinda53

Member
Joined
Jun 6, 2024
Posts
17
Hi all.

Seem to have the same issue a few others have had recently with Server 2022 and not being able to install CU's.
I have done all the usual SFC and DISM repair commands and Windows Update Component stuff.

Seems to be the same point of failure as others too:

024-06-11 11:05:13, Info CBS Exec: Warning - Manifest doesn't exist for: \\?\C:\Windows\CbsTemp\31112165_1639837719\Windows10.0-KB5037782-x64.cab\amd64_microsoft-windows-slb-mux.resources_31bf3856ad364e35_10.0.20348.1_de-de_cd5d7147fb33674b.manifest
2024-06-11 11:05:13, Info CBS Component Identity: Microsoft-Windows-Slb-Mux.Resources, Culture=de-DE, Version=10.0.20348.1, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS
2024-06-11 11:05:13, Info CBS Exec: Warning - Manifest doesn't exist for: \\?\C:\Windows\CbsTemp\31112165_1639837719\Windows10.0-KB5037782-x64.cab\amd64_microsoft-windows-s..fcounters.resources_31bf3856ad364e35_10.0.20348.1_de-de_870f5a3b78c5a188.manifest
2024-06-11 11:05:13, Info CBS Component Identity: Microsoft-Windows-Slb-Mux-PerfCounters.Resources, Culture=de-DE, Version=10.0.20348.1, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS
2024-06-11 11:05:13, Error CSI 000006ee@2024/6/11:10:05:13.397 (F) onecore\base\wcp\sil\ntsystem.cpp(2823): Error STATUS_OBJECT_NAME_NOT_FOUND originated in function Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysCreateFile expression: (null)
[gle=0x80004005]
2024-06-11 11:05:13, Info CBS Added C:\Windows\Logs\CBS\CBS.log to WER report.
2024-06-11 11:05:13, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20240611042203.cab to WER report.
2024-06-11 11:05:13, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20240610214037.cab to WER report.
2024-06-11 11:05:13, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20240610154039.cab to WER report.
2024-06-11 11:05:13, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20240610094053.cab to WER report.
2024-06-11 11:05:13, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20240610042159.cab to WER report.
2024-06-11 11:05:13, Info CBS Not able to add pending.xml to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2024-06-11 11:05:13, Info CBS Not able to add pending.xml.bad to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2024-06-11 11:05:13, Info CBS Not able to add SCM.EVM to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2024-06-11 11:05:13, Error CSI 000006ef (F) STATUS_OBJECT_NAME_NOT_FOUND #11580125# from Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysCreateFile(flags = 0, handle = {provider=NULL, handle=0, name= ("null")}, da = (FILE_GENERIC_READ|DELETE|WRITE_DAC|WRITE_OWNER|FILE_WRITE_ATTRIBUTES), oa = @0xee9ebfc0c0->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[176]'\??\C:\Windows\CbsTemp\31112165_1639837719\Windows10.0-KB5037782-x64.cab\amd64_microsoft-windows-slb-mux.resources_31bf3856ad364e35_10.0.20348.1_de-de_cd5d7147fb33674b.manife[gle=0xd0000034]
2024-06-11 11:05:13, Error CSI st'; a:(OBJ_CASE_INSENSITIVE)}, iosb = @0xee9ebfc138, as = (null), fa = (FILE_ATTRIBUTE_NORMAL), sa = (FILE_SHARE_READ|FILE_SHARE_WRITE|FILE_SHARE_DELETE), cd = FILE_OPEN, co = (FILE_NON_DIRECTORY_FILE|FILE_SYNCHRONOUS_IO_NONALERT|0x00004000), eab = NULL, eal = 0, disp = Invalid)
[gle=0xd0000034]
2024-06-11 11:05:13, Error CSI 000006f0 (F) STATUS_OBJECT_NAME_NOT_FOUND #11580124# from Windows::Rtl::SystemImplementation::CSystemIsolationLayer_IRtlSystemIsolationLayerTearoff::TransferFileEx(flags = (OpenForBackupIntent), op = 'Move', odir = NULL, oname = [l:176]'\??\C:\Windows\CbsTemp\31112165_1639837719\Windows10.0-KB5037782-x64.cab\amd64_microsoft-windows-slb-mux.resources_31bf3856ad364e35_10.0.20348.1_de-de_cd5d7147fb33674b.manifest', ndir = @0x1fbc71ff300, nname = [l:41 ml:63]'bd0beed9e6bbda019bbd0000c803e02c_manifest', disp = [gle=0xd0000034]
2024-06-11 11:05:13, Error CSI Unmapped disposition: 0)
[gle=0xd0000034]
2024-06-11 11:05:13, Error CSI 000006f1 (F) HRESULT_FROM_WIN32(ERROR_FILE_NOT_FOUND) #11574736# from Windows::ServicingAPI::CCSITransaction::ICSITransaction2_AddComponents(Flags = 4, a = @0x1fbbf5d6130, mp = @0x1fbbf5d6930, disp = 0)[gle=0x80070002]
2024-06-11 11:05:13, Info CBS Failed to add one or more component [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]
2024-06-11 11:05:13, Error CBS Failed to complete component closure [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]
2024-06-11 11:05:13, Info CBS CommitPackagesState: Started persisting state of packages
2024-06-11 11:05:13, Info CBS CommitPackagesState: Completed persisting state of packages
2024-06-11 11:05:13, Info CSI 000006f2@2024/6/11:10:05:13.892 CSI Transaction @0x1fba4207240 destroyed
2024-06-11 11:05:13, Info CBS Perf: Resolve chain complete.
2024-06-11 11:05:13, Info CBS Failed to resolve execution chain. [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]
2024-06-11 11:05:13, Error CBS Failed to process single phase execution. [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]
2024-06-11 11:05:13, Info CBS WER: Generating failure report for package: Package_for_RollupFix~31bf3856ad364e35~amd64~~20348.2461.1.11, status: 0x800f081f, failure source: Resolve, start state: Absent, target state: Installed, client id: UpdateAgentLCU

This is a single server domain controller and application server so I don't think it would survive an in-place upgrade without issues.

Really hope you can help.

Thanks in advance.
 
Sincere apologies, I didn't upload the CBS log or Components Scan.
I have since re-ran the updates and the June CU fails with the same error.

Attached are the CBS.zip we transfer link and Components Scanner text log.

CBS.log
 

Attachments

Hi and welcome to Sysnative,

Upload your COMPONENTS hive.
  • Navigate to C:\Windows\System32\Config and locate the COMPONENTS file.
  • 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.
  • 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.
  • If the file is too large to upload here, upload the file to www.wetransfer.com and post the link in your next reply.
 
Hi,

Here's the first fix.

Step 1. Download
6530fbb0f4101-56f31e53c97da-SFCFix.PNG
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.
650c22f99662d-6190d993a26f3-SFCFix-Zip-Eng.gif

  • 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. Attempt to update again with Proces Monitor running.
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 (CTRL +E) on the toolbar as shown below.



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 the LogFile.PML and upload it to WeTransfer - Send Large Files & Share Photos Online - Up to 2GB Free and provide the link.
6. Provide also a new copy of the CBS logs for the time stamps.
 

Attachments

Here's the next fix.

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.
650c22f99662d-6190d993a26f3-SFCFix-Zip-Eng.gif

  • 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.

Afterwards attempt to update again (no need to run ProcMon) and let me know the result. If it fails attach a new copy of the CBS logs.
 

Attachments

Looked like it was going a lot longer at the 44% mark before jumping to 100% and then the failure.
Here's the latest CBS:

CBS.zip

Thanks.
 
Here's the next fix.

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.
650c22f99662d-6190d993a26f3-SFCFix-Zip-Eng.gif

  • 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.

Afterwards attempt to update again. If it fails attach a new copy of the CBS logs.
 

Attachments

Here's the next fix.

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.
650c22f99662d-6190d993a26f3-SFCFix-Zip-Eng.gif

  • 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.

Afterwards attempt to update again. If it fails attach a new copy of the CBS logs.
 

Attachments

Good morning too!

Here's the next fix.

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.
650c22f99662d-6190d993a26f3-SFCFix-Zip-Eng.gif

  • 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.

Afterwards attempt to update again. If it fails attach a new copy of the CBS logs.
 

Attachments

Next fix.

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.
650c22f99662d-6190d993a26f3-SFCFix-Zip-Eng.gif

  • 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.

Afterwards attempt to update again. If it fails attach a new copy of the CBS logs.
 

Attachments

Failed again. The logs seem to show the different language versions of that failing update / package.

Thanks again for all this help.

CBS.zip
 

Attachments

Indeed, but unfortunately the CBS logs shows only one or two components each time.

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.
650c22f99662d-6190d993a26f3-SFCFix-Zip-Eng.gif

  • 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.

Afterwards attempt to update again. If it fails attach a new copy of the 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