[SOLVED] WinServer 2022 Update error code 0x800f081f on any CU

A

armal

Active member
Joined
Sep 11, 2024
Posts
32
Hi there,

I have exactly same problem like here [SOLVED] - WinServer 2022 Update error code 0x800f081f on any CU
Win 2022 Server Standard and can not install any CU

Could you help? I'm lost :( I don't want to reinstall system. I attached COMPONENTS file too.

Thanks



CBS Logs:

2024-09-11 22:59:19, Info CBS Component Identity: Microsoft-Windows-Slb-Mux-PerfCounters.Resources, Culture=it-IT, Version=10.0.20348.1, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS
2024-09-11 22:59:19, Info CBS Exec: Warning - Manifest doesn't exist for: \\?\C:\Windows\CbsTemp\31130764_3504910377\Windows10.0-KB5042881-x64.cab\amd64_microsoft-windows-slb-mux-perfcounters_31bf3856ad364e35_10.0.20348.1_none_1da2555dd5ebeb46.manifest
2024-09-11 22:59:19, Info CBS Component Identity: Microsoft-Windows-Slb-Mux-PerfCounters, Culture=neutral, Version=10.0.20348.1, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS
2024-09-11 22:59:19, Info CBS Exec: Warning - Manifest doesn't exist for: \\?\C:\Windows\CbsTemp\31130764_3504910377\Windows10.0-KB5042881-x64.cab\msil_microsoft-windows-slbmux-events_31bf3856ad364e35_10.0.20348.1_none_48fc7f53590719a7.manifest
2024-09-11 22:59:19, Info CBS Component Identity: Microsoft-Windows-SlbMux-Events, Culture=neutral, Version=10.0.20348.1, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=msil, versionScope=NonSxS
2024-09-11 22:59:19, Error CSI 000006ea@2024/9/11:20:59:19.815 (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-09-11 22:59:19, Info CBS Added C:\Windows\Logs\CBS\CBS.log to WER report.
2024-09-11 22:59:19, Info CBS Not able to add pending.xml to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2024-09-11 22:59:19, Info CBS Not able to add pending.xml.bad to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2024-09-11 22:59:19, Info CBS Not able to add SCM.EVM to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2024-09-11 22:59:19, Error CSI 000006eb (F) STATUS_OBJECT_NAME_NOT_FOUND #11863026# 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 = @0x4b23bc500->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[176]'\??\C:\Windows\CbsTemp\31130764_3504910377\Windows10.0-KB5042881-x64.cab\amd64_microsoft-windows-slb-mux.resources_31bf3856ad364e35_10.0.20348.1_it-it_02f9106ab43c6095.manifes[gle=0xd0000034]
2024-09-11 22:59:19, Error CSI t'; a:(OBJ_CASE_INSENSITIVE)}, iosb = @0x4b23bc578, 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-09-11 22:59:19, Error CSI 000006ec (F) STATUS_OBJECT_NAME_NOT_FOUND #11863025# from Windows::Rtl::SystemImplementation::CSystemIsolationLayer_IRtlSystemIsolationLayerTearoff::TransferFileEx(flags = (OpenForBackupIntent), op = 'Move', odir = NULL, oname = [l:176]'\??\C:\Windows\CbsTemp\31130764_3504910377\Windows10.0-KB5042881-x64.cab\amd64_microsoft-windows-slb-mux.resources_31bf3856ad364e35_10.0.20348.1_it-it_02f9106ab43c6095.manifest', ndir = @0x18d85c953d0, nname = [l:41 ml:63]'9b189f788d04db01cba70000e807a426_manifest', disp = [gle=0xd0000034]
2024-09-11 22:59:19, Error CSI Unmapped disposition: 0)
[gle=0xd0000034]
2024-09-11 22:59:19, Error CSI 000006ed (F) HRESULT_FROM_WIN32(ERROR_FILE_NOT_FOUND) #11861958# from Windows::ServicingAPI::CCSITransaction::ICSITransaction2_AddComponents(Flags = 4, a = @0x18dfc23e160, mp = @0x18dfc23e960, disp = 0)[gle=0x80070002]
2024-09-11 22:59:19, Info CBS Failed to add one or more component [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]
2024-09-11 22:59:19, Error CBS Failed to complete component closure [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]
2024-09-11 22:59:19, Info CBS CommitPackagesState: Started persisting state of packages
2024-09-11 22:59:19, Info CBS CommitPackagesState: Completed persisting state of packages
2024-09-11 22:59:19, Info CSI 000006ee@2024/9/11:20:59:19.987 CSI Transaction @0x18de1d87c50 destroyed
2024-09-11 22:59:20, Info CBS Perf: Resolve chain complete.
2024-09-11 22:59:20, Info CBS Failed to resolve execution chain. [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]
2024-09-11 22:59:20, Error CBS Failed to process single phase execution. [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]
2024-09-11 22:59:20, Info CBS WER: Generating failure report for package: Package_for_RollupFix~31bf3856ad364e35~amd64~~20348.2700.1.9, status: 0x800f081f, failure source: Resolve, start state: Absent, target state: Installed, client id: UpdateAgentLCU
2024-09-11 22:59:20, Info CBS Not able to query DisableWerReporting flag. Assuming not set... [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2024-09-11 22:59:20, Info CBS Added C:\Windows\Logs\CBS\CBS.log to WER report.
Click to expand...
 

Attachments

Really guys, it's almost 3 months since I asked. I can not update the system with this problem.
 
Hi there,

I have problems with installing updates for Windows Server 2022. Since July installation of every monthly cumulative update fails with error Download error - 0x800f081f

As you can see below I tried sfcscan and dism update. I waited for the next monthly update but the problem still exists.

I'll be gratefull for any help


-- there are logs from today --

Microsoft Windows [Version 10.0.20348.2402]
(c) Microsoft Corporation. All rights reserved.

C:\Users\Administrator>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.


C:\Users\Administrator>Dism /Online /Cleanup-Image /RestoreHealth

Deployment Image Servicing and Management tool
Version: 10.0.20348.681

Image Version: 10.0.20348.2402


Error: 1223

Operation was incomplete because of a cancel request.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

C:\Users\Administrator>Dism /Online /Cleanup-Image /RestoreHealth

Deployment Image Servicing and Management tool
Version: 10.0.20348.681

Image Version: 10.0.20348.2402

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

C:\Users\Administrator>
 
Hi @armal,

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
 
Hi,

I've merged both threads.

Please provide a new copy of the COMPONENTS hive.

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.
 
Here's the first fix.

Download
67139f7e69a58-SFCFix-ico.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.
67139f52b3c1e-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. If it fails attach a new copy of the CBS logs.
 

Attachments

Please provide the previous Cbs_persist logs as well.

Upload a copy of the CBS folder
  • Open Windows Explorer and browse to the C:\Windows\Logs folder.
  • Right-click on the CBS folder and choose Send to > Compressed (zipped) folder.
  • Now the message will appear, "Windows cannot create the Compressed (zipped) Folder here. Do you want it to be placed on the desktop instead?"
  • Click on the Yes button here.
653a64385d891-618e949e09fef-CBS-Folder.png

  • Attach the file CBS.zip to your next reply. If the file is too large to attach, upload the CBS.zip file to www.wetransfer.com and post the link in your next reply.
 
Hi,

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.
67139f52b3c1e-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. 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.
67139f52b3c1e-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. If it fails attach a new copy of the CBS logs.
 

Attachments

Here's the next fix for another component.

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.
67139f52b3c1e-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. 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