Solved Latest Macrium Reflect updates

f14tomcat · Oct 31, 2022

cereberus said:
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.

Thanks, Martin. I understand the options, but I think for now I'll just keep with the PE for Win 11 supplied by Macrium. It's at 22000, so current enough.

f14tomcat · Oct 31, 2022

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

Rescue Media Builder - Knowledgebase 8.0 - Macrium Reflect Knowledgebase

knowledgebase.macrium.com

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.

Thanks, Bree. I made a note to myself to try the disable of the Recovery WIMs on all but 22621 (main OS) as suggested by you and Martin ( @cereberus ). I can't think of any reason I would absolutely need them enabled.

Thanks to both...........

f14tomcat · Nov 1, 2022

f14tomcat said:
Thanks, Bree. I made a note to myself to try the disable of the Recovery WIMs on all but 22621 (main OS) as suggested by you and Martin ( @cereberus ). I can't think of any reason I would absolutely need them enabled.

Thanks to both...........

Disabling the recovery partitions on all but my main OS had no effect on how MR found the RE to use. It still picked up the DEV build. I will stick with the PE unless somebody has another suggestion. Minor vent..... it seems silly that MR would force a bad choice on you.

Bree · Nov 1, 2022

f14tomcat said:
Disabling the recovery partitions on all but my main OS had no effect on how MR found the RE to use. It still picked up the DEV build. I will stick with the PE unless somebody has another suggestion....

Well it must be finding the newer DEV WinRE.wim from somewhere. Perhaps the Dev build has somehow overwritten you RTM one with its own?

I can only suggest you search the same locations as Macrium would, C:\Windows\System32\Recovery and <ALL VOLUMES>\Recovery, to see if you can find where this my have happened and (possibly) correct it.

cereberus · Nov 1, 2022

f14tomcat said:
Disabling the recovery partitions on all but my main OS had no effect on how MR found the RE to use. It still picked up the DEV build. I will stick with the PE unless somebody has another suggestion. Minor vent..... it seems silly that MR would force a bad choice on you.

You could try and image backup the recovery partitions, delete them and reinstate after MR has updated?

f14tomcat · Nov 1, 2022

cereberus said:
You could try and image backup the recovery partitions, delete them and reinstate after MR has updated?

That would work, but................. the time is an issue, but the wear and tear on the SSD and it's write cycles dealing with over 100 GB of writes. That's a show stopper.

f14tomcat · Nov 1, 2022

Bree said:
Well it must be finding the newer DEV WinRE.wim from somewhere. Perhaps the Dev build has somehow overwritten you RTM one with its own?

I can only suggest you search the same locations as Macrium would, C:\Windows\System32\Recovery and <ALL VOLUMES>\Recovery, to see if you can find where this my have happened and (possibly) correct it.

cereberus said:
You could try and image backup the recovery partitions, delete them and reinstate after MR has updated?

The third, and final one I will investigate, is a custom path to the .WIM. Currently, it is in an un-lettered partition just after the OS partition. I could temporarily assign a drive letter to it, use the Custom Wim option in MR, let it build the media, then remove the drive letter.

I may give that a try.

CountMike · Nov 25, 2022

Bree · Nov 25, 2022

New update released, first post updated.

v8.0.7167 - 25th November 2022

cereberus · Nov 25, 2022

Bree said:
New update released, first post updated.

v8.0.7167 - 25th November 2022

Cannot see it yet.

CountMike · Nov 25, 2022

Got notificatin few minutes ago
Huston or wherever it is, first it was a "Network error" and now from program itself

Bree · Nov 25, 2022

cereberus said:
Cannot see it yet.

It can sometimes take a few minutes for a newly released patch to propagate out to the CDN servers.

It's there now....

Edit: well, maybe it needs a few more minutes..... :wink:

cereberus · Nov 25, 2022

CountMike said:
Got notificatin few minutes ago
Huston or wherever it is, first it was a "Network error" and now from program itself
View attachment 46141

Getting http error 403 in UK