Has anyone cloned ver 2004 using Macrium reflect?

stonecherub said:

Bree:
Once-upon-a-time, this all made sense to me but, as I become an octogenarian, I find both my knowledge and my confidence are deteriorating. I no longer get the picture. ...
...I am re-thinking the whole enterprise. Swapping a damaged, loose 250 GB drive with a good one was trivial. Now, I must have control of Win10 and Reflect to write a good copy of C:/ onto the internal drive. And I just keep getting older!

With the recovery partition now after the C: partition in 2004 you'd need to manually adjust the size of the C: partition. It just adds a few steps to the procedure you have been using.

When you get to the Clone screen, untick the partition after the C: partition before clicking 'Copy selected partitions'.



Click on the C: partition in the destination drive, then click 'Cloned Partition Properties'.



Then adjust the free space to make room for the last partition...




...after which you can drag and drop the last partition onto the free space you created in the destination.




Then your clone will work as usual when you click the Next button.

If it ain't one damned thing, it's another. Following your directions with a fresh, quick formatted, loose 450 GB drive, I cleared "Copy selected ..." checkbox and selected the NTFS Primary partition (of two) but was unable to change the properties as that selection was grayed-out. Deleting that existing partition changed nothing.

If the fix is simple and replying takes much less than 5 minutes of your time, OK. Otherwise let's not waste any more of your time on this. I need to completely rethink recovery where I can restore C:/ from removable media. On the other hand, at my age, I may croak before I ever need to do something like this.

stonecherub said:

If the fix is simple and replying takes much less than 5 minutes of your time, OK. Otherwise let's not waste any more of your time on this. I need to completely rethink recovery where I can restore C:/ from removable media....

Well, the simplest fix is to make sure that the destination disk you are cloning to is the same size or larger than the source drive you want to clone. Then you won't need to worry about any resizing.

I'm not sure I follow exactly what you did or how it failed in your post above. The best thing is probably to take a break for a few days and come back to this refreshed. Then see if the steps in my post #11 make more sense.

If you want to completely rethink your recovery strategy then look at making a disk image rather than a clone. I use imaging rather than cloning to back up my machines. I use an external 2TB HDD to hold images of several different machines.

My M.2 drive is 465GB with less than 200 used. The Crucial loose drive is slightly smaller at 447 GB. Before MS changed the rules, I was able to write the contents of the M.2 drive to 250 GB loose drives.

Do you think it possible that a newer version of Reflect will address this problem? I can wait. I will mark this solved tomorrow.

stonecherub said:

My M.2 drive is 465GB with less than 200 used. The Crucial loose drive is slightly smaller at 447 GB. Before MS changed the rules, I was able to write the contents of the M.2 drive to 250 GB loose drives.

Do you think it possible that a newer version of Reflect will address this problem? I can wait. I will mark this solved tomorrow.

Macrium currently copies all partitions it can, starting with the first and working its way up until it finds one that's too large which it shrinks to fit. If that's the last partition then all is good and the clone will succeed. It's only when there is another partition after that one that it will give up and say that there's not enough room. You can manually make room by shrinking the C: partition a bit more than Macrium did, but as yet Macrium will not automatically fit all partitions under all circumstances - only in the simplest case where just the last partition is too big.

If you read to the end of the the thread I raised on the Macrium Forum you'll see that others have asked for this to be addressed.

Cloning to a smaller destination drive fails in Windows 10 version 2004

Whether or not Macrium will address this problem remains to be seen. It may not be straightforward to devise an algorithm that will work in all circumstances.

updated versions of the Macrium Reflect software since v7.2.5098 include bug fixes for Win10 v2004

• Changed Block Tracker
  
  
  • Fixed a permission issue that prevented the Encrypted File System (EFS) from encrypting some files on volumes that were formatted while CBT was active.
  • Improved compatibility with Windows 10 build 2004.