DISM Error 1009 – The configuration registry database is corrupt

When you run the DISM ScanHealth or RestoreHealth command, the following error may occur:

Error: 1009

The configuration registry database is corrupt.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

Cause

The error code 1009 (hex: 0x800703F1) means “ERROR_BADDB”. It indicates that a registry hive is corrupt. If this error occurs during DISM ScanHealth or RestoreHealth, the COMPONENTS hive could be the issue.

Resolution

You can fix the COMPONENTS registry hive using the following tool from Sysnative.com.

How to check your COMPONENTS registry hive for corruption | Sysnative Forums

Download ComponentsScanner (64-bit) and run it.

When you see the following message, read it and press any key to continue:



Welcome to ComponentsScanner by Sysnative Forums.

This tool will check your COMPONENTS registry hive for corruption and report the results.
When it is complete, a report will be saved to your desktop. The information contained in the report can then be
used to assist in the repair of the COMPONENTS hive if necessary.
Support for this tool and advice for repairing any corruptions can be found for free at Sysnative Forums (www.sysnative.com).
Please understand that the use of this tool is entirely at your own risk. Sysnative Forums will not be held
responsible for any loss or damage caused as a result of the use or misuse of this program.
If you do not agree to these terms, or if you wish not to continue for any other reason, please exit now.
Otherwise press any key to continue . .

Press any key to continue.

It now offers to repair the hive if it’s corrupt:

ComponentsScanner has detected the following issues that it is able to repair automatically. 
 
        * ERROR_BADDB - sequence numbers are mismatched 
 
Would you like to run the repairs? Your COMPONENTS hive will be backed up before attempting any repairs. [Y/n]

Now, press Y to give your consent to repair the hive. That should do the trick.

Note:

The above tool won’t help if your DRIVERS hive is corrupted. The DRIVERS hive has to be fixed manually.


One small request: If you liked this post, please share this?

One "tiny" share from you would seriously help a lot with the growth of this blog. Some great suggestions:
  • Pin it!
  • Share it to your favorite blog + Facebook, Reddit
  • Tweet it!
So thank you so much for your support. It won't take more than 10 seconds of your time. The share buttons are right below. :)

Ramesh Srinivasan is passionate about Microsoft technologies and he has been a consecutive ten-time recipient of the Microsoft Most Valuable Professional award in the Windows Shell/Desktop Experience category, from 2003 to 2012. He loves to troubleshoot and write about Windows. Ramesh founded Winhelponline.com in 2005.

Leave a Comment