Macrium Reflect

same here, I thought it was just me, this happens on a laptop that is set to RST (RAID) in the BIOS even though it's not an actual RAID array. If I delete the RAID Driver which Macrium puts and put the old AHCI Driver it works but this didn't happen with the previous builds. I am sure they will release yet another paid version update soon

 

Thank you Spartan, mine is a Dell T5600 Desktop without raid

 

The problem you are having was caused by a MicroSloth update in early September and also using a WinRE for your basic rescue media. If you use a WinPE, the problem doesn't exist. This month, MicroSloth has issued another update which fixes the problem but you must rebuild your Rescue Media (if you wanna use WinRE) to have the problem go away.

 

TRF, thank you - Macrium is doing the WinRE by default and my Rescue Disk was only done last week, so I am not sure if this is already fixed. Never tried the other options but will try the WinPe 10 now.

 

Just to confirm, WinPe worked fine for me - all good. One follow up question, in the recovery environment I have the option to use legacy or uefi - both will allow me to access my images and I can browse them etc. Does it matter which option I choose there and under what scenario is one preferable to the other?

 

The option to choose is based on the BiOS your machine is running at... if you're an EUFI configuration, use that... if Legacy/MBR, use that.

 

I usually test booting in recovery mode and browsing an old image to see if things look ok. While I have done some restores in the past, I only did these when necessary or migrating to a new pc, still feeling uneasy doing a restore on my working pc. So would the wrong choice only rear its ugly head when doing a restore back to my destination pc? When browsing the images, I did not notice any difference between using legacy or uefi. My pc is legacy btw.

 

That choice matters if you need to run Fix Boot Problems. If you booted Rescue in Legacy BIOS mode, then that wizard will attempt fixes appropriate for booting Windows in Legacy BIOS mode — which won’t help you if your Windows disk is meant to be booted in UEFI mode. And vice versa.

Apart from that, if your system supports booting both ways, Reflect will run the same way in both modes. However, a system that allows Legacy BIOS booting won’t be able to have UEFI Secure Boot active. That’s a nice anti-rootkit mechanism. So if you don’t actually need to boot in Legacy BIOS mode, consider disabling it so that you can enable Secure Boot. That will have the side benefit of preventing you from accidentally booting the “wrong” way.

 

Jphughan, I moved to this PC maybe two years ago and it is Win10 Pro and does not support Secure Boot State. That's why it is still legacy. Not sure if this is/was related but TPM is not usable. I think I am ok with it as it is for another year or so and then move to the next system and this will be uefi.

 

looks to be only for the annual subscription, I'll never get that when there is a perpetual license availble.

 

In anyone else's experience is it better to deactivate a copy of Macrium before an OS upgrade and then reactivate or should it survive the upgrade without issue? This will be a server edition.

 

If you have the registration code available, deactivation is always the safest approach... no risk of failure or support interaction to solve such an issue.

It's really very painless...

 

I always install it, create my recovery USB thumb drive then deactivate the license from the help menu then uninstall it. It's better to do the backups before loading the OS anyway.

 

Why is that? Does the shadow service fail in ways that aren't detectable?

Maybe I've just been lucky.

 

Thanks for the replies. Sounds like I'll just go ahead and deactivate it and reactivate when done.

 

So far I didn't notice any problem making system backup when system is online. I doubt that there are any problems that would require making backups while offline.

 

Thanks. If it sometimes fails in such a way that reflect doesn't generate an error or warning, it sure would be nice for us to know more about this. It would be terrible to try to make a restore with a faulty image.

I've been trusting macrium reflect to make usable images, just like you, so I want to hear more from those who don't trust it.

 

I prefer to do the backups via the bootable disk because then I am sure that nothing is interfering such as security programs, system utilities, files in use, etc.

 

@TheRollbackFrog et al:
Macrium Reflect 8 Free v8.0.7690 [UEFI]
WinRE10 2004 (64-bit) v8.0.7690 Status OK
Current boot menu - Windows RE10 version 2004 (64-bit)
Boot Mode is set to UEFI; Secure Boot: ON; PTT is ON;
-
Just saved Differential and updated Reflect & Rescue (flash drive) media.
Boot menu and Rescue media = The operating system couldn't be loaded because the kernal is missing or contains errors.
-
W10RE Rescue (optical disk) media 1903 (64-bit) v8.0.6758 from May 2022 works.
-
Recommendations? create WinPE10 or run Windows updates. W10 Home 22H2 (19045.3448)

 

"boot menu" - either disk is not present, or wrong drive.
media - wrong mode, IMO UEFI cant boot MBR sticks.

WinRE is a "recovery environment", this is different from WinPE <- recommended.

try ventoy for sticks and put ISO files on the stick.
i dont trust recovery environments or recovery boot options.

 

I thought win RE was just a winPE image with some added do-dads for recovery options.

Thanks. I learn something new every day.

 

Bummer. Looks like the discounts are only on the annual plans now?

 

?

WinRE is default.

W10RE Rescue (optical disk) media 1903 (64-bit) v8.0.6758 from May 2022 works.
Rescue (flash drive) media 1903 (64-bit) v8.0.6758 from May 2022 worked before update.