Solved W11 24h2 and old installation setup

garlin said:

Windows PE and Windows Setup are basically the same image, except only one of them has Setup files.
ISO/USB boot only picks the image marked with Flag = 2.

WinPE is provided for IT & system modders who write their own custom deployment tools. And is the basis for Recovery tools like WinXPE. While you can apply changes to either image, Setup is the only one that matters.

For NTLite, you only need to check boot.wim (2) from "Reapply tasks across editions". Another way to perform this, is load one of the images from boot.wim directly, and add the Registry file. "Reapply tasks across editions" is a time saver so you don't need to do this separate step every time you work on a Windows image.

Click to expand...

for "Reapply tasks across editions":
this REG file needs to be added under the NTLite/REG section first, then only selecting 'Microsoft Windows Setup (x64)' under the 'Reapply tasks across editions' makes sense & does the job.

This is one way of doing it, but in this, there are two downsides

1. for every ISO produced via NTL, this task will be a repetitive job to perform
&
2. That REG file will be added inside the install.wim as well, without any real effect

But If I load a 24H2 vanilla (26100.1 in my case) ISO into NTLite & load the Microsoft Windows Setup (x64)
& add this REG file only to it, and create/pack the ISO, then, in that case, I can use that ISO for further modification with install.wim,
without everytime doing the 'Reapply tasks across editions'

What do you say?

Both solutions work.
I'm done here.

Just my 2 cents worth regarding the question of adding items to the autounattend.xml: If you want to add something to an answer file, consider using the "Windows System Image Manager" which is a part of the ADK. It's extremely easy to use and will position anything that you add to the correct location automatically.

My suggestion is to take note of exactly what WSIM does, maybe by comparing it to your original answer file. It won't be long before you get a feel for how the answer file is laid out. In no time at all you will be manually editing your answer files like it was just another text document

Another good way of learning is to follow one of Kari's outstanding tutorials. Just follow along with this and you should get a lot more familiar with the structure of the answer file.

Hi, "long time reader, first time poster"

i manually added this REG fix (DISM mounted boot.wim, loaded SYSTEM hive and edited REG_SZ)

[HKEY_LOCAL_MACHINE\SYSTEM\Setup]
"CmdLine"="X:\\sources\\setup.exe"

It still boots to new setup. Tips? Im playing around with ARM edition 24h2

try changing that back to winpeshl.exe

then use winpeshl.ini

SIW2 said:

try changing that back to winpeshl.exe

then use winpeshl.ini

Click to expand...

Thanks, i literally just tried that before your post and sadly didn´t work either

Hello,

I think the forum rules are no duplicate posts but alas perhaps it's warranted here so will only link it in case someone in this thread my have ideas to solve this issue w/ audio cutouts post update to 24H2: Audio cutouts in MSFS 2020 after updating to 24H2

Thanks, and mods of course remove it if I've run afoul with this link!

NoelCP said:

Hello,

I think the forum rules are no duplicate posts but alas perhaps it's warranted here so will only link it in case someone in this thread my have ideas to solve this issue w/ audio cutouts post update to 24H2: Audio cutouts in MSFS 2020 after updating to 24H2

Thanks, and mods of course remove it if I've run afoul with this link!

Click to expand...

I don't think your question is related. This thread is about running the new Setup vs. the legacy Setup client from a clean install.

If you have 24H2 issues, you can manually uninstall the audio driver and disable driver updates from Windows Updates. Reinstall an older version of the audio driver, and see if that makes any difference.