Solved Windows 11 24H2 optional. Why?

So I decided to switch from the beta insider channel to the RP channel which promptly offered me the RP build of 24H2. After a lengthy install however I learned that my 24H2 file explorer would immediately crash if I right clicked any file or folder in it. This would occur even booting into safe mode. After great frustration not being able to find a solution to this huge issue I grabbed my Macrium backup 23H2 beta build and went back to 23H2. Maybe I'll attempt the upgrade again on a future build of 24H2 but this one was a failed experiment.

han jansen said:

Hi,

Did it turn on BitLocker even if it wasn't before?
two times a typo

Ciao, Han

Click to expand...

No.
On my Windows 11 Home PC Dell Inspiron 3280 , which I updated from 23H2 to 24H2 yesterday, Bitlocker Device Encryption is Off. (I had turned Device Encryption off in 23H2 also. I had stopped using Device Encryption long ago.)



On my Beelink SEi 12 MiniPC running Windows 11 Pro 23H2 which I updated to 24H2 today , Bitlocker Drive Encryption is Off. ( I hadn't turned Bitlocker Drive Encryption on in 23H2 anytime)

SIW2 said:

What are the contents of your Recustomization.xml ?

Click to expand...

@SIW2
I tried many methods to access the Recustomization.xml file in vain. Finally I used TestDisk to access the WINRETOOLS partition, list the files and copied the file. And this is the result.

This transcript is repeated in many languages.
I presume it basically refers to restoring the system to the DELL factory image.
Your comments?
Note: Since a new Winre.wim relevant to Build 26100.2314 has been written, I have created a new Macrium Reflect Rescue Media ( flash drive) and checked it works since I always use the rescue media for system backups and never from within Windows. The factory image is of no consequence.

That is so it appears in advanced startup options or whatever it is called.

There is probably another .xml in winre.wim\sources\recovery\tools folder which points at some dell program which is in winre. Your winre.wim looks pretty large. The dell program might still be in there. It might have survived any updates to winre.

If you used that winre.wim to create macrium media, you wont see the dell program even if it is still in there. Because macrium will bypass the recovery options and go straight to macrium launcher as the shell. It does that using winpeshl.ini
[LaunchApp]
AppPath = %SYSTEMDRIVE%\Program Files\Macrium\launch.exe



I used a similar method that Dell used with my own program

If anybody wants to have a play, I made a little thing that does it for you

add-to-wimv10.zip

^That looks wonderful. I think you should give the exact steps to be followed for that addon to make other users comfortable to followon .

SIW2 said:

Your winre.wim looks pretty large. The dell program might still be in there. It might have survived any updates to winre.

Click to expand...

My Beelink MiniPC, which has now undergone three feature updates shows the Winre.wim size of 740.31MB( screenshot below). The Dell Inspiron's at 865.77MB is just 125MB larger and still has 625MB free space in the Recovery partition which I think would be sufficient to take care of any future updates ( without creating a second Recovery partition) [ I have once expanded that partition when it reached near-full - always careful .]

I think you should give the exact steps

Click to expand...

rt click and run as admin the .cmd file





If you already have a bootable wim you want to use, answer N to the first question





Then it asks to browse to the bootable wim you want to use




Then it looks for your installed diskgenius, macrium and hasleo






Then it adds the files to the wim you browsed to. Wimlib puts them into the wim. It is very quick, no need to mount.

If you want you can optimize the wim to make it a bit smaller

Then you could copy the wim onto your ventoyed usb stick, which is easy for anybody to do.
More advanced users can add a winpe boot menu entry to the current bcd store if desired.

I expect everybody knows by now that if you prepare a usb stick using ventoy, you can just copy .iso files onto the stick and ventoy will throw up a menu from which you choose which .iso file to boot. Ventoy

It can do the same with .wim files. Create a folder on the big partition of the ventoyed usb stick called ventoy. Put this ventoy_wimboot.img file in the ventoy folder you just created https://github.com/ventoy/wimiso/releases/download/v1.0/ventoy_wimboot.img