10% failure rate during custom ISO installation with Windows 25H2

Now you're throwing the IoT edition in the mix. Anyway, this is already tedious. Adios.

andersonricardo said:

No, civil construction

Click to expand...

Hello there,
I am a structural engineer currently collaborating with a construction company.
In addition to my professional work, I have recently undertaken a technical project in which I created a customized Windows image by employing DISM commands in conjunction with NTLite.

During this process, I encountered an issue that stemmed from the removal of certain critical components within the Windows image. To avoid such complications, it is strongly advisable to utilize NTLite without eliminating any essential features—particularly the Windows Recovery Environment (WinRE). Both versions 24H2 and 25H2 are highly sensitive to recovery-related components, and preserving them is crucial for system stability and functionality.

maur0 said:

I know what your problem is, I had the same problem. Simple solution: use a boot iso from Windows 11 23h2 or Windows 10.
use ultraiso to open windows 10 or 11 23h2 and replace your install.esd or install.wim and save new iso

work

There might be some junk folders there, just delete them with the script below.


%SystemDrive%

attrib winpepge.sys -s -h
del /f winpepge.sys
del /f DumpStack.log.tmp
rd /s /q $WINDOWS.~BT
rd /s /q $WINDOWS.~LS

Click to expand...

Hey maur0, I created an account on this site just to tell you thank you! this solution works!, I captured a 25H2 version with all the latest updates, then used rufus to create a 23H2 bootable drive, once it was created I just replaced its install.wim with my captured image and it worked great (it even works with secure boot enabled), also I don't care about duplicate SIDs etc. since its a sale image. anyways I don't know how you came up with this but thanks again!