Macrium Reflect Clone Attempt Wiped My HDD

NavyLCDR said:

Well...how is Macrium Reflect booted from a rescue drive supposed to know what druve letters were assigned to which partitions on which drives by the last Windows OS that was booted?

I have learned to always name partitions to avoid the 'issue', but it seems to me that Reflect could easily 'note' the current letter assignments when creating the rescue drive, and apply these on starting up - where applicable, of course - not all drives may be present. That would be a 'luxury' feature.

I can see that wouldn't cope with a multi-booting system.

NavyLCDR said:

Well...how is Macrium Reflect booted from a rescue drive supposed to know what druve letters were assigned to which partitions on which drives by the last Windows OS that was booted?

It loads the mounted devices key from an installed os. Not clear to me how it decides which to load in a multiboot scenario.

See for yourself. Boot up some macrium winpe. Open regedit and look. It is an unusual "feature"

idlewanderlust said:

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

Thanks for the info. I had issues with Macrium too, on NVMe as a matter of fact, I no longer recommend it.
I have settled with easeus and there is of course aomei and horizondata, all have proven to be pretty reliable.