[WinNTSetup v5.3.5.2]

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

[WinNTSetup v5.3.5.2]

@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.

[WinNTSetup v5.3.5.2]

On 7/4/2024 at 5:18 PM, KittyMaster said:

I've two issues.

1st issue:
Use bootsect.exe to update the bootcode : ALL results in following

Windows 7 in UEFI mode is a bit picky about partition layout. It only support GPT.

 

On 7/4/2024 at 5:18 PM, KittyMaster said:

2nd issue:
I've placed the correct x64 files from Win8 backported drivers as instructed, but USB3 still didn't work:

The backported driver were update and are now signed with SHA-256.
So this method does not work, unless you find the older drivers.

[WinNTSetup v5.3.5.2]

2 hours ago, KittyMaster said:

Note: Inside the sources folder of the ISO, I noticed there are two files called "install.swm" and "install2.swm". Could these be causing the problem?

Dunno, maybe a Windows 7 related problem. Try older version like 4.25.

Maybe the SWM file is broken, try apply with image.exe.

[WinNTSetup v5.3.5.2]

WinNTSetup 5.3.5.2

- fixed crash with no source selection
- removed policy for HiberbootEnabled

[WinNTSetup v5.3.5.2]

Yes, the second policy for HiberbootEnabled has no effect and will be removed.
The first one seems to be different between windows versions.

[WinNTSetup v5.3.5.2]

On 6/23/2024 at 4:40 AM, wuliyen said:

!\Windows\SysWOW64\wbem\
!\Windows\SysWOW64\WindowsPowerShell\

The above writing style, only the directory files will be retained, the directory folders will not be retained.

Yes, MinWin focus on deleting files. It's unusual to delete complete folder and than want to keep it.

In that case, use wildcard pattern:

!\Windows\SysWOW64\WindowsPowerShell\*

 

[WinNTSetup v5.3.5.2]

It's just a problem with settings app. It properly tries to communicate with Defender and does not get any respond. 

[WinNTSetup v5.3.5.2]

Yes, Windows 10 2015 version already uses a 16 MB partition.

[WinNTSetup v5.3.5.2]

2 hours ago, Nikolay said:

Hi, why is your msr partition 128 MB and not 16mb?

Because older Windows versions used a 128 MB MSR partition.

The default unattend and diskpart scripts should work for all OS,
but you are free to edit them or add your own.

[WinNTSetup v5.3.5.2]

No, <ProductKey> is not supported with WinNTSetup's direct WIM apply.

Maybe you can use FirstLogonCommands to run: slmgr /ipk M7XTQ-FN8P6-TTKYV-9D4CC-J462D

[WinNTSetup v5.3.5.2]

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

[WinNTSetup v5.3.5.2]

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

[WinNTSetup v5.3.5.2]

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

 

[WinNTSetup v5.3.5.2]

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

[WinNTSetup v5.3.5.2]

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.

[WinNTSetup v5.3.5.2]

File permission are changed for MinWin by default, so Admin users have full access to the entire file system.

Profile\Options.ini --> options --> AdminAccess

 

To use modified *.inf files, drvinst.exe need to be patched.

you can remove signature check of inf files with:

WinNTSetup_x64.exe drvinstpatch

 

[WinNTSetup v5.3.5.2]

17 hours ago, belivakov said:

@JFX, please add an option to disable the Bitlocker in the Tweaking page, because of the new M$ policy for Windows 11 (24H2):

Just add this to your unattend.xml --> oobsystem.

    <component name="Microsoft-Windows-SecureStartup-FilterDriver" processorArchitecture="amd64" language="neutral" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" publicKeyToken="31bf3856ad364e35" versionScope="nonSxS">
      <PreventDeviceEncryption>true</PreventDeviceEncryption>
    </component>

 

10 hours ago, wuliyen said:

WinSxS.ini
Keep all files in the folder Manifests,
How to set up？

If you want to keep most of the WinSxS folder than delete WinSxS.ini.
Without it you black\white list WinSxS files like all other in the Remove folder.

[WinNTSetup v5.3.5.2]

Fixed.

[WinNTSetup v5.3.5.2]

That's because it is part of Windows 10/11. But old systems and WinPE are missing it.

[WinNTSetup v5.3.5.2]

I forgot offreg.dll again, re-uploaded.

[WinNTSetup v5.3.5.2]

WinNTSetup 5.3.5

- removed redudant code, WimHost options removed
- updated wimlib to version 1.14.4
- enforce modded wimlib
- HideProductKeys option defaults to 1
- minwim crash fixed
- minwim speed improved
- minwim extended log files
- fixed WinRE GUI bugs
- fixed crash installing WinXP

[WinNTSetup v5.3.5.2]

Tools\Win10Builds.ini

[StartAllBack for Windows 11]

Listviews group header text color is back to dark blue on dark mode. Was good with SAB 3.7.3.

[WinNTSetup v5.3.5.2]

@dimo70 You can't disable defender while the system is still running, it does protect it self.