Windows 10 Inaccessible Boot Device
Windows 10 PC, boots to BSOD Inaccessible Boot Device. Have cloned drive (In an attempt to repair) to new 1TB and ran SFC and CHKDSK. Also removed any Sessions Pending from registry. Note: No updates were Install pending. Intel Pentium G860 CPU. No BIOS updated had been performed to any ones knowledge. I have no history with this client machine, so that is everything I know so far. I have been booting to USB install media to run repairs. No Restore points exist on the PC.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I think your original drive was damaged .
ASKER
bootrec /rebuild shows [1] E:\Windows
but returns "The requested system device cannot be found"
but returns "The requested system device cannot be found"
ASKER
John, I agree the drive was likely the cause. Was hopeful, since the clone went through without any unreadable sectors. Any other ideas?
Cloning a bad drive normally does not work.
Try a disk test on the original drive. You may need a disk recovery service if you have important data on it.
Try a disk test on the original drive. You may need a disk recovery service if you have important data on it.
Your symptom suggested a ransomware attack of the old harddisk and all bootloader files are gone.
You need a fresh install of the OS.
You need a fresh install of the OS.
ASKER
Virus scan is still running (Norton Security), but it has found 6 virus infections so far. I am checking with client to see if they had an active license for antivirus.
is the correct drive on top in the bios boot priority?
ASKER
Yes, the boot priority was fine. Viruses were all contained in unopened e-mails (Trash). Was unable to repair using bootrec. Computer was high priority and had to reset OS and reinstall all software.
ASKER
Some good ideas were presented, but unfortunately a solution was not found. The time line was short, and reset of the OS had to be used. The new HDD and OS are working great so far. Time will tell if something greater was the problem.
Thanks to both contributors.
Thanks to both contributors.
Thank you for the update
ASKER
The original drive I suspected from beginning was the cause, and that is why I cloned it. I am currently running a virus scan on the original drive while working on the installed clone. SFC, CHKDSK, and DISM all successfully run on new drive, but no luck yet.