[SOLVED] Configuration Registry Database Corrupt!

D

Davii

Member
Joined
May 5, 2018
Posts
12
Hey guys. So yesterday I was trying to install an MTK driver for my phone so that i could load a custom recovery and "flash" it. The driver installation, of course, failed with the error message -the configuration registry database is corrupt-. Thinking that it was an issue with the driver and tried a different MTK driver, it also failed, then I tried a Realtek driver, a Nvidia driver and a Qualcomm driver, all failing with the same error.

So, I started searching, one forum said to try sfc/scannow.

That got to 28% then failed because it couldn't access windows resource protection. So, again i did some research and turns out it is controlled by trustedinstaller. I manually turned trustedinstaller service on, but sfc/scannow still failed, again at 28% in the verification step.

So, I tried DISM that "failed". And I placed failed in quotes because it returned Error 87, which google says, means that there is nothing to clean.

Doing more research about this registry error I happened on this forum, specifically this page: Configuration registry database corrupt , where a member had the same issue as myself, however, he got it solved.

So today I tried the one method the forum member above tried which I didn't, which was using SFCFix.exe. It didn't fail, it outright crashed.

So am asking is there anyway, I can get help with this problem, what log files do I need to upload
Thanks in advance.

System Specs:
Lenovo Ideapad Z500
Windows 10 Enterprise (Admin account)
8GB RAM
1 GB VRAM
Intel i5-3210M 2.50Ghz Dual Core
 

Attachments

Last edited:
Hello and welcome!

Please zip and attach the following file: C:\Windows\system32\config\DRIVERS.

Copy the file to your Desktop before zipping the it. If you get the message that the file is in use, please reboot and try again.
 
The above file is incorrect. That one is C:\Windows\system32\drivers.

Here is the correct file:
 

Attachments

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



Step 2 - DISM /RestoreHealth Scan



  1. Right-click on the Start button and select Command Prompt (Admin)
  2. When command prompt opens, Copy (Ctrl+C) and Paste (Right-click > Paste) the following command into it, then press Enter

    Dism /Online /Cleanup-Image /RestoreHealth
  3. When DISM finishes scanning your component store, zip up and attach your CBS log to your next post:

    C:\Windows\Logs\CBS\CBS.log
 
Ok. I did everything in step 1. Trying Step 2, DISM returned Error 87, "the cleanup-Image option is unknown"


Screenshot_126.png


Here is the cbs file:
 

Attachments

SFCFix Script

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 SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
  5. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.




SFC Scan


  1. Click on the Start button and in the search box, type Command Prompt
  2. When you see Command Prompt on the list, right-click on it and select Run as administrator
  3. When command prompt opens, copy and paste the following commands into it, press enter after each

    sfc /scannow

    Wait for this to finish before you continue

    copy %windir%\logs\cbs\cbs.log %userprofile%\Desktop\cbs.txt
  4. This will create a file, cbs.txt on your Desktop. Please attach this to your next post.
 

Attachments

Here's the SFCFx.txt:

Code: 
SFCFix version 3.0.0.0 by niemiro.
Start time: 2018-05-06 16:30:31.094
Microsoft Windows 10 Build 16299 - amd64
Using .zip script file at C:\Users\Davian\Documents\Phone Flash stuff\SFCFix.zip [0]








PowerCopy::
Successfully took permissions for file or folder C:\WINDOWS\winsxs\amd64_microsoft-windows-ie-ieproxy_31bf3856ad364e35_11.0.16299.15_none_e70c8b2a268eed66\ieproxy.dll
Successfully took permissions for file or folder C:\WINDOWS\winsxs\amd64_microsoft-windows-ie-behaviors_31bf3856ad364e35_11.0.16299.15_none_93a12b79ce0c2b49
Successfully took permissions for file or folder C:\WINDOWS\winsxs\amd64_microsoft-windows-d..t-winproviders-appx_31bf3856ad364e35_10.0.16299.15_none_6aa168fc1d1ae4eb\AppxProvider.dll
Successfully took permissions for file or folder C:\WINDOWS\winsxs\amd64_microsoft-windows-d..-japanese-utilities_31bf3856ad364e35_10.0.16299.15_none_101d6ad7e33f1ce6
Successfully took permissions for file or folder C:\WINDOWS\winsxs\amd64_microsoft-windows-appxsip_31bf3856ad364e35_10.0.16299.15_none_ec5153a1e72a5947
Successfully took permissions for file or folder C:\WINDOWS\winsxs\amd64_microsoft-hyper-v-management-clients_31bf3856ad364e35_10.0.16299.15_none_1577ec7ff0f40e84\Hyper-V Manager.lnk


