Thanks for the reply.
>But is it possible to install the tool on another PC, connect my disk to that PC, and still do what you suggested?
Yes, absolutely. Use the SATA convertor, and select the faulty disk and scan.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
So what is going on right now is I have 3 hard disks having different issues but I would be focusing on one. The first disk has Windows 10 installed on it but sadly it always unexpectedly shows BSOD containing some different error messages (FAULTY HARDWARE..., MEMORY MANAGEMENT, and so on) when I'm working or just doing simple operations on my PC, (watching videos, typing, and so on). The truth is the error still appears when I'm actually not doing anything with my PC and then my PC restarts. The second disk has Windows 7 installed but it boots up and never leaves the Windows logo (stuck). And lastly, the third disk (which is the one I actually do care about), the one that has the BSOD "Inaccessible Boot Disk" error.
Now it's an old hard disk that was kept unused for long. So when I put it into my PC and boot it up, it boots normally, goes to the Windows logo, after it loads I get the BSOD error. So yeah that's the problem. I found a temporary fix for it using the command prompt in recovery mode. What I did was I navigated to C:\Windows\System32\config\RegBack, copied the contents in that directory and pasted it here C:\Windows\System32\config. I, first of all, made a backup of these particular files found in \config dir: DEFAULT, SAM, SECURITY, SOFTWARE and SYSTEM, by simply renaming them and then going to \RegBack dir copying the exact same files there and pasting them in \config dir. This is the sequence in which I executed the commands:
"d:" (my c drive)
"cd windows/system32/config"
"dir"
"cd regback"
"dir"
cd..
"ren DEFAULT DEFAULT1"
"ren SAM SAM1"
"ren SECURITY SECURITY1"
"ren SOFTWARE SOFTWARE1"
"ren SYSTEM SYSTEM1"
"cd regback"
"dir"
"copy *.* .."
"cd.."
"dir"
"exit"
After that, I restarted my pc, it booted up, the Windows logo loading screen came on, it loaded for some seconds and "Getting PC Ready" was seen after. Then boom it worked. I could see a blue screen, but this one was different, It was lighter than the former having these white dots going in circles (let me just say it wasn't BSOD). It was good having to see my old lock screen wallpaper giving me a warm welcome. I put in my password and yeah I could see my desktop looking right back at me once again, with my apps and so many mouth-watering documents, but like the saying goes "if you pray for the rain, get ready to deal with the mud" (I guess), I found some issues. The volume icon and network icon at the system tray area had the x sign on them, meaning they were disabled. I went to Device Manager and found out that my sound driver, graphic driver, and many other essential drivers were uninstalled and had to be installed manually (sad). I was prompted to restart each time I installed a driver. Some minutes later I was done installing most of them and then I restarted my PC with a smile on my face, which would soon be wiped off in a couple of seconds. Yeah, my pc booted normally and then after the Widows logo loading screen, I was met with the same BSOD error again! (very sad). I asked my PC why it would betray me like this but I got no response. So I went to recovery mode and ran that same commands in cmd prompt which works but once I restart my PC it goes back to the BOSD error. I can keep running those commands in command prompt but it would give me a temporary fix, Each time I restart my system it goes back to the error. So how can I get a permanent fix? Do I need a Windows media creation tool to fix this? And how can I fix this using the tool?
PC Spec:
Dell Inspirion 1545
Pentium(R) Dual-Core CPU T4300 2.10GHz (2CPUs), ~2.1GHz
Windows 10 Pro 64-bit (10.0, Build 10240)
4096MB RAM
Intel Family Chipset
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Thanks for the reply.
>But is it possible to install the tool on another PC, connect my disk to that PC, and still do what you suggested?
Yes, absolutely. Use the SATA convertor, and select the faulty disk and scan.
Pretty sure that windows 7 is a legacy boot OS. Windows 10 accepts UEFI and legacy boot. You Most likely have a incorrect boot setup in the bios. Maybe you have the incrrocet boot order or incrrocet boot method. Since you can get into recovery mode and run cmd you can try to manually check the boot set up with bcdedit.exe. I would suggest to unplug the other HDD disks temporarily to see if windows 10 will magically boot ok. It's Windows You never know haha 🐈
Media creation tool is meant to be run on a well working computer as it kinda copies the existing files/ uses the existing files.
A permanent fix would to manually edit the the boot configuration.
Thanks for the reply CatteryDeveloper. How can I go about the boot configuration plz?
Thanks for the reply Sumit. It's not actually possible to install any app. Any device I try to connect to the PC won't be recognized or it won't even be detected. I can't access the Internet too. Well, those were when I could get to the welcome screen. Now the worst has happened. The commands I ran before to temporarily get access to the welcome screen isn't working anymore. All I see is Inaccessible Boot Disk.
Gosh Windows can be so stubborn.
I have a SATA to USB converter in case I want to access my files on the disk using another PC.
I was thinking of downloading the HDTune tool you suggested on another PC and then connecting my hard disk using the SATA converter to that PC, and then copying the tool to the disk, and next I insert the disk back into my main PC, run the commands, get to welcome screen and to my desktop and then try to install the tool, but all these would be futile because, as I said, the commands won't work and I can't get to the welcome screen.
But is it possible to install the tool on another PC and connect my disk to that PC and still do what you suggested?
Pretty sure that windows 7 is a legacy boot OS. Windows 10 accepts UEFI and legacy boot. You Most likely have a incorrect boot setup in the bios. Maybe you have the incrrocet boot order or incrrocet boot method. Since you can get into recovery mode and run cmd you can try to manually check the boot set up with bcdedit.exe. I would suggest to unplug the other HDD disks temporarily to see if windows 10 will magically boot ok. It's Windows You never know haha 🐈
Media creation tool is meant to be run on a well working computer as it kinda copies the existing files/ uses the existing files.
A permanent fix would to manually edit the the boot configuration.
Hi Daniel,
I'm Sumit, here to answer your query at the Microsoft Community.
This looks so much like a failed disk. When your system runs, do the following:
Please download and run HDTune Trial or HD Tune Free.
Select the Disk where OS is installed.
Make screenshots of the following
the health.
the error scan.
the benchmark.
Post back the screenshots.
Also post the results of CHKDSK command:
How to do a Disk check of System drive in Windows 10 and interpret the logs
https://www.yourwindowsguide.com/2018/04/how-to...
Disclaimer:
There are links to non-Microsoft websites which would provide accurate and safe information. Watch out for ads on the websites which are frequently classified as a PUP (Potentially Unwanted Products). There is no need to buy paid products to fix your computers as they do more harm than good sometimes.