Source hard Drive now not regognized

[Pampa]

Used Hasleo Disk Clone to clone a 512GB SSD to an internal  M2 SSD.

It worked. The M2 drive now boots, but the 2.5" SSD won't any longer. Presume some sort of hardware mismatch. How can this be corrected?

[admin]

It's clear that cloning operations do not modify the source drive, so I can't tell you why this is happening. Perhaps you could provide more detailed information to see if we can find some clues.

[Pampa]

It's clear that cloning operations do not modify the source drive, so I can't tell you why this is happening. Perhaps you could provide more detailed information to see if we can find some clues.

Thanks for the reply.
That's what I would have thought also, that the source drive wouldn't get changed at all. 

No idea what happened, but somehow the MBR (or drive letter assignment/structure) was somehow corrupted on the source drive and it was unable to boot windows from it. I was unable to rebuild it, after many attempts.

Luckily Hasleo had made a perfect clone to the M2 drive, so I just used that and used  clone hardware to completely fix the issue. 

All good now.

[admin]

Was the target disk in a USB enclosure during cloning? And did you attempt to boot Windows from the USB after cloning was complete? Is your computer UEFI-based?

[Pampa]

Was the target disk in a USB enclosure during cloning? And did you attempt to boot Windows from the USB after cloning was complete? Is your computer UEFI-based?

BIOS is set to UEFI + Legacy.

Source was a 2.5" SSD SATA drive (the drive I usually use to boot from); 
M2 target was in the single M2 slot in the motherboard itself (I use it as a spare if the 2.5" isn't inserted in the SATA dock).

Normally it boots from the SATA drive, but I can select the M2 drive if I want to during start-up, using the Bios' Boot Menu.

[admin]

Was the target disk in a USB enclosure during cloning? And did you attempt to boot Windows from the USB after cloning was complete? Is your computer UEFI-based?

BIOS is set to UEFI + Legacy.

Source was a 2.5" SSD SATA drive (the drive I usually use to boot from); 
M2 target was in the single M2 slot in the motherboard itself (I use it as a spare if the 2.5" isn't inserted in the SATA dock).

Normally it boots from the SATA drive, but I can select the M2 drive if I want to during start-up, using the Bios' Boot Menu.

Therefore, the target drive is not a USB drive. This shouldn't happen in this case, and we also don't know why.

[Pampa]

Ended up using cloning hardware to be able to use the 2.5" hard drive again.
I am also not sure what went on here, but now convinced it had nothing to do with your software.
Hasleo worked perfectly to clone to the M2 drive.
This one looks like it will remain a mystery.

(thanks for the help, nonetheless, much appreciated)

[admin]

Ended up using cloning hardware to be able to use the 2.5" hard drive again.
I am also not sure what went on here, but now convinced it had nothing to do with your software.
Hasleo worked perfectly to clone to the M2 drive.
This one looks like it will remain a mystery.

(thanks for the help, nonetheless, much appreciated)

I'm glad to hear that. Have a nice day!