The file \\?\C:\WINDOWS\winsxs\amd64_microsoft-windows-ie-ieproxy_31bf3856ad364e35_11.0.16299.15_none_e70c8b2a268eed66\ieproxy.dll is in use and must be replaced over a reboot.
Failed to copy file C:\Users\Davian\AppData\Local\niemiro\Archive\winsxs\amd64_microsoft-windows-ie-behaviors_31bf3856ad364e35_11.0.16299.15_none_93a12b79ce0c2b49\iepeers.dll to C:\WINDOWS\winsxs\amd64_microsoft-windows-ie-behaviors_31bf3856ad364e35_11.0.16299.15_none_93a12b79ce0c2b49\iepeers.dll with error code ERROR_ACCESS_DENIED.
Successfully copied file C:\Users\Davian\AppData\Local\niemiro\Archive\winsxs\amd64_microsoft-windows-d..t-winproviders-appx_31bf3856ad364e35_10.0.16299.15_none_6aa168fc1d1ae4eb\AppxProvider.dll to C:\WINDOWS\winsxs\amd64_microsoft-windows-d..t-winproviders-appx_31bf3856ad364e35_10.0.16299.15_none_6aa168fc1d1ae4eb\AppxProvider.dll.
Failed to copy file C:\Users\Davian\AppData\Local\niemiro\Archive\winsxs\amd64_microsoft-windows-d..-japanese-utilities_31bf3856ad364e35_10.0.16299.15_none_101d6ad7e33f1ce6\IMJPUEX.EXE to C:\WINDOWS\winsxs\amd64_microsoft-windows-d..-japanese-utilities_31bf3856ad364e35_10.0.16299.15_none_101d6ad7e33f1ce6\IMJPUEX.EXE with error code ERROR_ACCESS_DENIED.
Failed to copy file C:\Users\Davian\AppData\Local\niemiro\Archive\winsxs\amd64_microsoft-windows-appxsip_31bf3856ad364e35_10.0.16299.15_none_ec5153a1e72a5947\AppxSip.dll to C:\WINDOWS\winsxs\amd64_microsoft-windows-appxsip_31bf3856ad364e35_10.0.16299.15_none_ec5153a1e72a5947\AppxSip.dll with error code ERROR_ACCESS_DENIED.
Successfully copied file C:\Users\Davian\AppData\Local\niemiro\Archive\winsxs\amd64_microsoft-hyper-v-management-clients_31bf3856ad364e35_10.0.16299.15_none_1577ec7ff0f40e84\Hyper-V Manager.lnk to C:\WINDOWS\winsxs\amd64_microsoft-hyper-v-management-clients_31bf3856ad364e35_10.0.16299.15_none_1577ec7ff0f40e84\Hyper-V Manager.lnk.


Successfully pended file for replace over reboot: \\?\C:\WINDOWS\winsxs\amd64_microsoft-windows-ie-ieproxy_31bf3856ad364e35_11.0.16299.15_none_e70c8b2a268eed66\ieproxy.dll


