[SOLVED] Error 1009. Configuration registry database is corrupt. Server 2019

[maxeh7]

Hi.

Looks like there is corruption due to failed updates (I think).

DISM /restorehealth fails with:

Deployment Image Servicing and Management tool
Version: 10.0.17763.1697

Image Version: 10.0.17763.2686

[== 4.5% ]
Error: 1009

The configuration registry database is corrupt.


SFCFix output below:


SFCFix version 3.0.2.1 by niemiro.
Start time: 2023-08-10 08:29:38.214
Microsoft Windows Server 10 Build 17763 - amd64
Not using a script file.

AutoAnalysis::
WARNING: Failed to check store directories with return code 1 and error code ERROR_FILE_NOT_FOUND. COMPONENTS hive may be corrupt.

WARNING: Components hive failed load test and may be corrupt.

WARNING: Components hive failed final reload test with error code ERROR_BADDB and may be corrupt.

SUMMARY: No corruptions were detected.
AutoAnalysis:: directive completed successfully.

Successfully processed all directives.

Failed to process registry database in location 1.
Failed to load registry hive C:\Windows\System32\config\COMPONENTS into key HKEY_LOCAL_MACHINE\COMPONENTS with error code ERROR_BADDB.

Failed to process registry database in location 2 with error code ERROR_FILE_NOT_FOUND.
WARNING: Failed to process registry database in location 3 with error code ERROR_INVALID_HANDLE.
Failed to process registry database in location 4 with error code ERROR_INVALID_HANDLE.
Failed to process registry database in location 4 with error code ERROR_FILE_NOT_FOUND.
Failed to process registry database in location 4 with error code ERROR_FILE_NOT_FOUND.
Failed to process registry database in location 4 with error code ERROR_FILE_NOT_FOUND.

SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2023-08-10 08:54:38.113
----------------------EOF-----------------------


Appreciate any help..

Thanks

 

[maxeh7]

Apologies, I omitted the diag files (attached).

The basic problem is that updates have stopped working with error 0x800703f1. SFC/DISM indicate corruption of the component store - Unfortunately this wasn't noticed until backups of the OS drive have fallen out of retention.

Thanks

 

[maxeh7]

The issue is now resolved.

From going through the output from the tools I believe the fix was performed by ComponentsScanner:

==== Repairs Attempted ====
Repair Type: ERROR_BADDB
* Pre Repair Stage: Nothing to do
* Repair Stage: Successfully updated primary and secondary sequence numbers to 79253
* Post Repair Stage: Hive successfully loaded in Regedit without error


After collecting the diags I ran Windows Update again and it worked, after this I was able to run DISM and this was also successful.


Thanks for providing this resource and tools!