Solved Latest Macrium Reflect updates

Latest Update:

v8.1.7469 - 18th April 2023



Release notes: Macrium Reflect Patch Details


Previous update:

v8.1.7401 - 3rd March 2023



Release notes:




Reflect Free does not get the update to v8.1. It does however still get security and bug fixes.

Latest Reflect Free update:

v8.0.7279 - 10th January 2023



Release notes: Macrium Reflect Patch Details

Macrium Reflect Free to reach End Of Life.

Macrium Reflect Free Product - End Of Life (EOL)​

Macrium Reflect Free v8.0 is the last version to receive feature, compatibility or bug fix updates.

Will future security vulnerabilities be fixed?

Yes, security patches will still be provided until 1st January 2024. After that date we will no longer provide any changes to the v8 Free code base.

Can I continue to use Macrium Reflect Free?

Yes, you can continue to use the software in perpetuity, your license to use the software is unaffected.

Will Macrium Reflect Free have any new features or updates for future Windows versions?

Macrium Reflect Free v8.0 supports Windows XP SP 3.0 up to, and including, Windows 10 & 11 version 22H2. There will be no new features or support for later Windows operating system updates.



Note: This notice only applies to Macrium Reflect Free.

Click to expand...

I always update my boot menu and USB drive as well.

Done & recovery drive created and tested.

@Brink - Shawn, can you consolidate all this into a "Latest" thread not titled to any particular release, like on TF? Thanks.

f14tomcat said:

@Brink - Shawn, can you consolidate all this into a "Latest" thread not titled to any particular release, like on TF? Thanks.

Click to expand...

I thought that too, as the Thread Starter I can change the title myself.

I have edited the title and updated post #1 now. I'll endeavour to keep Post #1 updated as required.

Since today the bootmedia of the latest Macrium takes a lot of time for testing the diskwrite-speed ( starts when making a backup) , it takes about 1 hour for making a backup !!
Used to be about 5 minutes !
When going back to a previous backup , all went fine ( in 4 minutes )
Did a disk-check ; no errors found ..........
What could be wrong........????

Tried to backup to another HDD , this time no problems , went very fast !
So , have to check the HDD , which I always used for backups , with a disk-check.............

pietcorus2 said:

Since today the bootmedia of the latest Macrium takes a lot of time for testing the diskwrite-speed ( starts when making a backup)....
.....Tried to backup to another HDD , this time no problems , went very fast !

Click to expand...

It's worth checking the disk, but it may not have a problem.

Is this the first time this install of Macrium has backed up to this particular HDD? If so, I've noticed that the speed check always takes a lot longer, if it's a drive that Macrium recognises as having used before then it seems to remember thst it has already tested it.

" the speed check always takes a lot longer "..............well costed me a lot of precious time !
Checked the HDD , which is used by Macrium since the start of Win11, a lot of backups in a folder ( Macrium)
No errors were found .
Then made a new folder ( Macrium2) on the same HDD , tried to make a backup to this new folder , succeeded ( 5 minutes ) ! Still dont know the exact reason for the writing-speed test problem , maybe the folder is too full(??) , but will send my next backups to this new folder ( Macrium2)...........

pietcorus2 said:

" the speed check always takes a lot longer "..............well costed me a lot of precious time !
Checked the HDD , which is used by Macrium since the start of Win11, a lot of backups in a folder ( Macrium)
No errors were found .
Then made a new folder ( Macrium2) on the same HDD , tried to make a backup to this new folder , succeeded ( 5 minutes ) ! Still dont know the exact reason for the writing-speed test problem , maybe the folder is too full(??) , but will send my next backups to this new folder ( Macrium2)...........

Click to expand...

You could have had a dodgy USB connection. Maybe degraded to USB 1 speed for some reason.

20% off for Halloween

Bree said:

20% off for Halloween

Macrium Reflect for Home Use

High performance backups combined with easy to configure backup plans, complete with ransomware protection and email support.

www.macrium.com

View attachment 42984

Click to expand...

If you wait one month, you will possibly get 50% off on Black Friday, but if they do not follow recent tradition...........

Thanks Count!

Not in a hurry for updating my boot-media , this time .
No changes reported for it.................

pietcorus2 said:

Not in a hurry for updating my boot-media , this time .
No changes reported for it.................

Click to expand...

I always update it as the heading always tells me I have not missed an update without having to backtrack version numbers.
It only takes 5 minutes at most.

I also work on opinion that you never know when you might fall foul of a bug that has been fixed. Like all things, I doubt they mention every bug that has been fixed - just headliners.

Does anyone know how to force Reflect to see the current booted OS, i.e. 22621 and not Dev or other OS's on the same drive? The Rescue Build always wants to pick up the highest one it can find, in my case DEV 25231 (?). Occasionally, the WIN on the DEV is not quite all together and causes issues. I thought some time back that had been corrected by Macrium to only pick up the current OS, then it went back to the highest it could find. I've tried hiding the partitions of other OS's on the drive, but that doesn't help. Any insights would be appreciated.

First post updated.

Yeah - this is a problem when multi booting.

You could try to use "reagentc /disable" on the other OSs to temporarily park the winre.wim file in OSs C drive. Then use "reagentc /enable afterwards.

Another approach could be to make an image backup of the other recovery partitions and delete them, restoring later.

This is one of the reasons I multiboot with native booting virtual hard drives as each OSs recovery partition is within the vhd and not visible when booting from another OS unless you physically mount the drive.

f14tomcat said:

Does anyone know how to force Reflect to see the current booted OS, i.e. 22621 and not Dev or other OS's on the same drive? The Rescue Build always wants to pick up the highest one it can find, in my case DEV.....

Click to expand...

This is how Macrium is supposed to look for the WinRE to use....

Windows Recovery Environment (WinRE)​

Files for the Windows Recovery rescue environment are pre-existing and located on the local file system.

The folowinng folders, and sub-folders are searched for file WinRE.wim

C:\Windows\System32\Recovery

<ALL VOLUMES>\Recovery

If multiple copies of WinRE.wim are found then each WIM is examined and the WIM that contains the most recent Windows OS is copied to the Staging Area.

Click to expand...

It would appear that if your DEV build is the version that's currently in your recovery partition then it will be found under <ALL VOLUMES>\Recovery and used. I would think that if you turn off the recovery environment in all builds then the only WinRE.wim it could find would be the one in the C:\Windows\System32\Recovery for the currently booted windows. If you do want the recovery enabled, then try only enabling it in your 22621 build.