WinNTSetup v5.3.5.1

[Antonino]

thanx jfx,

I have opened options.ini and I have come across the last line

AdminAccess=1

now what are the possible alternatives and consequent consequences? for instance, what happens if I have the following

AdminAccess=0

???

I also tried running WinNTSetup_x64 drvinstpatch

and it said it wanted the names of inf files and me to choose from among 2 options (p and a, patch and analyze) and then file1, file2, etc - I could not get a clue how to go on.

Edited May 16 by Antonino

[Antonino]

if u want ur printer to keep working in ur minwinned vhd, you might wanna consider the following list to add to your deletion restrictions in the winnsetup remove folder:

!\windows\system32\winhttp.dll
!\windows\system32\winnsi.dll
!\windows\system32\winspool.drv
!\windows\system32\winsta.dll
!\windows\system32\wintrust.dll
!\windows\system32\WinTypes.dll
!\windows\system32\winusb.dll
!\windows\system32\wldp.dll
!\windows\system32\WmiPrvSE.exe
!\windows\system32\wmiutils.dll
!\windows\system32\ws2_32.dll
!\windows\system32\WSDApi.dll
!\windows\system32\wsnmp32.dll
!\windows\system32\wtsapi32.dll
!\windows\system32\advapi32.dll
!\windows\system32\APMon.dll
!\windows\system32\AppMon.dll
!\windows\system32\atl.dll
!\windows\system32\bcrypt.dll
!\windows\system32\bcryptprimitives.dll
!\windows\system32\C_437.NLS
!\windows\system32\C_1252.NLS
!\windows\system32\CbsApi.dll
!\windows\system32\cfgmgr32.dll
!\windows\system32\cimwin32.dll
!\windows\system32\clbcatq.dll
!\windows\system32\CNMLMDR.DLL
!\windows\system32\coloradapterclient.dll
!\windows\system32\combase.dll
!\windows\system32\crypt32.dll
!\windows\system32\cryptbase.dll
!\windows\system32\cryptnet.dll
!\windows\system32\cryptsp.dll
!\windows\system32\cscapi.dll
!\windows\system32\DDORes.dll
!\windows\system32\DevDispItemProvider.dll
!\windows\system32\deviceassociation.dll
!\windows\system32\devobj.dll
!\windows\system32\devrtl.dll
!\windows\system32\dhcpcsvc.dll
!\windows\system32\dhcpcsvc6.dll
!\windows\system32\dnsapi.dll
!\windows\system32\drvstore.dll
!\windows\system32\dsrole.dll
!\windows\system32\fastprox.dll
!\windows\system32\FirewallAPI.dll
!\windows\system32\framedynos.dll
!\windows\system32\fwbase.dll
!\windows\system32\FWPUCLNT.DLL
!\windows\system32\gdi32.dll
!\windows\system32\gdi32full.dll
!\windows\system32\gpapi.dll
!\windows\system32\iertutil.dll
!\windows\system32\inetpp.dll
!\windows\system32\IPHLPAPI.DLL
!\windows\system32\jscript.dll
!\windows\system32\kernel.appcore.dll
!\windows\system32\kernel32.dll
!\windows\system32\KernelBase.dll
!\windows\system32\l_intl.nls
!\windows\system32\locale.nls
!\windows\system32\localspl.dll
!\windows\system32\lprhelp.dll
!\windows\system32\lprmon.dll
!\windows\system32\mfc42u.dll
!\windows\system32\msasn1.dll
!\windows\system32\mscms.dll
!\windows\system32\msimg32.dll
!\windows\system32\msls31.dll
!\windows\system32\msvcp_win.dll
!\windows\system32\msvcrt.dll
!\windows\system32\MSWB7.dll
!\windows\system32\mswsock.dll
!\windows\system32\msxml6.dll
!\windows\system32\msxml6r.dll
!\windows\system32\ncobjapi.dll
!\windows\system32\netapi32.dll
!\windows\system32\netprofm.dll
!\windows\system32\netutils.dll
!\windows\system32\npmproxy.dll
!\windows\system32\nsi.dll
!\windows\system32\ntdll.dll
!\windows\system32\ole32.dll
!\windows\system32\oleaut32.dll
!\windows\system32\powrprof.dll
!\windows\system32\Print.PrintSupport.Source.dll
!\windows\system32\PrinterCleanupTask.dll
!\windows\system32\PrintIsolationProxy.dll
!\windows\system32\prm0009.dll
!\windows\system32\prntvpt.dll
!\windows\system32\profapi.dll
!\windows\system32\propsys.dll
!\windows\system32\psapi.dll
!\windows\system32\rasadhlp.dll
!\windows\system32\riched20.dll
!\windows\system32\riched32.dll
!\windows\system32\rpcrt4.dll
!\windows\system32\rsaenh.dll
!\windows\system32\samcli.dll
!\windows\system32\sechost.dll
!\windows\system32\secur32.dll
!\windows\system32\SensApi.dll
!\windows\system32\setupapi.dll
!\windows\system32\sfc_os.dll
!\windows\system32\SHCore.dll
!\windows\system32\shell32.dll
!\windows\system32\shlwapi.dll
!\windows\system32\signdrv.dll
!\windows\system32\slc.dll
!\windows\system32\snmpapi.dll
!\windows\system32\spfileq.dll
!\windows\system32\spinf.dll
!\windows\system32\spoolss.dll
!\windows\system32\spoolsv.exe
!\windows\system32\sppc.dll
!\windows\system32\srvcli.dll
!\windows\system32\sspicli.dll
!\windows\system32\stdole2.tlb
!\windows\system32\StructuredQuery.dll
!\windows\system32\sxs.dll
!\windows\system32\taskschd.dll
!\windows\system32\tcpmon.dll
!\windows\system32\ucrtbase.dll
!\windows\system32\umpdc.dll
!\windows\system32\urlmon.dll
!\windows\system32\usbmon.dll
!\windows\system32\user32.dll
!\windows\system32\userenv.dll
!\windows\system32\usp10.dll
!\windows\system32\version.dll
!\windows\system32\wbemcomn.dll
!\windows\system32\wbemprox.dll
!\windows\system32\wbemsvc.dll
!\windows\system32\webservices.dll
!\windows\system32\win32spl.dll
!\windows\system32\win32u.dll
!\windows\system32\Windows.Devices.Enumeration.dll
!\windows\system32\windows.storage.dll 

