The configuration registry database is corrupt

[svcv]

Hey, so a couple of days ago my graphics card drivers stopped working. Trying to install them again from the control panel result in the error in the title of the thread ("the configuration registry database is corrupt"). If I remember right, sfc/scannow failed because it couldn't access windows resource protection. I am afraid I can't check the exact error message again - when I try to run it now, it says there are system repairs pending requiring reboot to complete. The problem is that all Windows updates and repairs triggered by the reboot fail. I created a system image through windows installation media but the installation process fails every time ("Windows 10 installation has failed").

I attach the C:\Windows\system32\config\DRIVERS file and the CBS log. I'd rather avoid having to do a clean install since I had to put in a lot of work to make all the applications I am using function together, so I'd be very greatful if someone could point me in the right direction.

The CBS file was too large to be attached, so here's a google drive link - CBS.rar

 

[Sysnative Windows Update]

Hello and welcome!

Step 1 - Replace Drivers Hive Manually

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

1. Download DRIVERS.ZIP and save to your desktop.
2. Right-click on it and select Extract all.... Make sure the "Show extracted files when complete" is checked and click Extract.
3. Now we have the DRIVERS file that we will be using to replace your current one.
4. Navigate to C:\Windows\System32\config
5. Right-click on the current DRIVERS file and select rename. Rename it to DRIVERS.bad.
   Note: If you get an error that the file is in use, reboot your computer and then try again.
6. Take the file from the Drivers folder on your desktop and paste it into C:\Windows\System32\config

Afterwards, the driver updates should work again

 

[svcv]

Hi, that fixed if for the drivers, thank you! However, the system still won't update (KB4517389 and KB4524100). Any chance to fix that as well?

 

[Sysnative Windows Update]

Great!

Please do the following:

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 magnifying glass 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 and provide the link to the LogFile.PML file as well as your CBS.log Examples of services to upload to are Dropbox or OneDrive or SendSpace.

 

[svcv]

Thank you, I'll get through this step when I'm back from work :)

 

[Sysnative Windows Update]

Sure!

Will check when I wake up

 

[svcv]

Ok, these are the files, but I wasn't quite sure about the step 3 - usually the failing part is just after reboot, but the instructions don't make a mention of using the "boot logging" option. So I attach two files, one is simply me following instructions and attempting to update through the windows update service (after which the system asks me to reboot) and that's where process monitoring ends, and in the other I used the "boot logging" option after the windows update service tells me to reboot to install the update.

CBS.rar
Logfile.PML
Bootlog.pml

 

[Sysnative Windows Update]

Ah, in that case I need C:\Windows\Inf\setupapi.dev.log as well.

 

[svcv]

Hmmm, I am throwing in the other setupapi.dev.log in as well just in case (the one with the date in the file name, second link)

setupapi.dev.rar
setupapi.dev.20191014_130637.rar

 

[Sysnative Windows Update]

Step#1 - FRST Scan

1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
2. Right-click FRST64.exe and click Run as Administrator to run it as administrator. When the tool opens, click Yes to disclaimer.
3. Please ensure you place a check mark in the Addition.txt check box at the bottom of the form before running (if not already checked).
4. Press Scan button.
5. It will produce a log called FRST.txt in the same directory the tool is run from (which should now be the desktop)
6. Please attach the log back here.
7. Another log (Addition.txt - also located in the same directory as FRST64.exe) will be generated Please also attach that along with the FRST.txt in your reply.