WinNTSetup v5.4.2

[Sergei Strelec]

21 hours ago, JFX said:

WinNTSetup 5.4.2

- fixed could not start minimized
- fixed some wimcapture issues
- fixed possible buffer overflow in some minwin functions
- fixed crash on malformed Win10Builds.ini
- updated ux and drvinst patcher for Win11 build > 28000

JFX

Thank you. Happy New Year to you and all the best!

[Antonino]

20 hours ago, bovirus said:

 

thank u ever so much jfx - works like a charm!

[ceo54]

@JFX Thank you for the update. This program is so essential, I can't image install without it. Thank you for making it.

One question, I used the $OEM$ folder with SetupComplete.cmd inside but it never ran, Like the drivers/unattend dedicated tabs, can we also have dedicated tabs for SetupComplete, Firstlogon.cmd etc where we could specify the locations of the files and program make them available to Windows setup ?

Thank you for your great work. Highly appreciated.

[Antonino]

exactly, for a fully customized install. talking about this, I was gonna ask jfx a further question, for a change: does winntsetup limit itself to processing whatever .reg file it finds in the user-specified folder in the systweak slot or can it also process any other filetype there is in the said folder? Moreover, on the wake of all this, in my continuously and continually desperate attempt to customize my installs as quickly as possible, I was wondering whether we could "ask" winntsetup to install the required iso with the same config and settings as the online os it operates from or, for that matter, any other os offline. So far, I have been able to do it all with several .bat and .ps1 scripts on a post-install basis only. It would be just wonderful if one could have the resulting os with all the desired settings at first attempt, or nearly so. whatever automation I have tried so far that works perfectly concerns reg files only. on the same wavelength, I was wondering whether the .ini slot as in the case of sample.ini can actively process any other ini file that gets added, as happens with reg flles in the systweak slot or it accepts only one ini file to process.    

Edited January 3 by Antonino

[JFX]

Happy new year!

$OEM$ folder is automatically selected, if it's in the same folder as install.wim.
Else you can choose it on the "Ready?" window.

[ceo54]

On 1/2/2026 at 7:08 PM, JFX said:

Happy new year!

$OEM$ folder is automatically selected, if it's in the same folder as install.wim.
Else you can choose it on the "Ready?" window.

Thank you for the response. I selected the OEM folder on the ready page yet my SetupComplete.cmd never ran. Any ideas ?

[wuliyen]

13 hours ago, ceo54 said:

Thank you for the response. I selected the OEM folder on the ready page yet my SetupComplete.cmd never ran. Any ideas ?

[windeploy.exe] Client OS edition and OEM license detected and no enterprise edition detected, will not run SetupComplete.cmd

[Antonino]

excuse me, where is the ready page? everybody says the $oem$ folder should be placed beside install.wim, but in the iso file there is no sign of $OEM$, nor will iso accept any external addition. so where is a viable $OEM$ folder in the end?

[wuliyen]

8 hours ago, Antonino said:

excuse me, where is the ready page? everybody says the $oem$ folder should be placed beside install.wim, but in the iso file there is no sign of $OEM$, nor will iso accept any external addition. so where is a viable $OEM$ folder in the end?

Place it in the root directory of the installation medium (at the same level as the sources folder)

[ceo54]

On 1/4/2026 at 10:34 AM, wuliyen said:

[windeploy.exe] Client OS edition and OEM license detected and no enterprise edition detected, will not run SetupComplete.cmd

Thank you for the response. I'm aware of the OEM licensing forbids the execusion of SetupComplete but I'm not aware of client os, could you please expand ? Any non-business will be client OS that means essentially any client image. This doesn't seem right. 

[JFX]

All Server and Enterprise versions will support SetupComplete.cmd.
But lower client SKUs like Home and Pro, will not work if they are OEM versions.

If you select a $OEM$ folder, WinNTSetup will copy 

$$\Setup\Scripts\SetupComplete.cmd to \Windows\Setup\Scripts\SetupComplete.cmd.

After setup finished you can check the log file under: \Windows\Panther\UnattendGC\setupact.log.

[RafaCorreia]

Good afternoon. Excuse my English, but I'm using Google Translate. I use your application quite a lot here in my repair shop and congratulations on the quick, simple and functional solution.

I noticed an error in this new version: when I use the function in "Modifications - Disable User Account Control" in Windows 11 25h2, it gives an XML error, but when I use the old version it works normally (on the same machine). I noticed this because I always used the same XML and the same diskpart script.