[SOLVED] Server 2019 Essentials (Domain Controller) component store corruption

Hi,

We are still looking into this problem, but some additional information could be help as well.
- Is the clone exactly the same as the production server?

This because you were able to repair the COMPONENTS hive on the clone, but failed on the production server. (failed to parse hive, this could indicate major corruption)

Rich (BB code): 
2022-12-18 11:07:43, Info                  CBS    (p)    CBS Catalog Missing    (n)            Package_80_for_KB2992611~31bf3856ad364e35~amd64~~6.1.1.0

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
  • Open the startmenu and type the command cmd.
  • After you find the Command Prompt, right click on it and select Run as Administrator.
  • Copy and paste the following into the Command Prompt and press enter.
Code: 
reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS
Right-click on the file FRST64.exe and choose Run as administrator.
  • Copy and paste the following (code) into the Search box and click the Search Registry button.
Code: 
KB2992611
  • When the scan is complete, a message will display that SearchReg.txt is saved in the same folder FRST was started from.
  • Post the logfile SearchReg.txt as attachment in your next reply.
 
Clone was taken a few weeks ago. Prod system is online (on internet), in use, and active. Windows updates still attempting to occur.

2022-12 Cumulative Update for .NET Framework 3.5, 4.7.2 and 4.8 for Windows Server 2019 for x64 (KB5021085) is Pending Restart
2022-12 Cumulative Update for Windows Server 2019 (1809) for x64-based Systems (KB5021237) is Pending Install

Clone is offline (not on internet). I attempted multiple repairs prior to last resort reaching out on forums, so there may be some differences. Hardware is different as well.
 

Attachments

Thanks for the update, I will get back to you as soon as possible, but it can take some time...
 
No problem at all, thank you. I work on this server for a non-profit senior community center, so any help is appreciated.
 
Hi,

What was the result of Windows Update on the production server? Please post a new copy of the CBS log as well as the COMPONENTS hive.
 
Some update files are missing or have problems. We'll try to download the update again later. Error code: (0x80073712)
.net update and Malicious Software tool were successful

2022-12 Cumulative Update for Windows Server 2019 (1809) for x64-based Systems (KB5021237) (10 attempts)
Last failed install attempt on ‎12/‎20/‎2022 - 0x80073712

2022-11 Cumulative Update for Windows Server 2019 (1809) for x64-based Systems (KB5019966) (57 attempts)
Last failed install attempt on ‎12/‎14/‎2022 - 0x80240034
 

Attachments

Rich (BB code): 
2022-12-19 22:26:57, Error                 CSI    00000014@2022/12/20:03:26:57.741 (F) onecore\base\wcp\componentstore\versionedindex.cpp(3604): Store corruption detected in function ComponentStore::CRawStoreLayout::CheckFamilyIndexForDeadWinnerComponent expression: (null)
  MissingWinningComponentKey on resource 'amd64_e9c2df2b7f642c2eba97591676533d30_31bf3856ad364e35_10.0.17763.2989_none_44896c720bb18653'[gle=0x80004005]

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.
62151e1bebac4-SFCFix-Txt-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, reboot the server and attempt to update. If it fails attach a new copy of the CBS log.
 

Attachments

Installation of 2022-12 Cumulative Update (KB5021237) is attempting install. Has been at 20% for 10 minutes. Will send CBS logs once it completes or fails
 
Thanks, for the next fix I'll need to prepare a Server 2019 VM with (some older) updates to provide the next fix. So this will be tomorrow, I think....
 
Rich (BB code): 
2022-12-20 10:33:23, Error                 CSI    00000018@2022/12/20:15:33:23.361 (F) onecore\base\wcp\componentstore\versionedindex.cpp(3604): Store corruption detected in function ComponentStore::CRawStoreLayout::CheckFamilyIndexForDeadWinnerComponent expression: (null)
  MissingWinningComponentKey on resource 'amd64_e9c5b6771b5c2bbdfe2788d259614b8c_31bf3856ad364e35_10.0.17763.1697_none_536b6bfdcaa687f0'[gle=0x80004005]

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.
62151e1bebac4-SFCFix-Txt-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, reboot the server and attempt to update. If it fails attach a new copy of the CBS log.
 

Attachments

Out of curiosity, i ran DISM again (i hope that is ok). It now gets to 100% but failed on "cant find source files". So huge improvement, and definitely making progress. thank you
 

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