Direkt zum Inhalt

After Cloning C, neither original C nor new C can be selected in boot order

Thread needs solution

I followed the instructions to clone my C: drive (Windows 10 Pro installation) to a larger SSD. When done, I turned off the computer, removed the original C: and replaced it with the new C: and then started up into the bios to change the boot order from CD/DVD drive to the new C:. The new C: drive is not available to be selected:

1footinthegrave.com/images/support/boot-priority-no-p1-512ssd.jpg

It is listed under SATA Information, but is not present in Boot Priority. It is possible to boot to it by pressing F8 and selecting it from the list of drives and Windows seems to operate normally (I had to enter license info in one of my programs).

I decided to shut down and remove the new C: and re-install the original C:. This resulted in the same problem:

1footinthegrave.com/images/support/boot-priority-no-p1-128ssd.jpg

In addition to the original C: not being able to be selected, there is 2 other "drives" in the list that I don't understand. However, as before, I can select the original C: in the list on the Boot Menu (F8) and Windows starts.

I am running out of space on the original C:, which is why I cloned it to a 512 GB SSD. How do I make the new C: drive bootable. The Clone Drive procedure in True Image 2017 was supposed to do that automatically - it said it would. And now I can't even boot from the original C:.

Your help will be greatly appreciated.

0 Users found this helpful

Jim, I am not familiar with the UEFI BIOS setting panel that your images show but I was expecting to see an option shown for the Windows Boot Manager rather than just selecting a specific disk drive.

Have you tried going into the Advanced Mode (F7) to what further settings this shows to you?

Your cloned drive and the original drive should both be identical and both of these should be bootable, as shown by the fact that you can boot these drives when you select them in the Boot menu F8 option, so the real issue here is the UEFI BIOS settings.

Jim, I got curious and found a discussion on this issue at Tom's Hardware. There are some good suggestions. Sounds like it is not an uncommon thing.

http://www.tomshardware.com/answers/id-2163637/ssd-show-boot-priority-asus-z97-pro.html

Jim,

You need to press the F7 key to enter the Advanced Bios mode.  After that look for a tab that says Boot.  Click on that tab and look for Boot Order.  You need to look for an entry that says Windows Boot Manager.  Windows Boot Manager needs to be first in the list in order to boot your drive either the new clone or the old drive.

You should be able to click on the first entry in the Boot Order list to expose a dropdown menu from which to select Windows Boot Manager as the first in the list.  If you do not see the Windows Boot Manager in the list then you can look for Installed drives to locate it.  You should be able to click on the Windows Boot Manager enrty there and using key combo Shift and + move the entry up the list.  Move it to the top position there and that in turn will make it show up in the Boot Order list so that you can make it first in that list.

Steve Smith wrote:
Have you tried going into the Advanced Mode (F7) to what further settings this shows to you?

Yes, I tried that and a couple other things. No joy to be had there. But I did find a solution (see below).

BrunoC wrote:
Jim, I got curious and found a discussion on this issue at Tom's Hardware. There are some good suggestions. Sounds like it is not an uncommon thing.

http://www.tomshardware.com/answers/id-2163637/ssd-show-boot-priority-asus-z97-pro.html

Thanks for sharing that. I hope it will help others who may have this problem with a computer using a ASUS Gryphon Z97 motherboard. Unfortunately, I didn't find your post in time. I did find where other people had a similar problem as mine and were directed to download a utility for Windows 10, 64bit that will help repair a system startup drive. It worked for me and I am up and running on the new, larger drive. It might have been easier, if I knew about the Z97 issues, but I guess the search terms I used weren't cutting it. I hope this thread will help others who find themselves in a similar situation though. Thanks for your help.

Jim

Enchanted, looks like we posted replies at the same time. Thanks. Your solution might also have worked, but I did find one that got me back up and running normal. Appreciate you trying to help though.

Jim

Your welcome, glad you got the issue resloved.