...could be a (missing) driver problem that's making the old image unbootable. (A new Windows install would find the appropriate drivers whilst installing). Unlikely though, as most SSDs will (AIUI) still work with default drivers.
I cloned mine on the host m/c (since the SSD was mSATA, and the laptop had a mSATA slot, I was able to leave the hard drive in-situ until cloned). This might make a difference in how BIOS finally sees things, but that is really clutching at straws.
Frankly, I'd try a different clone tool. I remember what I did with Macrium - it allows you to drag and drop the partitions you want to clone. So, in preparation for a single-pass clone, I first dragged the two "system" partitions in turn (and they set up to clone to the same size), and finally the data partition, for which there was nominally not enough space on the target disc (for the partition - though plenty of room for the data it contains). This by default then resizes the target partition to the maximum space available, and you then fire off the clone process for all the dragged partitions.
I suspect Aomei PM should (and might have) cope with resizing, but if you try with a different tool, at least you eliminate one potential suspect (and Macrium certainly introduces an additional step if you're going to (have to) resize partitions).
The free version of Macrium is sufficient for the process, and it is well described under "cloning" in their knowledgebase.
|
Unbootable SSD new
Unbootable SSD new