Successfully restored ownership for C:\WINDOWS\winsxs\amd64_microsoft-windows-ie-behaviors_31bf3856ad364e35_11.0.16299.15_none_93a12b79ce0c2b49
Successfully restored permissions on C:\WINDOWS\winsxs\amd64_microsoft-windows-ie-behaviors_31bf3856ad364e35_11.0.16299.15_none_93a12b79ce0c2b49
Successfully restored ownership for C:\WINDOWS\winsxs\amd64_microsoft-windows-d..t-winproviders-appx_31bf3856ad364e35_10.0.16299.15_none_6aa168fc1d1ae4eb\AppxProvider.dll
Successfully restored permissions on C:\WINDOWS\winsxs\amd64_microsoft-windows-d..t-winproviders-appx_31bf3856ad364e35_10.0.16299.15_none_6aa168fc1d1ae4eb\AppxProvider.dll
Successfully restored ownership for C:\WINDOWS\winsxs\amd64_microsoft-windows-d..-japanese-utilities_31bf3856ad364e35_10.0.16299.15_none_101d6ad7e33f1ce6
Successfully restored permissions on C:\WINDOWS\winsxs\amd64_microsoft-windows-d..-japanese-utilities_31bf3856ad364e35_10.0.16299.15_none_101d6ad7e33f1ce6
Successfully restored ownership for C:\WINDOWS\winsxs\amd64_microsoft-windows-appxsip_31bf3856ad364e35_10.0.16299.15_none_ec5153a1e72a5947
Successfully restored permissions on C:\WINDOWS\winsxs\amd64_microsoft-windows-appxsip_31bf3856ad364e35_10.0.16299.15_none_ec5153a1e72a5947
Successfully restored ownership for C:\WINDOWS\winsxs\amd64_microsoft-hyper-v-management-clients_31bf3856ad364e35_10.0.16299.15_none_1577ec7ff0f40e84\Hyper-V Manager.lnk
Successfully restored permissions on C:\WINDOWS\winsxs\amd64_microsoft-hyper-v-management-clients_31bf3856ad364e35_10.0.16299.15_none_1577ec7ff0f40e84\Hyper-V Manager.lnk
PowerCopy:: directive failed to complete successfully.








Reboot:: directive completed successfully.








PostRebootCorruptionDetection::
No hash verification failures detected.
PostRebootCorruptionDetection:: directive completed successfully.








PostRebootRestorePermissions::
Successfully restored ownership for C:\WINDOWS\winsxs\amd64_microsoft-windows-ie-ieproxy_31bf3856ad364e35_11.0.16299.15_none_e70c8b2a268eed66\ieproxy.dll
Successfully restored permissions on C:\WINDOWS\winsxs\amd64_microsoft-windows-ie-ieproxy_31bf3856ad364e35_11.0.16299.15_none_e70c8b2a268eed66\ieproxy.dll
PostRebootRestorePermissions:: directive completed successfully.








Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 6 datablocks.
Finish time: 2018-05-06 16:49:46.467
----------------------EOF-----------------------


sfc /scannow failed again at 12%

And here's the CBS.txt:

cbs.txt - Google Drive
 
Hey so i ran the SFCFix with the zip file you gave me
This is the output:
Code: 
SFCFix version 3.0.0.0 by niemiro.
Start time: 2018-05-06 23:22:18.212
Microsoft Windows 10 Build 16299 - amd64
Using .zip script file at C:\Users\Davian\Documents\Phone Flash stuff\SFCFix.zip [0]








PowerCopy::
Successfully took permissions for file or folder C:\WINDOWS\winsxs\amd64_microsoft-windows-c..sktop.appxmain.root_31bf3856ad364e35_10.0.16299.15_none_fdfd375a1fa340ac


Failed to read file attributes for file C:\WINDOWS\winsxs\amd64_microsoft-windows-c..sktop.appxmain.root_31bf3856ad364e35_10.0.16299.15_none_fdfd375a1fa340ac\SAPIBackgroundTask.dll.
Failed to copy file C:\Users\Davian\AppData\Local\niemiro\Archive\winsxs\amd64_microsoft-windows-c..sktop.appxmain.root_31bf3856ad364e35_10.0.16299.15_none_fdfd375a1fa340ac\SAPIBackgroundTask.dll to C:\WINDOWS\winsxs\amd64_microsoft-windows-c..sktop.appxmain.root_31bf3856ad364e35_10.0.16299.15_none_fdfd375a1fa340ac\SAPIBackgroundTask.dll with error code 0x570.


Successfully restored ownership for C:\WINDOWS\winsxs\amd64_microsoft-windows-c..sktop.appxmain.root_31bf3856ad364e35_10.0.16299.15_none_fdfd375a1fa340ac
Successfully restored permissions on C:\WINDOWS\winsxs\amd64_microsoft-windows-c..sktop.appxmain.root_31bf3856ad364e35_10.0.16299.15_none_fdfd375a1fa340ac
PowerCopy:: directive failed to complete successfully.








Failed to process all directives successfully.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 7 datablocks.
Finish time: 2018-05-06 23:22:19.784
Script hash: Dr5EeCw1g23NFKi7KSuR25ICvCov/maq1eFXLqgUiFQ=
----------------------EOF-----------------------

i restarted then ran sfc /scanow.

On a side note: I'm now able to install drivers again.
 

Attachments

Well i was planning on doing that a few months from now with i buy a new hard drive.
 
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