Windows 11 26H2 wpeinit not found

D

dhillonpatel1

New Member
Messages
3
Reaction score
0
1791207757804.png

Getting this when creating a custom ISO with drivers injected,

[HKEY_LOCAL_MACHINE\SYSTEM\Setup]
"CmdLine"="cmd /c start /min wpeinit && \\sources\\setup"

Have this injected to the WIM as well.

any ideas on how i resolve this,

trying on a Hyper V VM
 
garlin said:
This reg key only works for boot.wim (WinPE Setup). It doesn't belong in install.wim or install.esd.
Click to expand...
Thank you that is really useful,

is this even needed for the wim to work?

We are essentially putting the image on USB's and deploying it out that way.
 
What problem are you solving? The legacy Setup client is only really needed for compatibility reasons, like if you're using sysprep and the newer Setup doesn't like your captured WIM image. But it works using the old Setup.
 
I am just trying to build of a new image using 26H2 really nothing in particular
We used this when we set up 25H2 and worked perfectly fine.
All our computers are newer so i am guessing Legacy boot is not needed.
Don't quite understand this as the Legacy boot is not even enabled on the boot options and not in my WIM either.
 
Last edited:
Legacy boot refers to whether you choose to run the Setup client introduced in 24H2, or the old client which is still available in boot.wim.

The new client treats every clean install as an "upgrade", which can sometimes break a captured WIM image. Most users who modify a standard ISO shouldn't notice the difference, except for the install screens will look differently.
 
dhillonpatel1 said:
I am just trying to build of a new image using 26H2 really nothing in particular
We used this when we set up 25H2 and worked perfectly fine.
All our computers are newer so i am guessing Legacy boot is not needed.
Don't quite understand this as the Legacy boot is not even enabled on the boot options and not in my WIM either.
Click to expand...
Hi,
if you're saying NTLite causes this error just on 26H2, please attach that preset and if replicated it will be fixed.
However, make sure no custom REG files are integrated when making sure just the preset causes it applied to the original intact ISO.
 
You must log in or register to reply here.
Back
Top