Macrium Reflect 8 restore problem. Main drive does seem to show as available to restore.

I've used Macrium for ages and in the past have always used the 'Image partitions required to restore Windows' option and am well used to using that. Never an issue.

On this W11 install I have been using the 'Image selected disks on this computer' option and today went to do a restore. I'm not seeing what I expect to see and the whole C drive and related partitions is not offered as a restore.

This is the disk layout and all drives are internal. Disk 0 contains the Macrium images under the partition called Macrium.



When making an image I have lately been selecting these partitions. File History from disk 1 and then all partitions on Disk 2. I notice Windows shows disks 0 and 1 and Macrium sees 1 and 2. Not sure if that is relevant or not:



When I try a restore all I see is partition F offered. The list of operations shows just one, restore partition F. I can not find any way to get the C drive partitions to show as available for restore. When the image is made it goes through I think six operations. making image F, making image D, making image C and so on. The image file is the expected size but it just does not show any of these as available to restore.

This is all I see on a restore. Partition F to be restored. Nothing else showing. I see the same thing using bootable rescue media The list of operations for the restore list only the one, restore F:

As a test I have made an image using the 'Image partitions required to restore Windows' option and that looks as I would expect and am used to. This is what is missing from the other files made using the other method.

How large is the image in question (F:)? What do you see when you mount that image?

The image size is around 62Gb for all partitions and a few Gb less for just the partitions needed for Windows. Top file C Drive Test is just Windows. That loads correctly for a restore.



And as viewed in File Explorer:

allan said:

What do you see when you mount that image?

Click to expand...

All partitions seem to be identified correctly by Macrium.

I've never used "'Image selected disks on this computer'", but rather definitions I create that contain the partitions I want imaged. It appears everything is there, it's just going under the label of F: drive, is that correct? If so, you're probably better off just creating a definition and using that for your imaging in the future.

What about the links "select a different source disk" and "select a different target disk" in the 3rd pic post #1?

allan said:

I've never used "'Image selected disks on this computer'", but rather definitions I create that contain the partitions I want imaged. It appears everything is there, it's just going under the label of F: drive, is that correct?

Click to expand...

I suspect its not going to restore the other partitions tbh. If I go right to the final step it says it will perform just one operation.

My reason for wanting to include File History was simply to keep all the indexes in order although in practice I suspect that does not matter and File History still works as normal, it just can not 'see' stuff archived between the the missing dates a restore gives.

JLArranz said:

What about the links "select a different source disk" and "select a different target disk" in the 3rd pic post #1?

Click to expand...

I have tried all those thanks, nothing gives any clues to why the partitions are missing.

As a quick test I imaged the D partition and as expected that shows correctly for a restore. Next I image F and D and this time only F is available as a restore even though the image file contains both.

I've been trying to research this issue and from what I gather it may be down to the fact that Windows is installed to Disk 1 rather than Disk 0 (I also see this may be the most preferable option in some cases) and that this causes issues with disk enumeration and the way Macrium sees the disks. It all gets complicated but it seems it is not uncommon to see this happening and the only real fix for a set up like mine is to do the images separately.

In a way I'm pleased I have this out now rather than when a restore was mission critical.