Macrium Reflect Clone Attempt Wiped My HDD

Is the NVMe large enough to have held EVERYTHING that used to be on D?

No possible "it wouldn't fit, so it couldn't be transferred" issues?

Otherwise you might need to look at something like active @filerecovery. Those kind of programs will scan and if they find the data, you need to buy a license to recover it. Active is as good as any and it is about half the cost. Find & Restore Lost Files: Undelete deleted files and recover damaged disks

Your hard drive appears not to have a c: partition (well, not now anyway). So were you cloning a non-system drive to a bootable NVME drive? Was all of that now-empty D: partition full of something? Or was there a C: which has now disappeared?

mngerhold said:

Your hard drive appears not to have a c: partition (well, not now anyway). So were you cloning a non-system drive to a bootable NVME drive? Was all of that now-empty D: partition full of something? Or was there a C: which has now disappeared?

I was attempting to clone the hard drive I've been using for the last few years that had Windows and all my files (roughly 400 GB) on it to the new NVMe. I did this in Macrium while on the NVMe install of Windows. Both the NVMe and HDD had Windows running on them; the HDD had been my primary drive since my first build of this PC. I had only set up a new Windows install and Reflect when I attempted the clone.

I still don't know if you had a C: partition on the HDD (although you must have) - and now I'm even more confused: You were 'on the NVMe install of Windows', and attempted to clone the HDD to the NVMe? That can't be right! If it is, something was bound to go wrong. Perhaps you booted Macrium from a recovery USB stick?

mngerhold said:

I still don't know if you had a C: partition on the HDD (although you must have)

Yes, I did.

- and now I'm even more confused: You were 'on the NVMe install of Windows', and attempted to clone the HDD to the NVMe?

Correct.

That can't be right! If it is, something was bound to go wrong. Perhaps you booted Macrium from a recovery USB stick?

OK, I see where I left a gap. I started the process on the NVMe, at which time Macrium asked to make a recovery media for it to reboot to. At that point, the computer restarted and loaded the recovery media it created and attempted the cloning. Sorry, my ADHD strikes again.

OK, that makes sense. Unfortunately, I have no idea what happened to your data. Its of no consolation to you that I've never experienced an issue like this with Reflect.

It may not be a consolation, but I certainly wouldn't want this to happen to anyone else!

Are you absolutely sure that you selected the HDD partition as the source and the SSD as the destination? Could you have made a mistake and selected the HDD as the destination rather than the source? When you boot into the Macrium Reflect rescue environment, it is very possible for different partitions on different drives to get different drive letters than they had when booted into Windows.