Win 8.1 x64 NTLite * "is not a valid Win32 application"

kylemichelsen

New Member
I am trying to slipstream Windows 8.1 x64 on a Windows 8.1 64x machine, using ntlite and it refuses to work, but successfully works on a windows 10 machine, integrating updates. I would like to be able to make images in 8.1 x64.
Tried several versions of ntlite.

I changed <ForceDismExe>true</ForceDismExe>
and still can't get ntlite to work.

How do I fix this?
Thanks.
 
Normally your 8.1 host should have the latest SSU (Servicing Stack Update) installed to process updates. What version of NTLite is this?
 
Any version, I've tried 2023.9.9419.0, 2.3.9.9039, 1.8.0.7261, should I go with a much older version? All Windows updates are installed on Windows 8.1 x64 host machine. Thanks.
 
I would re-install the current version (since nuhi's only going to care about recent builds), and attach copies of your preset, and NTLite.log.
The fact that 1.8.0.7261 doesn't work, and W10 does -- points to some weird DISM problem on your host.

If you happen to have a VM handy (like VirtualBox), might want to try to running NTLite on a vanilla 8.1 image.
 
Hi,

I tested the 2023.9.9419 inside Win8.1 Pro Update 3, with the kb5030329 for example (and a tons of others) into en_windows_8.1_with_update_x64_dvd_6051480.iso, all good (screenshot during the process attached).
8.1-2023-09-30-21-34-06.png

Does it break for you on even the kb5030329? If so, your host's DISM is somehow broken or NTLite is somehow blocked.
Reinstall/fix, or as garlin suggested, create a VM for image creation purposes (make sure to treat it as a real machine to not waste activations).

Let us know how it goes, this is not heard of before.
 
You can use free activation for testing a VM or another PC, since what you're reporting is a clear DISM failure -- so integrating one update will be the same as multiple updates. This won't require any licensed features to replicate.

"[ ] is not a valid Win32 application" error is typical when 32-bit and 64-bit DLL's are mixed up.
 
Back
Top