[SOLVED] Registration Database is corrupt

Status
Not open for further replies.

Kieran

Member
Joined
Mar 11, 2019
Posts
12
When trying to install drivers for a bluetooth adapter through the Device Manager, I received the message "The configuration registry database is corrupt"
When I try to install windows updates, they fail with the error "Install error - 0x800703f1"

I've run the SFC scan, all the DISM scans, and SFCFix.

Currently it appears that I can't install any drivers, nor can I install any windows updates. So far all scans said they've found no corruption.

Here is my SFCFix log:

Code:
SFCFix version 3.0.1.0 by niemiro.
Start time: 2019-03-11 02:25:32.289
Microsoft Windows 10 Build 17134 - amd64
Not using a script file.




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




Successfully processed all directives.
SFCFix version 3.0.1.0 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2019-03-11 02:27:58.972
----------------------EOF-----------------------

Here is my CBS folder: CBS

Here is my DRIVERS file: DRIVERS

Here is my COMPONENTS file: COMPONENTS


Thank you very much for your time and effort
Kieran
 

Attachments

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

Try updating drivers again and let me know if it works.
 

Attachments

Interesting results. Windows update completed successfully but in the device manager all devices without drivers now show up as "Unknown device," attempting to update / install the drivers fails with the message "Windows could not find drivers for your device." Before this they were named devices and windows was able to find generic drivers for them -- it just failed to install them.
 
Before the device had stopped being recognized, Windows Update had scheduled a driver patch or update of some kind specifically aimed at this ASUS brand of bluetooth adapter. Looking at the windows update history it doesn't seem like it ever got installed.
 
Is it important that I restart after switching out these files? I have been just for safety.
 
For some reason I'm consistently getting DRIVERS being in use by System now, even if I restart and try to swap the file immediately. It didn't happen at all earlier, and I swapped them after the system had been on for a while.
 
Windows just failed to install the 1803 and 1809 feature updates. After downloading the update it did some configuration during shutdown, some more configuration during boot up that required a restart, and on the second boot it said the update failed and it was rolling back changes.
 
Understood. I'm still having trouble replacing the DRIVERS file, it seems like no matter how many times I restart or how quickly I try to swap it it's always in use. I've also tried waiting a little while after the system is started, and closing applications first.
 
Again for clarity it worked without any difficulty for the first swap, I'm not sure what's changed since then.
 
Do this and then try replacing the hive:

Step#1 - FRST Fix
NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system
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. Download attached file and save it to the Desktop.
Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop).
3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
4. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.
 

Attachments

Here are the contents of Fixlog.txt
Code:
Fix result of Farbar Recovery Scan Tool (x64) Version: 11.03.2019
Ran by Kieran (11-03-2019 23:07:57) Run:1
Running from C:\Users\Kieran\Desktop
Loaded Profiles: Kieran (Available Profiles: Kieran & OVRLibraryService & DefaultAppPool)
Boot Mode: Normal
==============================================

fixlist content:
*****************
CreateRestorePoint:
C:\Windows\System32\config\DRIVERS
*****************

Restore point was successfully created.
Could not move "C:\Windows\System32\config\DRIVERS" => Scheduled to move on reboot.

Result of scheduled files to move (Boot Mode: Normal) (Date&Time: 11-03-2019 23:09:06)

C:\Windows\System32\config\DRIVERS => moved successfully

==== End of Fixlog 23:09:06 ====

I've successfully replaced DRIVERS with the new file. When attempting to update the drivers for the bluetooth adapter I now receive this message:

IqbIeqR.png


"Windows found drivers for your device but encountered an error while attempting to install them.

Microsoft Bluetooth LE Enumerator

The system cannot find the file specified."
 
I restarted and the drivers successfully installed. My bluetooth adapter is working correctly again. I'll check to see if Windows Update is able to complete the installation.
 
Windows updated successfully. It even installed the updated ASUS bluetooth driver. It still needs to install feature update 1809, but all devices appear to be working correctly.
 
Windows has fully updated and all my devices seem to be working properly. I think we can call this one solved. Thank you very much for your help!
 
Status
Not open for further replies.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top