Solved Latest Macrium Reflect 8 updates

Ohhhh dear... That was fairly poor oversight and execution on the side of Macrium! If the C:\ is not bootable NOR IS REFELCT!!
Okay, so we need to get this moved to a hidden partition or separate drive...

I understand you can make a USB, I have several Refelct v8 and v10 32GB USB's floating around for clients etc. But the whole point of the bootable menu is that the WIM should surely not stored on the C:\ partition??? Not another partition at the end of the drive?
MR is so advanced with overwhelming UI, I am confused why they would overly simplify this... EDIT: Thanks Kev! Step in builder to specify Macrium's dumping ground for the bootable WIM that should not be touched.

Bree, you're a good bloke. Thanks for your time, mate. Much appreciated!

Bree said:

Spoiler

C:\Boot\Macrium is Macrium Reflect's Staging Area. This is where Macrium builds the .wim file for the rescue media. It remains stored there for two reasons.

The first is so it doesn't have to to rebuild the rescue media every time you want to make a rescue USB, it just copies the existing files over.

The second is that when you add Macrium Reflect to the boot menu, it boots from the files stored here, as shown in the BCD entry.

There's nothing here that Macrium can't rebuild if you delete it, but if you have added Macrium to the boot menu it will no longer be able to boot to the rescue media.

Click to expand...

Flipmode said:

the whole point of the bootable menu is that the WIM should surely not stored on the C:\ partition??? Not another partition at the end of the drive?

Click to expand...

Wouldn't matter what partition it was in if the drive dies, you'd loose the lot. A recovery USB is an essential, the boot menu option is there as a convenience, it is so much faster to boot from.

Bree said:

Wouldn't matter what partition it was in if the drive dies, you'd loose the lot. A recovery USB is an essential, the boot menu option is there as a convenience, it is so much faster to boot from.

Click to expand...

For me partitions are always going. Just had to log in and recover 2nd partition on an external M2 SATA SSD in an external enclosure.

Whether lost clusters, in the wrong place at the wrong time, or drives ""mysteriously"" converting from ExFAT to NTFS... it's usually the partition that's infected, needing rolling back, lost a drive letter, lost it's file system (in this case!), having general issues, or requiring recovery.
That's the only reason why I suggested another partition. "They don't make them like they used to!".. Surely 5GB would be enough for MR to build on, plus future rebuilds?
But it would probably require a drive letter for MR to access and build....

Nothing to lose sleep over.... Ohh no! I can't sleep!

Edited.

Bree said:

but if you have added Macrium to the boot menu it will no longer be able to boot to the rescue media.

Click to expand...

Since when? I've always been able to boot from either.

From boot menu:


From 8GB USB:


EDIT to add: I always boot my USB media from the one-time boot menu which I guess bypasses the BCD?

I'm still on v8 8.1.8325. Is it likely Macrium will issue an updated patch to replace 8.1.8595 which seems to be causing problems? Mitch.

Scott said:

Bree said:

but if you have added Macrium to the boot menu it will no longer be able to boot to the rescue media.

Click to expand...

Since when? I've always been able to boot from either.

Click to expand...

Flipmode was asking what would happen if you deleted C:\boot\macrium. That would kill Macrium recovery from the boot menu, because that's where the BCD entry points to for the boot files.

Bree said:

Flipmode was asking what would happen if you deleted C:\boot\macrium. That would kill Macrium recovery from the boot menu, because that's where the BCD entry points to for the boot files.

Click to expand...

Okay, my misunderstanding. I should have read the thread more carefully.