4 Operator

 • 

4.3K Posts

May 2nd, 2017 12:00

I agree, the fact you changed the drive needs to be followed up with the procedure used.  Did you reinstall Windows, what type of drive and even why did you change the drive..

9 Legend

 • 

87.5K Posts

May 2nd, 2017 12:00

Did you install the operating system on the drive (the new drive, unless it was a warranty replacement, is blank)?

May 2nd, 2017 17:00

I changed it because the old hard drive was giving me the same error message

May 2nd, 2017 17:00

it was a blank hard drive and I accidentally  threw the other one away.

4 Operator

 • 

4.3K Posts

May 2nd, 2017 22:00

I have seen many posts, in different forums, about no boot device found.  Other such messages are "BCD data is corrupted" and cannot boot.  

I don't know the reasons for these and there may be several different reasons.  But when you boot on newer systems, the firmware directs the system to a boot drive which contains the Boot file.  That starts Windows.  If the firmware cannot find a drive with the correct configuration, you may see that message.

So the first thing to do is to make sure your boot drive is identified correctly in the Bios.  For a UEFI system, that would require the Windows Boot Manager being the priority boot device.  For a Legacy system, the drive itself would be the correct device.

If you boot your system and use F12 to get a Boot Device Menu, do you show the correct device, and if selected, will it boot.

If that doesn't repair the problem, for some reason the system cannot see the drive.  This can happen in at least one case if the drive is a PCIe drive and the Bios does not contain a driver for it.  But as far as I know, there is not a consensus on what is happening in these cases.  Other devices may be involved such as external drives or even SD cards.

No Events found!

Top