NTLite import XML files

From the Post-Setup (Before logon) screen, Add / File and change the Destination path to "\path\to\parent\folder".
 
Destination would be "\". You're not allowed to specify a drive letter.

If you're copying your own autounattend.xml, it's easier to build and copy the ISO to the USB device first, then manually copy the autounattend.xml to the USB's root folder.
 
garlin said:
Destination would be "\". You're not allowed to specify a drive letter.

If you're copying your own autounattend.xml, it's easier to build and copy the ISO to the USB device first, then manually copy the autounattend.xml to the USB's root folder.
Click to expand...

can't this really be done in another way that makes everything automatic, because the other versions of windows 11 the answer file doesn't work on the new one
 
Copy the selfmade UnAttended.xml to the mounted NTL root folder before Apply image to ISO.
Typically: C:\NTLite\Temp\NLTmpMnt or change the drive you've chosen to mount the image in NTL ie.: D:\

Then is should work.
 
W11 24H2's new Setup client has known compatibility issues with some unattended files, that previously worked for 23H2 and older releases. If you have a licensed copy of NTLite, switch to the legacy Setup by choosing Settings / System / Boot/Setup - Legacy.
 
Agree - but if doing sysprep on Win24H2 with the build-in NTL UnAttended section - just delete Windows.old in root, and in Panther folder delete unattend and unattend-original file after capture.
Then it's possible to install 24H2 after change "Reseal mode" from Audit to a blank line in a second run of NTL even 24H2 new install changed to an upgrade depending mode.
 
OP is clearly not doing sysprep. Please don't confuse newer NTLite users.
 
francis11 said:
Agree - but if doing sysprep on Win24H2 with the build-in NTL UnAttended section - just delete Windows.old in root, and in Panther folder delete unattend and unattend-original file after capture.
Then it's possible to install 24H2 after change "Reseal mode" from Audit to a blank line in a second run of NTL even 24H2 new install changed to an upgrade depending mode.
Click to expand...

here is a screenshot of how to do it
 

Attachments

  • Screenshot (35).png
    Screenshot (35).png
    86.2 KB
Pcgamer27 said:
ok so this must be disabled
Click to expand...
Enabled and apply the change

I did it directly in boot.wim but possible to do it with install.wim mounted, NTLite does it in boot.wim
If I remember correctly, I don't remember which method remained, in the end
 
tistou77 said:
Enabled and apply the change

I did it directly in boot.wim but possible to do it with install.wim mounted, NTLite does it in boot.wim
If I remember correctly, I don't remember which method remained, in the end
Click to expand...

okay this way
 

Attachments

  • Screenshot (37).png
    Screenshot (37).png
    119 KB
The directory of the image that will be "used" to create the ISO
 
You must log in or register to reply here.
Back
Top