When I try to download the update patch for version 7.2.4711 I get a 'Patch Engine error (13)'. Any suggestions?
Could be an issue with a regional CDN not having the new installer or something. Try using the Download Agent to get the full installer file for the latest release. Free: http://updates.macrium.com/reflect/v7/reflectdl.exe Paid: http://updates.macrium.com/reflect/v7/reflectdlfull.exe
Thank you JP for your prompt reply. I'm busy at the moment, I'll try the download agent later and report the outcome.
I just tested (one machine only) and don't have the problem, Windows as per sig, but I didn't rebuild the boot menu. But I haven't rebuilt the boot menu, or rescue media, for some time - though I probably should have ... . Now I am a bit cautious to do so , especially as I may have another potential problem with AOMEI Backupper Pro installed .... Maybe a driver missing or not loading? I also prefer having that menu, even if it does slow my occasional reboots - so convenient.
If you back up the partition containing your Rescue Media file cache, you can always update/rebuild your Rescue Media, and if it doesn’t work, just extract the previous file set from your backup. You’d have to use the Skip WIM Rebuild option after that in order to have a new Reflect version build with an old Rescue Media file set, but this type of post-update problem with Rescue Media is precisely why I suggested to Macrium that they implement the Skip WIM Rebuild option during the Rescue Media Builder beta. Or just create a Rescue Media ISO from the current release before updating.
Need help !!! I have Windows Pro 1909 and just updated to 4711. OK, but when I build the rescue menia and test it I go to a light blue screen and I can not get Reflect or anything to show. Can it be a driver that needs to be added? I tried re and pe and nothing helps! I do not have this added to the boot menu. I guess I do not remember how to add drivers in boot, but not sure that is the issue! Is there a way to tell Reflect to rebuild the drivers?
I saw you advised that before. Must remember to do that in future, can't be too cautious. Haven't been following their forum but if there are boot menu / Rescue Media problems with this build, hope they get sorted soon! Nothing worse than not being able to trust an imaging program. I'd rather they erred on the side of conservatism with updates, and no sloppy testing!
Windows Pro 1909 boot menu failure, Windows Error: Windows Failed to Start A Recent Hardware or Software Change Might Be the Cause Fixed reinstalled Macrium Reflect. reinstalled windows, nothing worked .. since the last update for Reflect cant restore from boot menu or usb.
Reading your posts in this thread scared me so I tested MR and it seems to work fine on 2 pc's after last update. I updated both the boot menu and usb boot - no problems here. Sorry for problems there.
Encouraging, John! The other experiences are a bit concerning, and I don't feel up to testing this stuff right now. I hope they are the exceptions, and not the norm, as I just went ahead and updated this time - normally I wait a while!
Macrium Reflect for me has been rock solid,I have had version 6, 7. bit something has gone wrong since last update. and patch tuesday. and I find my self with 150 gb of backups that I cant restore.. I also updated both the boot menu and usb boot which is what landed me in this mess. the boot menu on usb boot and windows , just dont boot. any way I be moving to new backup software for now ..
Update from Macrium about the Boot Manager errors: https://forum.macrium.com/34231/RE-recovery-environment-0xc000000f-code?PageIndex=4
Funny as it looks like it now defaults to ON and I had to remove it but I never used it and always did notice this when building the media. Anyway, I STILL can not boot from any rescue media I built since windows 1909 and no previous boot disks work either. I somehow need to get this fixed!
Thanks again JP! I've just tried your link to 'Macrium Reflect Package download' and it worked out without any issues. Also for good measure, I have updated the bootable rescue media, performed an incremental backup and restored without any problems...
"Bug fixes and Improvements v7.2.4732 - 15th February 2020 Error: 'Error reading Image file' Some customers have received 'Error reading Image file' when creating Delta Incremental Images. This has been resolved. We recommend re-building your rescue media if currently built with v7.2.4711 to ensure compatibility with your backup sets. Volume detection Reflect would fail to recognise file systems formatted on Dynamic volumes spanning disks with 4K sector sizes. This has been resolved. Rescue Media Builder This release resolves a problem starting the rescue environment from the recovery boot created menu with v7.2.4711. Note: Running either this full installer or patch will automatically correct the current boot menu. If you continue to have problems then please launch RMBuilder and remove/re-add the boot menu. Moving the PE staging files to a different drive would result in duplication of the boot\Macrium sub folder. This has been resolved. Note: If a corrupt PE staging folder structure is detected by RMBuilder then it will be automatically deleted."
Thanks. I've just installed build 4732, updated the bootable rescue media, made an incremental backup and performed a restore in 41 seconds, Macrium is faster than ever...
I doubt they made any changes to the actual backup and restore processes, in fact every time I’ve seen someone on the Macrium forums say that it seems faster or slower after an update, Macrium usually comments to say that they didn’t change anything in that respect. However, if you try to restore a backup immediately after you capture it, then there will be very little for RDR to do in order to return your disk to the state of the backup you made immediately beforehand, so it will be fast.
Yes, I am aware that perception of a process after an update is certainly not objective unless it is specifically advertised as an improvement by MR, but I've never had restores under 1 minute before, and I always restore the system as a test after any update or uninstalling a new program. Maybe a fluke, but I also noticed that restore times change a bit with the USB hard drive used, sometimes there are differences of 10-15 seconds depending on the hard drive in use. Trivial differences of course, restoring in 41 secs or 1 minute or even 2 minutes, it is always very fast. I still remember with ShadowProtect 12 years ago, I could never get restores under 12 minutes, although I was not using incremental backups.
Good news that resolution has been so swiftly implemented. Issues were possibly caused by Win 10 update rather than Macrium itself? But c/should have been picked up in testing nonetheless ...
Thanks for confirming. Edit: Still a possibility that there may be some interrelationship with recent Win 10 CU issue ... we may not be out of the woods yet?