Salta al contenuto principale

Cloned drive not present on Windows "Restart"

Thread needs solution

Hi,

Windows 7 Pro 64 bit, successfully (more or less) cloned my HP laptop internal HDD to Adata SSD on external USB with ATI2013 boot CD and using manual settings. Installed SSD in laptop, removed CD, no USB drive attached, Windows boots and runs fine. I can do a Windows "Shutdown" ok then boot again by pressing power button and it works as it should. Problem is whenever I do a Windows "Restart" I get a BIOS message saying no boot device present. I then abort the process and power off and on again and Windows boots ok. I've repeated the cloning process (wanted to adjust the size of one partition anyway) and the problem persists. Have done CHKDSK on all partitions.

I did at an earlier stage have various problems attempting to clone the drive from Windows, before arriving at the more recommended method above. I suspect something left over from those failures is causing this issue. Suggestions where to look and how to fix?

Thanks.

0 Users found this helpful

This might not be a clone problem at all. But just to cover bases, try this.

With the target drive installed in the desired final location, use the bootCD to clone the source drive to the target.

Btw, is there more than one drive in your system and did you remove the source drive after you made the clone and BEFORE you tried to boot again? If not then you might need both drives to boot with--windows might have marked one as system and one as boot drive.

Always a good idea to make a full backup too. :)

Single drive in a laptop. I had tried cloning in the direction you say but it was unsuccessful... can't recall why exactly but I think it needed a restart and it hung at that point, perhaps because I didn't remove one of the drives as you say (don't recall Acronis asking me to do so).

It's annoying me that only one "little" thing appears to be wrong, a flag somewhere saying don't boot from this drive on next restart... the kind of trick Acronis seems to use during some cloning processes, but in this case not restored to normal.

It's a windows thing not an ati thing. ati covers it in the instructions in the manual and flags it in the program steps. Cloning has other risks, which is why most of us urge backing up and restoring over cloning, regardless of what package you use.