Windows Server 2022 - KB5021249 failing to install with error 0x800f081f

[biosphere]

Running Windows Update pass on Server 2022 fails on installing "2022-12 Cumulative Update for Microsoft server operating system version 21H2 for x64-based Systems (KB5021249)" with "Status: Download error 0x800f081f".

Rebooting the server does not help, and same error appears when running the update manually (MSU downloaded from Update catalog).

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.

dism /online /cleanup-image /restorehealth:

Deployment Image Servicing and Management tool
Version: 10.0.20348.681

Image Version: 10.0.20348.1249

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

 

[biosphere]

Anyone have any input here?

 

[Maxstar]

Hi and welcome to Sysnative,

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.

Afterwards, reboot the server and attempt to update. If it fails attach a new copy of the CBS log(s).

 

[biosphere]

Thank you.

Ran SFCFix, rebooted, ran update again. Failed again, but in a different way.

The error message is now "There were some problems installing updates, but we'll try again later. If you keep seeing this and want to search the web or contact support for information, this may help: (0x800f081f)", and only KB5022291 is listed available as opposed to both that KB and the cumulative .Net one previously.

CBS.log was unfortunately too large to attach, so had to zip it.

 

[Maxstar]

Hi,

Could you please provide the following hive files.

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.

Export CBS (Component Based Servicing) hive

• Click on the Start button and type regedit
• When you see regedit on the list, right-click on it and select Run as administrator.
• 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\Component Based Servicing

• Once selected, click File > Export....
• Change the Save as type: to Registry Hive Files (*.*).
  
  
  
  
  
• Name this file ComponentBasedServicing (with no file extension) and save it to your Desktop.
• Right-click on the saved file and choose Send > Compressed (zipped) Folder.
• Attach the .ZIP file to your next post.
• If the file is too large to upload here, upload the file to www.wetransfer.com and post the link in your next reply.

 

[biosphere]

Thank you, here you go.

 

[Maxstar]

Hi,

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.

Afterwards, reboot the server and attempt to update. If it fails attach a new copy of the CBS log.

 

[biosphere]

Ran SFCFix, rebooted. On reboot it appeared to install some updates, after reboot it spent a while at "Cleaning up" before getting to login screen.

Updates fail after reboot, but now with a different error message: "There were some problems installing updates, but we'll try again later. If you keep seeing this and want to search the web or contact support for information, this may help: (0x80070002)".

New copy of CBS.log attached (had to be zipped due to size).

 

[Maxstar]

2023-01-17 16:08:14, Info                  CBS    Not able to add SCM.EVM to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2023-01-17 16:08:14, Error                 CSI    000002e6 (F) STATUS_OBJECT_NAME_NOT_FOUND #1528060# from Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey(flg = 0, key = {provider=NULL, handle=0, name= ("null")}, da = (KEY_ALL_ACCESS|KEY_WOW64_64KEY), oa = @0x9763dfbd28->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[196]'\Registry\Machine\COMPONENTS\DerivedData\VersionedIndex\10.0.20348.1300 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-windows-slb-mux-perfcounters_31bf3856ad364e35_none_001811c5231d5abb'; a:(OBJ_CASE_INSENSITIVE)[gle=0xd0000034]
2023-01-17 16:08:14, Error                 CSI    }, disp = Invalid)[gle=0xd0000034]
2023-01-17 16:08:14, Error                 CSI    000002e7 (F) STATUS_OBJECT_NAME_NOT_FOUND #1528059# from Windows::Rtl::SystemImplementation::CKey::OpenExistingKey(f = 2, da = (KEY_ALL_ACCESS), oa = @0x9763dfc380, key = NULL, disp = (null))[gle=0xd0000034]

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 SFCFixScript.txt and save it to your desktop.
• Drag the SFCFixScript.txt 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.

Afterwards, reboot the server and attempt to update. If it fails attach a new copy of the CBS log.

 

[biosphere]

Still failing, see files attached.

 

[Maxstar]

