JFX

Greetings, I only document all the hidden ini options in WinNTSetup.ini.txt. But @click-click made and pdf for the GUI ones: https://www.mediafire.com/file/znuf574scdac94d/WinNTGUI2Ini.pdf/file

Maybe, but if WinVerifyTrust fails, i would guess that your HostOS is very old.

Not sure what you mean. What error do you get?

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.

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.

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

Nope, disable defender tweak completely kills defender, so new tweaks aren't really necessary.

Don't know, you properly the first one ever getting this error message. Make sure you not running out of free disk space. You need at least the size of \Windows\System32\config\SOFTWARE.

Sure, just add a APPX dispaly name to the RemoveAPPX section. Wildcards like ? and * are allow, too.

It depends if there is a wimlib_WIMHOST_error.log than 47 is one of the wimlib error codes else it would be a System Error Codes.

SAB tires to start ImmersiveShellController before sending Local\ShellStartupEvent, this can't work in a WinPE. It's ok with a tiny twinui.pcshell.dll, but maybe SAB could ignore this check if: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\MiniNT key exists.

WinNTSetup has an option to save drive letter assignment. If this not works for you, than manually backup the registry value of your Z: under HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices.

It is the same syntax as the ini file uses: WinNTSetup_x64.exe NT6 -sysPart:HDD0:1 -tempDrive:Z: -sysLetter:C: -bcd:EFI -silent -setup

Yes, seems there got something wrong with the rar creation. WinNTSetup 5.4.1 - added missing LANG folder - bootice language files prefer MUI names - disabled multicore apply for x86 version. - removed system menu integration

See first post as usual. Merry xmas and a happy new year to all.