• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Cloned HDD to SSD but Win 7 won't startup

oslama

Diamond Member
I used EaseUS partition manager to format the SSD and cloned using Macrium Reflect free. The file structure and size are identical on HD and SSD however Window 7 does not fully start. System boots to Windows logo with animation and immediately reboots to prompt windows did not start previously please select repair mode and or launch normally (which again causes boot loop).

There is a 100MB boot partition, which was not there before, is showing in Windows Explorer, not sure which drive it was created on.

OS: Win 7 Ulitmate 64-bit
HD: Seagate 500GB w/ prefetch, indexing, search, page & hibernation files removed / disabled
SSD: CrucialM550 512GB
boot option: MBR with NTFS file system

Do i need to fix MBR on SSD?

Is there a non windows cloning utility that i can use?
 
Last edited:
The 100MB is a recovery partition. It also exists on your original disk and you can see it using Computer Management > Disk Management. It looks like the migrating software assigned a drive letter to it since you can see it in Windows Explorer. But since you cannot boot, how do you see it?

Check that your SSD is also MBR.

The easier thing to do is to try and clone the disk again. Or maybe using the repair option on the OS installation disk.

Come to think of it, if there is a C: drive letter assigned to the recovery partition, and the MBR boot sequence points to C: it will sure not boot.
 
It sounds as if your booting normal off the 100MB boot partition which must be on the ssd for alignment.
I would remove the sata and power cables to be sure that your disabled Seagate 500GB is not the problem.
Go into the bios to check that the ssd is your first boot drive.
 
Last edited:
Crucial does not provide migrating softwre.

Every enthusiast should acquire useful tools.

Both Acronis Disk Director Home 11 and Acronis True-Image 2014 provide cloning capability that assures proper SSD alignment. You can download "Parted Magic" for $5 which does the same thing.

I used DD11 to clone a WD blue lappie drive to a Crucial mX100 via USB to a USB/SATA dock.
 
EaseUS, Macrium and Acronis make cloning software and you can use the free editions. Everyone has success with one or the other as posted in these forums.
 
Hi oslama, I am a little surprised you used the used EaseUS partition manager, but didn't use EaseUS Todo Backup. Great free tool that does exactly what you are trying to do. Just use the clone option. You really don't need to prep the drive either. It will remove the existing partitions in order to clone the layout of the source drive.
 
Hi oslama, I am a little surprised you used the used EaseUS partition manager, but didn't use EaseUS Todo Backup. Great free tool that does exactly what you are trying to do. Just use the clone option. You really don't need to prep the drive either. It will remove the existing partitions in order to clone the layout of the source drive.

The SSD drive was not recognized by windows and all the disk utility software, so i used windows disk management to prep the drive to MBR and then tried Todo Backup but it was taking took too long to clone 191GB windows partition, stuck at @ 52% ~ 4+ hours.
So i used Partition Manager to reformat and ran Macrium.

I did disconnect the HD and booted just from SSD
 
That is good to know, for some at least. In the link you provided it only says about the MX100 model. When I was checking about the M500 that I own I found nothing (and the OP has an M550). That makes use of third party software for migration necessary.
 
The last time I tried to use easeus it did the same thing to me. I stopped trying to clone and have instead moved to a clean install mentality when moving to a ssd. I've run into too many problems with cloning over the years. Any problem that is present on the source drive will migrate to the new drive and I don't want that to happen anymore.

If you must clone then use the manufacturers migration utility as has already been suggested. When I last cloned I used the intel migration software and it did a great job. Acronis has always worked best for me over the years and is what I would recommend if you want a program that isn't manufacturer specific.
 
The SSD drive was not recognized by windows and all the disk utility software, so i used windows disk management to prep the drive to MBR and then tried Todo Backup but it was taking took too long to clone 191GB windows partition, stuck at @ 52% ~ 4+ hours.
So i used Partition Manager to reformat and ran Macrium.

I did disconnect the HD and booted just from SSD

That's too bad that it took so long and didn't finish. I have run into that at times, where the progress indicator would get stuck, but I just left it to finish. I don't believe I had one take that long though.
 
Just use EaseUs and copy the Windows partition. Never had problems. Delete any partitions you have on the SSD beforehand.
 
Keep in mind that if your source drive is from a manufacturer that provides disc cloning software, you can still use it even if your new (destination) drive is from a different manufacturer that doesn't provide any. i.e. if the drive you want to clone is from Seagate, you can use Seagate's utility (DiscWizard which is just a branded/lite version of Acronis TrueImage) to do the cloning. It doesn't require that the new drive be Seagate, only that one of them is Seagate. Same with Western Digital's version of Acronis TrueImage.
 
Some manufacturer specific migration software checks the hardware id of the drives and will not move data unless the target drive is one of theirs. The last two I tried are the samsung and intel migration suites and if the target drive is not theirs it will not work.
 
Keep in mind that if your source drive is from a manufacturer that provides disc cloning software, you can still use it even if your new (destination) drive is from a different manufacturer that doesn't provide any. i.e. if the drive you want to clone is from Seagate, you can use Seagate's utility (DiscWizard which is just a branded/lite version of Acronis TrueImage) to do the cloning. It doesn't require that the new drive be Seagate, only that one of them is Seagate. Same with Western Digital's version of Acronis TrueImage.

I tried DiskWizard sincd my source drive is seagate and the ssd booted to windows login screen but restarted. then i ran startup repair from windows 7 dvd but still get boot loop.
 
I tried DiskWizard sincd my source drive is seagate and the ssd booted to windows login screen but restarted. then i ran startup repair from windows 7 dvd but still get boot loop.
If DiscWizard completed successfully and did not complain then it sounds like something wrong with the boot environment on the source drive, drivers loading during boot, or Windows is balking at the drive change when the storage driver loads. Do not pre-partition the SSD before hand, let the cloning utility handle it.

You never did specify what motherboard and chipset is in the system, whether you are plugging into a SATA port that is integrated to the chipset, or a third-party SATA controller.
 
Last edited:
If DiscWizard completed successfully and did not complain then it sounds like something wrong with the boot environment on the source drive, drivers loading during boot, or Windows is balking at the drive change when the storage driver loads. Do not pre-partition the SSD before hand, let the cloning utility handle it.

You never did specify what motherboard and chipset is in the system, whether you are plugging into a SATA port that is integrated to the chipset, or a third-party SATA controller.

gigabyte z87ud4h with i7

crucial ssd is on sata 2
 
Last edited:
I am not sure what you mean by SATA 2, except maybe using port #2. You want to make sure you are using the Intel ports for the clone, not the Marvell ones.
 
Back
Top