[aviv00]

Feature request

Multi Lang

from -

dism /Get-WimInfo /WimFile:install.wim  /Index:1

get all the lang available

Languages :
        ar-SA
        en-US
        es-ES
        he-IL (Default)
        pt-BR
        ru-RU

and have option to choose which lang to install

so after the deploying is done and rest

it will run

dism /image:p:\  /Set-AllIntl:he-il

and set the unicode and ui of deployed image before booting

 

 

Ty for considering

[Wu-Tang]

Hello guys.

I have error in two last version 5.34/5.35, and in 5.30 havent.

When start create image mounted from vmware.

How to fix this to use last version?

[JFX]

10 hours ago, Wu-Tang said:

When start create image mounted from vmware.

How to fix this to use last version?

That's because vmware mounts in the user session and WinNTSetup now uses TrustedInstaller for WIM operations.
You can get back old behavior by adding this to WinNTSetup.ini

[WimHost]
RunAsTI=0

However VMware did removed the buggy disk mapping in version 17, so maybe better to mount the VDMK with OFSMount.

This allow you to mount as physical disk and the capture won't have problems with special files like WIMBoot pointer files.

[JFX]

WinNTSetup 5.3.5.1

- fixed language file creation failed with 5.3.5
- fixed capture of mounted VMware disks
- added support for multi language WIM files

[U96]

 

\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\

 

Translation of missing program lines into Russian

1049.dll

Edited Tuesday at 05:31 PM by U96

[U96]

@JFX

 

Please add a dark theme to the program itself. The fact is that in Windows 8.1 or Windows LTSB there is no dark theme in the system and the program is white.

mistakes:
1) The program does not load the ADK automatically in Windows LTSB.
2) The program does not show the Wimgapi version.
3) The program picks up icons from the system and if you change them to your own in "WinNTSetup_x64.exe "then they are all different.

Screenshot:

Edited Tuesday at 05:31 PM by U96

[JFX]

1 hour ago, U96 said:

Please add a dark theme to the program itself. The fact is that in Windows 8.1 or Windows LTSB there is no dark theme in the system and the program is white.

Adding dark mode for current Windows 10/11 builds, was already several month of work. I don't do this for deprecated windows versions. 

As for your mistakes:

1) It now longer loads ADK, if the current windows don't needed it.

2) Version display was removed, because some people carelessly updated and just broke supported OS versions, for no reason.

3) That's wanted, looking more current system conform.

 

Re-uploaded, you now can disable these 3 options in WinNTSetup.ini. 

[Options]
NoDownload=0
ShowEngineVersion=1
NewIcons=0

 

Edited Tuesday at 07:06 PM by JFX

[U96]

@JFX

1) The fact is that your program is most often embedded in Windows PE. In order not to embed drivers and the "Internet" service into WinPE by reducing the size of WinPE (I build WinPE 10 x64 myself weighing only 160 mb.) I prepare "winntsetup" before adding the iso image by downloading the SDK. I can do it manually, but how will people do it who don't know how to do it? 
2) Regarding the dark theme, the situation is the same for all versions of Windows NT. The fact is that in WinPE, heavily stripped down, there is no dark theme in the system, even if it is assembled on the newest Windows 11. 
3) The same situation applies to icons. In WinPE Windows 11, they are also displayed incorrectly, they may not be visible on some systems at all. "Winntsetup" is used mainly in WinPE and extremely rarely in a full-fledged \ installed system.
Don't get me wrong. I just looked at the program as ordinary people in different situations.

[Antonino]

I beg to differ - I use winntsetup for regular systems, I never use winpe, and I know quite a few people who can share the same situations.

 

Edited Tuesday at 10:20 PM by Antonino

[xiaoyue]

2011 年 1 月 31 日晚上 8:49，JFX 说：

PreventDeviceEncryption | Microsoft Learn https://learn.microsoft.com/en-us/windows-hardware/customize/desktop/unattend/microsoft-windows-securestartup-filterdriver-preventdeviceencryption

According to Microsoft's description, the unattended file is about PreventDeviceEncryption

The parameter <PreventDeviceEncryption>true</PreventDeviceEncryption> must be in the following stages:

Valid Configuration Passes

offlineServicing

specialize

auditSystem

oobeSystem

The Win7-11-Select.xml example for winntsetup puts this code in the FirstLogonCommands phase. Is this parameter valid?

 

[JFX]

@xiaoyue it does work as expected, ignored by older Windows versions, and converted to registry by newer ones.

[dimo70]

JFX, can you publish autounattend.xml for win 10, 11 with disabled bitlocker automatic on, and full unattended setup without asking anything? Thanks in advance. 

For making things easy i did this file, but not sure if everythink is good to work

Win7-11-Automatic.xml

Edited Wednesday at 04:47 PM by dimo70
adding sample file

[JFX]

I think you can do this. The error your xml generates is very clear.