On 6/5/2026 at 7:57 AM, dimo70 said:

JFX, Greetings! Where can I find the full list of all capabilities and features of an ini file for the latest version of WinNTSetup?

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

18 hours ago, click-click said:

Seems like bcdboot will fail if the boot files from the EFI partition are newer than what is in the source ?\Windows

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

On 4/27/2025 at 4:16 PM, Atari800XL said:

Does WinNTSetup use this setting in the "Disable Defender" section?

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.

WinNTSetup 5.4

- support for Windows 24H2 and Server 2025
- added arm64 and x86 versions
- language files prefer MUI names
- support for RTL languages
- use only one DISM session
- fixed Windows 7 ESP drive mounting
- updated Windows 7 USB3 drivers instructions
- new disable defender tweak includes Windows Malicious Software Removal Tool
 

The NTFS permissions comes from the WIM file.

MinWin apply only changes the admin rights (MinWin\Default\Options.ini --> AdminAccess = 1)

 

EDIT: I'll disable AdminAccess in next version, it's useful to test and modify MinWin installation, but should not be default.

On 8/9/2024 at 4:58 PM, sharicov@gmail.com said:

Cannot install Windows 11 from Win11_23H2_English_x64v2.iso

Windows 10 installation works fine (source: Win10_22H2_EnglishInternational_x64v1.iso)

Installing on USB disk (Samsung T3)

Winntsetup version 5.3.5.2

Tried all ways: normal, VHD and VHDx ways, static and dynamic.

Getting VHD BOOT INITIALIZATION FAILED Blue Screen error or BOOT INITIALIZATION FAILED Blue Screen error depends on installation type.

Please help.

Did you make any progress on this?

Sounds like the USB disk becomes inaccessible during boot.
Did you tried different hardware to boot the USB disk?

Is there any difference with official Windows To Go setup?

2 hours ago, click-click said:

one last question for now Does WinNtSetup do anything with BootDriverFlags?

No, it does not touch this value.

0x1C - is the default on Windows 10/11, so I wonder why you have a different one.

WinNTSetup_x64.exe NT6 -sysPart:Q: -tempDrive:Z: -sysLetter:-C: -bcd:ALL -silent -setup

Yes, the currently running system has the correct data in \DosDevices\Z:.
The offline system has invalid data in \DosDevices\C:

Mountpoints are calculated, but if you want to do it manually

Look up the data of the new partition under HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices
and add it to the offline systems registry \DosDevices\C: value.

8 hours ago, click-click said:

The BCD had the correct entries in the boot menu.

I doubt that. VHDs are unique, you need to updated the BCD for every new VHD.

Fixing mountpoint of system drive is always done, there is no special command line switch needed. 

Than maybe something is wrong with the WIM files you have.

@ibay770 WinNTSetup has reach EOL status.

You could use it's command line options to automate these steps.

 

@hhui Access denied error is very common with wimgapi or Dism, WinNTSetup already use Trusted Installer rights to overcome some of them.

You could try wimlib (top right window icon --> WIM API --> wimlib) for apply instead.