W11 24H2 ignores autounattend.xml

P

preiner

New Member
Messages
25
Reaction score
2
Hi,
23H2 seemed to work pretty well for me but i need to move forward.

I have my auto unattend section which worked on 23H2 with an older version of NTLITE but now things went to hell. I cant do two things.

1) I cant bypass LAN adapter requirement because it wants to create an MS account. I know i can shift-f10 and bypassnro but I need this to occur automagically without human typing

2) I cant seem to get unattend to do much. I need unattended section to automate everything except computer name and disk partitioning (These I always want to do manually)

Ive tried a dozen variations and no matter what I do I get that ugly UI with endless list of questions about keyboards and locales and whatever

(Yes, I have unattend ENABLED and relevant sections filled out.)

Thanks for any help.
 

Attachments

I should retest with the "new setup", I don't remember if I had problems the few times I tested and the autounattend.xml that I have been using for years
 
Re tested on "full ISO" with new setup and my autounattend.xml that I have been using for years and it's good

And no "requests" during installation except where to install Windows (no disk configuration with this one)
"Select location to install Windows 11" window => Desktop

* Generic key in file
 

Attachments

This is a "vanilla" autounattend.xml. Anyone who needs to add specialize pass commands will likely see their unattended file break Setup.

preiner uses the NTLite-specific feature "Prompt for Computer name" where NTLite copies "[Prompt]" as a placeholder in <ComputerName>. This is technically illegal as [ and ] are banned hostname characters.

NTLite expects to run NTLCompName.vbs before the specialize pass, and will replace the "[Prompt]" string with the user's provided hostname in \Windows\Panther\unattend.xml before Windows gets there and complains about it.

Just because you're not using the extended Unattended features, or not rewriting autounattend.xml by hand, doesn't imply a problem doesn't exist. There are many reports of 24H2 Setup not working with previous answer files.

You should try it with their configs, and not your own.
 
I tested "Prompt" a long time ago, it opens a prompt to modify the computer name during installation
If he want it to be automated, he should not put "Prompt" then, not to mention that it can cause problems, it would seem (I'll test just for fun)

EDIT : Ah... He wanted Computer Name manually

I prefer it when everything is automated (but to each their own use)
 
Last edited:
Not everything needs to be completely automated, some answer files are partially automated by design to skip over pre-determined settings. Anything that's left undefined in unattend.xml will be asked of the user while installing Windows.

Setup has always operated this way, and NTLite follows that example. You can automate as much, or as little, as you need.

Bottom line: Are you really trying to help the OP solve their problem or not? There are legitimate reasons for prompting for the hostname this early, like when you're joining an AD domain.
 
tistou77 said:
(I'll test just for fun)
Click to expand...
Where is the error (at what point) ?

I used his autounattend.xml file and install.wim where the VBS file was created, chose "test" when prompted to choose the computer name during installation, and Windows installed without any problem on laptop

His name on the Welcome page (before the desktop) and

View attachment 12983


Or is it not the right file that I used (the one from the 1st post) ?

EDIT : tested on French ISO
 

Attachments

Last edited:
You must log in or register to reply here.
Back
Top