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

jptheripper

jptheripper

Active member
Joined
Dec 6, 2022
Posts
37
I appreciate any help. I am at the end of my knowledge (and my wits).

Server 2019 Essentials, constantly crashing/freezing. Updates fail specifically KB5019966 with 0x80073712

sfc /scannow will not run due to windows resource protection
DISM fails at 4.5% with component store corruption
inplace upgrade freezes at 24%
 

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.
 
Had to reboot into safe mode to get it, booting takes hours (waiting for user profile) and file was in use. Safe mode was fast
Thank you in advance
 

Attachments

Hi,

Could you please check the COMPONENTS hive again with the following tool, this because I've got the ERROR_BADDB message.

Run
61f7aba7309a1-ComponentsScanner_Icon.png
ComponentsScanner again.
  • Right-click ComponentsScanner.exe and select "Run as administrator", click Yes on the UAC (User Account Control) prompt which appears.
  • Follow the on-screen instructions.
  • When the following message appears: "ComponentsScanner has detected the following issues that it is able to repair automatically."
  • Press Y to perform the repair.

    62446b15462b1-ComponentsScanner-ERROR_BADDB.png

  • Once complete, a report will be saved to your desktop called ComponentsScanner.txt.
  • Post the logfile ComponentsScanner.txt as attachment into your next reply.
 
Hi,

Perfect, please perform the following steps:

Step 1. Download
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.
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. Reboot the system and run the following DISM command and post the result.
Code: 
DISM /online /cleanup-image /RestoreHealth


Step 3. Run
61f7aba7309a1-ComponentsScanner_Icon.png
ComponentsScanner again.
  • Right-click ComponentsScanner.exe and select "Run as administrator", click Yes on the UAC (User Account Control) prompt which appears.
  • Follow the on-screen instructions.
  • Once complete, a report will be saved to your desktop called ComponentsScanner.txt.
  • Post the logfile ComponentsScanner.txt as attachment into your next reply.
 

Attachments

Hi,

Please post a new copy of the COMPONENTS hive and the latest CBS logs as well.
 
Attaching new COMPONENTS and CBS.
As an additional note, i am performing this on a clone of the actual server, i should be able to replicate on the production box as well correct?
Additional Information, server is no longer crashing/freezing as often and logins are much faster
 

Attachments

Hi,

Yes, you could start with ComponentsScanner on the productive server to repair the COMPONENTS hive if needed.

Here's the next fix:

Step 1.
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.
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. 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
 

Attachments

When running componentscanner.exe on the production system, i get "failed to parse hive, this could indicate major corruption".
 
jptheripper said:
Should i just work on the production server? I dont want to waste your efforts
Click to expand...
No worries, and thanks for the ComponentsScanner log of the porduction server.

Question: Is this server recently upgraded from 2008 (R2) to 2019?
 
Okay, please post the CBS hive as well to take a look at..

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