Windows 10: After Cloning, orig. C & new C can't be selected in boot order

I followed Acronis True Image 2017 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:

Click to see full-size.




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:

Click to see full-size.




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.

:)

 

Strange "C Missing" in Restore window

I did a test this morning. I cloned my C drive using Acronis 2017 booted from rescue media and cloned to a like SSD.

I then removed the source SSD and inserted the cloned SSD and booted the system.

I then checked the system restore window and now I have 2 "C Missing" entries.

I don't ever remember doing a system restore. In fact the last time I tried one it failed saying unable to complete system restore.

I also check to make sure system protection is turned on for the C drive after every MS update as on any major update always turns it off.

Will attempt further testing this weekend if time permits by turning off protection for every instance of C Missing and then cloning that SSD to a new SSD to see if the C Missing returns.

Will also await any further assistance from this forum.

 

Drive error detected

ok, I have 2 drives in my system. A C drive (OS) and a E drive (data only drive).

I do not clone the C drive to the E drive.

I clone the C drive to completely different (third) SSD using Macrium Reflect.

I boot from the cloned C drive (not E) and errors are reported on the E drive.

I put the original C drive back in and boot - No errors on the E drive.

There are three drives involved.

Original C, E data drive, and a third SSD that is the cloned C drive.

I disconnect the original C and boot from the third drive (the cloned C).

Immediately get drive errors on E.

Remove cloned C drive and reinsert original C and boot.

No errors detected.

The alert message does not specify which drive has the errors, but experience with this

issue is that the E drive is the drive reporting errors.

 

How many partitions did you clone? There is typically an EFI System partition, formatted as FAT32 that must also be cloned.

Also I would make a bootable USB flash drive or DVD of Kyhi's recovery tools:
Windows 10 Recovery Tools - Bootable Rescue Disk - - Windows 10 Forums

Boot the computer from it, run Macrium Reflect. Under the restore menu is a utility to Fix Windows boot problems. That utility is usually able to fix it - as long as the EFI system partition is already there, it will repair it.

If you can boot into a command prompt, there are ways of fixing it with diskpart and bcdboot commands, but Macrium Reflect will do it for you.

 

Thank you so much, NavyLCDR. I downloaded that (huge) file and Rufus to burn it onto a thumb drive. Pretty simple, although I did sorta feel like I had broke into someone's house and was using their computer *Eek - a Windows desktop that didn't look anything like my own. It all took a few minutes (downloading the ISO file took a while because it's 1.2 GB). It asked me if I wanted to restart the computer, I said yes, but it didn't restart. I had to click Start > Restart to do it. I booted into the bios and there was my C: drive among the boot choices. I put it on top, saved, exited and the machine booted into Windows from my new SSD.

I noticed that a System Reserved F: drive was listed in This PC. I don't believe that partition should be messed with, so I removed the drive letter in Disk Manager. The machine restarted fine. I rebooted the computer several more times to be sure everything was as it should be. That partition is still there, but it's hidden now from the file manager. It also frees up that drive letter, if I choose to use it for something else.

This experience really soured me on Acronis True Image 2017. It cloned the drive well enough, but it failed to make it bootable and caused me hours of headache. Thank you very much for making that headache go away.

 

Glad it worked out for you! It's not entirely Acronis being bad - most cloned drives that I have experienced need the boot repair done - but Macrium Reflect has both the cloning utility and the Fix Windows boot utility so it's the only program you need. Lots of members here have ditched Acronis and switched to Macrium for their backup images.

 

It turns out that my motherboard/bios may be the culprit... mea culpa to Acronis for blaming the software. There was actually a solution I didn't find until too late (not a bad too-late, since my problem was fixed) that other Gryphon Z97 users discovered. So, I was destined to find joy at some point.

True to form though, after feeling confident enough to put the box back together, which entailed trying to stuff a full-size HDD into an enclosure with two SSDs in there already and doing a little wire management, I booted up before putting the side of the case back on and... NOTHING. The C: drive wasn't even seen, for some reason.

Well, for some reason for sure - a me reason. My fat, wrinkled fingers managed to pull the SATA cable part way out of the C: drive while doing my cleanup. I didn't notice it because of the wide power cable wrapped over the top of it. One of those *Smile