A corrupt COMPONENTS hive with an ERROR_BADDB issue can be fixed with ComponentsScanner.
For other hive files we use another tool to repair the primary and secondary sequence numbers.
Step 1.Replace Components 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.
Download COMPONENTS.ZIP and save to your desktop.
Right-click on it and select Extract all.... Make sure the "Show extracted files when complete" is checked and click Extract.
Now we have the COMPONENTS file that we will be using to replace your current one.
Navigate to C:\Windows\System32\config
Right-click on the current COMPONENTS file and select rename. Rename it to COMPONENTS.bad. Note: If you get an error that the file is in use, reboot your computer and then try again.
Take the file from the Components folder on your desktop and paste it into C:\Windows\System32\config
Step 2Replace 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.
Download DRIVERS.ZIP and save to your desktop.
Right-click on it and select Extract all.... Make sure the "Show extracted files when complete" is checked and click Extract.
Now we have the DRIVERS file that we will be using to replace your current one.
Navigate to C:\Windows\System32\config
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.
Take the file from the Drivers folder on your desktop and paste it into C:\Windows\System32\config
No ComponentsScanner is not compatible to run on Insider Preview Builds, but when you drag and drop the corrupted hive into the executable the tool is able te resolve the ERROR_BADDB issue.
Which error do you get when you try to replace the hives into %windir%\System32\Config
my apologies, it said system file was in use, i ended up booting into a windows 11 usb, used command prompt to xcopy the two hive files directly to the config directory. it worked and now i can install drivers and everything seems fixed.
so how are drivers hives fixed, /what is the tool doing to it the curiousity is getting the best of me.