Restore drivers from repair disk cmd
I've fixed my "inaccessible boot disk" BSOD error. With constant research everyone else with this problem seemed to have given up and just did a fresh reinstall. I had a slight different approach and in the end it solved my problem.
I tried backing up my drivers and that was a fail. I also tried dism restore heatlh from the recovery cmd and that was a bust. Here is the code for that (make sure that your windows drive is C or whatever, I changed it using diskpart) (also can't do dism online since your not in windows and this is before booting)
dism /image:c:\ /cleanup-image /restorehealth
I then tried to restore my registry and that was a bust because my backups were empty (0 kbs files). So I had to do a fresh install. I did a fresh installed and installed macrium reflect. I still had the backup iamges of my original install and I used macrium's refelct viboot to virtually fix the image and try more options. What eventually I did was copy the *SYSTEM* registry hive/file from the "Fresh install of windows" over my corrupted image of windows.. and with success it worked.
How I did that was copy it from the fresh install which I believe I had to do from command prompt in recovery because windows gives you access errors if you try to do that from boot. Copied it from fresh install to a usb drive. I then copied it from the usb driver over the corrupted image and it worked. Then tried it for real instead of virtually and it still works. I've been up and running for a week now. Creating backups of everything including the working registry and pretty much everything. I've now becomed a back up freak... even though I was so frustrated because this whole process should've never happened because I had backups already but somehow they got corrupted too? Not sure...
Here is the code for the copy I did. It's something like this. Where drive e was my usb (regbackup was the folder). And drive c is my windows drive. Copy from place "A" to place "B"
xcopy e:\regbackup c:\windows\system32\config
I might've done a bad explanation and it was a quick one. This took two days of debugging and trying stuff. I don't even remember the command I did to try and restore my drivers but that didn't work anyway since I found out it was a registry problem and nothing else.
I hope my bad explanation can help others. I always hate when people solve a problem and never post how they solved it and leave the forum discussion blank.
Cheers!
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now