WS2019 failing to install cumulative updates (0x8024002e)

A

AimarPL

Contributor
Joined
Nov 15, 2018
Posts
97
Hi!
I'm having an issue with WS2019 and its cumulative updates - for some months already, they're not getting installed and failing with 0x8024002e code.
Tried SFC, tried DISM, tried direct WU instead of WSUS, tried manual patch installation, but... it always ends up with the same result.

Then, i remembered about this forums here and tool you had (sfcfix or smth like that), which is now replaced with componentscanner that I've tried too, it found one critical error, but i've no idea how to fix it:

Code: 
Windows Version: Windows Server 2019 Standard x64 (10.0.17763.3165)
Start time: 2022-11-24T07:48:37
Hive scanned: %windir%\System32\config\COMPONENTS
Number of keys: 793301
Number of values: 1354942

==== Critical Errors ====
Critical registry key "COMPONENTS\DerivedData\VersionedIndex\10.0.17763.2350 (WinBuild.160101.0800)\ComponentFamilies" exists but has no subkeys

==== Corrupt Key Names ====
None

==== Corrupt Value Names ====
None

==== Corrupt Value Data Type ====
None

==== Corrupt Value Data ====
None

==== Repair Log ====
No possible repairs

==== Warnings ====
None

I'm attaching CBS logs here: CBS.zip

And hoping for you hints, got to fix this WS box without a reinstall scenario.
Thank you in advance!
 
Hi guys, any ideas? or is it indeed so messed up that reinstall is the only option now?
Thanks in advance!
 
Hi,

Do you have back-ups of the COMPONENTS hive of this server?

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.

Download the
577bf0efb8088-FRST.png
Farbar Recovery Scan Tool and save it to your Desktop:

Download the 64 bit version: - Farbar Recovery Scan Tool Link

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

  • Download the attachment fixlist.txt and save it to your desktop.
  • Right-click on FRST.exe and select "Run as administrator".
  • Press the Fix button.
  • If for some reason the tool needs a restart, please make sure you let the system restart normally.
  • When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
  • Post the logfile Fixlog.txt as attachment in your next reply.

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

Attachments

Hi, @Maxstar, thank you for your hints!

Current WU error is: (0x800705b4)

Here's the fixlog content:

Code: 
fixlist content:
*****************
CreateRestorePoint:
CMD: reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS
DeleteValue: HKLM\COMPONENTS|ExecutionState
DeleteValue: HKLM\COMPONENTS|PendingXmlIdentifier
*****************

Error: (0) Failed to create a restore point.

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

The operation completed successfully.


========= End of CMD: =========

"HKLM\COMPONENTS\\ExecutionState" => removed successfully
"HKLM\COMPONENTS\\PendingXmlIdentifier" => removed successfully

==== End of Fixlog 08:01:53 ====

New CBS logs are here
 
Hi,

Please upload a new copy of the COMPONENTS hive, and the CBS hive.

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.
    Code: 
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing
  • Once selected, click File > Export....
  • Change the Save as type: to Registry Hive Files (*.*).

    622dbef75cd3a-Export-CBS-hive.png

  • 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.
 
Instead of a new copy of the CBS folder, I asked for the COMPONENTS hive, see post #3.
 
correct, i've noticed that second after sending the post :)

it's uploaded already:

Here's CBS: CBS
Here's ComponentsBasedServicing: link
Components: link
 
Could you please attempt to update again with Process Monitor running.

Step#1 - Capture Process Monitor Trace
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.
 
It took a lot of time, but... finally ended up with following error code: (0x800705b4)
CBS Logs are here: cbs
ProcMon logs are here: PML
 
Hi,

This error (0x800705b4) has to due with an timeout issue. It seems KB5015811 installed from the WSUS server and still marked as pending. Please configure WSUS and then perform two reboots.
 
well, i have done multiple reboots and re-done whole process listed here (with system roll back via snapshotting), but always ending up with the same issue:

2019-06 Servicing Stack Update for Windows Server 2019 for x64-based Systems (KB4504369) - Error 0x8000ffff (sometimes 0x80240034)
and "Failed to install on ‎12/‎2/‎2022" - 0x800f0840 for cumulative update

It fails even with manually downloaded update files (bypassing wsus). WSUS itself seems to be working just fine, all updates are approved (it's approval server only, patches are downloaded directly from WU).

I'm attaching current CBS logs, maybe there's something more now.
CBS Logs

Any ideas what could that be?
 
Hi,

This is the latest installed Servicing Stack Update: SSU-17763.3100 (KB5014797), could you please try to hide KB4504369?

Download
62877701aaac2-WusWowHide24.png
wushowhide.diagcab to hide an update.
  • Double click on the wushowhide.diagcab file and press Next.
  • Now the tool will search for updates and performs a scan to detect problems.
  • When this process is complete click on Hide updates.
  • Now an overview will appear with updates that have not yet been installed.
  • Select the update you want to hide and press Next.
  • When the troubleshooting has complete you can close the tool.
 
thanks @Maxstar,
after doing so it's skipping this update indeed, failing to install others and after the reboot on search for updates it fails with following code now:

Code: 
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: (0x800705b4)

CBS logs are attached here
 
Hi,

It seems Windows Update is trying to install another (old) SSU, could you please post a screenhot of the Update History from the settings screen.
 
Run the following DISM command and post the result. If it fails attach a new copy of the CBS log.
Code: 
DISM /online /cleanup-image /RestoreHealth
 
@Maxstar,
DISM finished successfully (without any errors shown), but afterwards i made a WU scan which failed so i did a reboot and run WU again.
Unfortunately, WU fails with following error:

Code: 
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: (0x800705b4)

CBS logs are here
 
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