2023-01-17 17:08:25, Error                 CSI    000002fc (F) STATUS_OBJECT_NAME_NOT_FOUND #3281046# from Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey(flg = 0, key = {provider=NULL, handle=0, name= ("null")}, da = (KEY_ALL_ACCESS|KEY_WOW64_64KEY), oa = @0xc25a47bf68->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[188]'\Registry\Machine\COMPONENTS\DerivedData\VersionedIndex\10.0.20348.1300 (WinBuild.160101.0800)\ComponentFamilies\msil_microsoft-windows-slbmux-events_31bf3856ad364e35_none_6d8897e5b977b8b0'; a:(OBJ_CASE_INSENSITIVE)}, disp [gle=0xd0000034]
2023-01-17 17:08:25, Error                 CSI    = Invalid)[gle=0xd0000034]
2023-01-17 17:08:25, Error                 CSI    000002fd (F) STATUS_OBJECT_NAME_NOT_FOUND #3281045# from Windows::Rtl::SystemImplementation::CKey::OpenExistingKey(f = 2, da = (KEY_ALL_ACCESS), oa = @0xc25a47c5c0, key = NULL, disp = (null))[gle=0xd0000034]
2023-01-17 17:08:25, Error                 CSI    000002fe (F) HRESULT_FROM_WIN32(ERROR_FILE_NOT_FOUND) #3197115# from Windows::ServicingAPI::CCSITransaction::ICSITransaction_EnumMissingComponents(Flags = 0, ppe = NULL, disp = 0)[gle=0x80070002]

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 SFCFixScript.txt and save it to your desktop.
• Drag the SFCFixScript.txt 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.

Afterwards, reboot the server and attempt to update. If it fails attach a new copy of the CBS log.

 

[biosphere]

Still failing, but this time with original error message: "There were some problems installing updates, but we'll try again later. If you keep seeing this and want to search the web or contact support for information, this may help: (0x800f081f)"

Files attached.

 

[Maxstar]

Hi,

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.

Afterwards, reboot the server and attempt to update. If it fails attach a new copy of the CBS log.

 

[biosphere]

Unfortunately this also failed. New error message though: There were some problems installing updates, but we'll try again later. If you keep seeing this and want to search the web or contact support for information, this may help: (0x800f0982)

Files attached.

 

[biosphere]

Previous CBS upload looked incomplete to me, here's one that looks more complete.

 

[Maxstar]

2023-01-18 18:28:43, Error                 CSI    00000584 (F) Cannot identify matching versions for component Microsoft-Windows-Slb-Mux, version 10.0.20348.859, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}.[gle=0x80004005]
2023-01-18 18:28:43, Error                 CSI    00000585@2023/1/18:17:28:43.676 (F) Attempting to mark store corrupt with category [l:21 ml:22]'CorruptComponentValue'[gle=0x80004005]
2023-01-18 18:28:43, Error                 CSI    00000586@2023/1/18:17:28:43.676 (F) onecore\base\wcp\componentstore\storelayout.cpp(2202): Error 800f0982 [Warning,Facility=15 (0x000f),Code=2434 (0x0982)] originated in function ComponentStore::CRawStoreLayout::AddComponentFile expression: ((SCODE) (((unsigned long)(1)<<31) | ((unsigned long)(15)<<16) | ((unsigned long)(0x982))) )
[gle=0x80004005]

Hi,

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.

Afterwards, reboot the server and attempt to update. If it fails attach a new copy of the CBS log.

 

[biosphere]

Hello!

Apologies for the late reply, but seen as this issue impacted a large number of deployments I had a parallel track with MS Support.

In short their explanation was that a rare combination of a specific 2022 ISO build and sysprep caused a loop condition where a superseded patch for some reason got tagged as not superseded, thus blocking any further updates beyond the (un)superseded patch.

Unfortunately (at least according to them) the only option is to in-place upgrade using the latest 2022 ISO available. We've done a few test runs and it seems to work, although very timeconsuming and annoying (need to plan _so_ many outages...).

Anyhoo - thank you so much for your assistance and help, the service provided by this community is absolutely golden. Thanks!

 

[Maxstar]

Hi,

There is no need to apologize, however, I am curious about the detailed explanation for "(...) ISO build and sysprep caused a loop condition..." Are there any particular tools or scripts used to further investigate this issue?

 

[biosphere]

Hi,

There is no need to apologize, however, I am curious about the detailed explanation for "(...) ISO build and sysprep caused a loop condition..." Are there any particular tools or scripts used to further investigate this issue?

They had us run their TSS toolset (Introduction to TroubleShootingScript toolset (TSSv2) - Windows Client). Based off of that, the information provided (from a Teams call, so this is from memory) was that KB5005039 had the supersede issue and causing the loop.

At first they has us install an SSU update and then attempt install of KB5005039 from catalog, but that failed with like a "this update is not applicable" or something.

After that their only recommendation was to do an in-place upgrade using newest available 2022 ISO. That has worked on all systems we have tried the fix on far, but obviously time-consuming. I'm a bit baffled that they would not be able to either remove the offending update or fix its dependency issues causing the loop, but it is what it is.

 

[Maxstar]

Thanks for sharing the additional information! KB5005039 is an old update from August 2021 and all the errors in de the CBS log refer to other updates? The latest error has to due with a component of this preview update KB5015879 from last year.