Issue with %SERIAL% ComputerName and Windows 11 24H2

[mwdksh]

Hello,

I'm creating a new image (from scratch) based on 24H2 with NTLite 2024.12.10221. I have had one based on 23H2 for some time that works quite well.

I was getting an error message using the new image during setup so I switched the setup process based on information I saw in another thread about 24H2's installer issues.

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

The same issue occured again but this time there was more information in the error, specifically mentioning Microsoft-Windows-Shell-Setup.

Error
Windows could not parse or process the unattend answer file for pass [specialize]. The settings specified in the answer file cannot be applied. The error was detected while processing settings for component [Microsoft-Windows-Shell-Setup].

This is that part of my autounattend.xml.
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<ComputerName>PC%SERIAL%</ComputerName>
<RegisteredOrganization>ABCD</RegisteredOrganization>
</component>

If I remove the %SERIAL% and use a static name, the error doesn't occur (but also no dynamic name).

Should %SERIAL% still be working?

Any advice appreciated.

 

[garlin]

NTLite implements a dynamic ComputerName ([Prompt] and %SERIAL%), using a short VBS script it creates for you.

Have you removed or disabled VBScript component? Last I checked, 24H2 should have VBS enabled by default.

 

[mwdksh]

Thanks for that.

The issue was that I was using my previous autoattend.xml file but I think NTLite needs to specifically create the autounattend.xml using %serial% for an image otherwise the script isn't triggered/run... I think?

Even though after doing that I can now just copy in any autounattend.xml and it works.

 

[garlin]

The issue was that I was using my previous autoattend.xml file but I think NTLite needs to specifically create the autounattend.xml using %serial% for an image otherwise the script isn't triggered/run... I think?

Correct. NTLite needs to have created the autounattend.xml, when [Prompt] or %SERIAL% is used.

This forces NTLite to both write the script, and schedule the task's run. It doesn't work when you manually copy it into an existing autounattend.xml, unless you followed the process at least once before with this ISO.

Even though after doing that I can now just copy in any autounattend.xml and it works.

Unattended changes to an ISO are persistent. There are not erased if you reload the image, and leave Unattended alone. Whatever previous settings you had are undisturbed. But if you apply new changes from Unattended mode, the new edits will overwrite everything.