JFX

No. But maybe try the ScanFiles.cmd. You could use it to populate the source combo box.

It it would work perfectly well running from invalid path, I would not have added this check.

Not sure why you have missing system files, but you can always download all requires files. WinNTSetup_x64.exe download

That path is invalid, some API's will misunderstand "..\Tools" to be the parent directory. I doubt you could even open that folder in windows explorer.

Thanks, added and also re-added offreg.dll.

I would say steve6375 has already given the right answer. WinNTSetup only applies the WIM to the VHD and create boot files. The image is still in sysprep phase and therefor will try to "specialize" the BCD store on first boot. If he immediately boot that VHD with Ventoy it will cause that error. I don't know how Ventoy boot it, but i guess it uses a virtual boot drive like NTBOOT. And that can't be seen later in the boot process. For the "hidden menu" he will need to use newer version.

WinNTSetup 5.3.4 - fixed problems starting as TrustedInstaller on some machines - fixed rare heap corruption - fixed CompactOS was ignored for Windows Server versions - Removed offreg.dll (will be downloaded for older Windows) - MinWin uses build number from registry rather than WIM - MinWin removed hard coded pathes - MinWin WinSxS.ini - can use "!" to avoid old components removal - MinWin WinSxS.ini can be deleted - MinWin fixed wincopy mode bug

\windows\system32\config should never be deleted. If it happens without you using telling it to do, then it's a bug.

Good you remind me about CompactOS and Server. It works so I'll remove this limitation. ! for WinSxS.ini will be supported. I think about making this ini optional. That should make things easier for people that just want to remove some files.

They were actually test versions for some problems that I could not reproduce. As there was not much feedback, i have to assume that all is fixed now. I will release an update, maybe next week.

Hi, no it's not a BETA version. It's the latest stable.

There is a command line tool for Group Policy: LGPO.exe. It should be possible to restore a saved backup in setupcomplete.cmd or FirstLogonCommands.

Nope, it's not possible to do this with registry.

That error means you did not run _DeltaPatchWinXP\FixWinXP.cmd.

Than use 3.8.6. Legacy version will not get any updates or fixes.

I would say that the problem, you create the boot files inside the VHD. You should select the bootable partition on local disk (I guess on disk 0).

The one in system32 folder is to old for users of Windows 7 or 8, so a newer version needs to be downloaded. Current ADK does not support Windows 7 therefore the files will be patched.

There is nothing I can do about. Looks like MS did only update the ReFS driver, but forgot to update the boot loader.

Good, next check if the service (WLANSVC) is running. and check wlan interfaces. netsh wlan show interfaces Maybe reapply reg file for classic taskbar flyout: MinWin\Default\Reg\SysTray_Network_Flyout.reg @wuliyen There will be only a few bug fix releases, but I don't plan to add any new features. WinNTSetup development is more or less frozen, but not yet discontinued.

@wuliyen Oh, right I was thinking about WinSxS folder, but you showed WindowsApps. It does work here and keeps all 5 folders. Maybe it's Windows setup that removes them depending on the "scale factor" of the newly installed Windows. @dimo70 You need to use GPT format for UEFI boot only and select the FAT32 ESP partition as boot drive.

@Antonino Blindly add files may not be the best way. First make sure you can install the driver and it show's correctly in device manager. @wuliyen That's a feature, read from here.

@Atari800XL I don't get any error message from Setup, if WinRe.wim is deleted. (at least not from 22631.2861.231204-0538.23H2_NI_RELEASE_SVC_REFRESH_CLIENTBUSINESS_VOL_x64FRE esd files) BTW: if I also delete the ReAgent.xml there is no error in the log file, only warning. @Antonino Lines beginning with ; or # are ignored and reserved for comments. You can also rename all the *.txt files inside Remove folder to *.ini. This should give comments a different color depending on the Editor you use.

Could it be you booted into this new windows and forgot to select "show hidden files" in folder options?

No, problem with Win11 23H2 v2 ISO. Also I don't no what to do about. If files are applied correctly and Windows Setup is deleting them, than it's not a bug of WinNTSetup.

Can't reproduce, works here.