What is the WinRE version of Windows 11 22H2?


After the latest update to Reflect, I updated my Rescue Media and boot tested it.  It booted WinRE 11 Build 22000.  I went to take a new image of my Rescue Media flash drive, and my old Comment said the WinRE build used on the last backup was 22621.


Did I make a typo last time?  Is the current WinRE 11 build 22000 or 22621?





Thanks!

 
EDIT: I loaded the last 2 Rescue Media image sets I made to check their comments.  From dates 2023-02-14 and 02-21, the WinRE version I have in the comments is 22621.  So, did I somehow regress back?  Is this a bug with Rescue Media builder in 8.1.7401?  If not, how can I fix this?  What are others seeing as their WinRE base version in Rescue Media builder?

Well, now I'm thoroughly confused.


I loaded 8.1.7387's flash drive image set and checked the Comment.  I put in the Comment for that image that it was WinRE Build 22621.  I put in a flash drive to restore the image to for boot testing.  The flash drive I inserted was already an older Rescue Media, so I booted it to check its version.  It was Reflect 8.1.7126 Beta WinRE 11 Build 22621.  I then burned the 7387 image to the same flash drive and test booted that.  Despite what I had said in the Comments, the restored image booted Rescue Media for 8.1.7387 BUT its WinRE was 22000!


So, what precisely is going on here?  Did I simply make a mistake in the WinRE version in the Comment?  But, that doesn't explain why the older Beta version has WinRE 11 Build 22621.


I THINK what is going on here is a mixture of 2 things.  I believe WinRE 11's latest build should be 22621 as it was on the Beta version.  I changed the Comment and saved the comment in the definition at some point, but in future, I manually changed the Comments for Rescue Media image sets.  Now, what I THINK has happened in the meantime is the 22H2 update's new Recovery partition.  I had 2 of them at one point, but eventually consolidated into the one by removing the old one.  Since then, though, I restored down pre-22H2 images and updated them to 22H2.  I think somewhere along the way, ancient Recovery files got retained in WINRETOOLS.


So, if someone could help me out here:

1.) what is the current Windows 11 22H2 WinRE build #?
2.) if my version is out of date, how can I fix it?


Thanks!

Hi,
I just build the rescue-media for a new installed W11-22H2-VM (VirtualBox) with both RE and PE:
WinRE has build 22621
WinPE has build 22000 (just now downloaded)

May be you have mixed RE and PE....
Have a nice sunday.


Regards, Il Capo

I doubt it's a case of WinRE being replaced by PE.  Both the screenshot I posted and the title bar of Reflect in the Rescue Media say WinRE.

This is interesting.  I restored a known 22621 WINRETOOLS partition, restarted Windows, removed the boot menu option from Reflect, changed based WIM to WinPE, changed back to WinRE, and even forced rebuilt the WinRE WIM.  It STILL says 22000.

+x

 

dbminter - 15 April 2023 9:25 PM

I was eventually able to fix it, but it required a bit of work.


I restored down a version of Windows 11 21H2 and its WINRETOOLS partition that was the version associated with 21H2.  I then ATTEMPTED to update it to 22H2, but 2 attempts in a row fixed the WINRETOOLS issue but BROKE Windows Update in 2 different ways.  However, the 22H2 update did create a 2nd WINRETOOLS partition along with my old 21H2 one.  I then restored my morning backup back to 22H2 and attempted to build new Rescue Media.  The new Rescue Media was 22621.


So, I'm just going to keep that old WINRETOOLS partition in place now that I've got something that works and just back it up along with the new WINRETOOLS partition.

I am struggling to see what the issue is.  I am on 22H2, and my winre is 22621.



Why do you want to keep the old winre partition?  It is only used in context of Macrium Reflect to create a usb drive/iso and new one works on older installs.


You can tidy up things as well as follows:-

If you type following in admin command prompt, it will move the current winre.win file from recovery partition and park it on C drive.



Then you can delete one of the recovery partitions and run the reagentc command with setrimage



You have to temporarily assign recovery partition a drive letter using diskpart or tool like minitool.   Yiu may need to create the folder structure as well.

Then run



This moves winre.wim back to the assigned recovery partition.

Then if you check, it should say it is enabled and which partition is in use (don't forget the hidden 16 mb msr partition - below shows recovery the recovery partition as 3rd but there is a hidden partition - Reflect shows it though)









In fact, the recovery partitions are not needed if not using bitlocker, as the enable parameter will put the winre.wim on C:\recovery folder.

This whole thing started when I tried deleting my old 22000 leftover WINRETOOLS and use the 22621 WINRETOOLS.  Somehow, my WINRETOOLS became 22000 (Macrium tech support verified this with an image copy of my WINRETOOLS.) when it should have been 22621 and I couldn't, initially, get my WINRETOOLS to be 22621.  Now that I have WINRETOOLS as 22621, I'm keeping the "old 22000" WINRETOOLS space allocated to itself so I don't get a repeat of this issue like before.