WinNTSetup v5.3.4

[JFX]

10 hours ago, freqout said:

This is great.  Wondering if this can be used to make the VHD bootable instead of actuing on my local boot partition, and if it can be scripted and completely automated from Powershell.

Yes, if you select a different boot drive, your local boot partition will not not be touched. 
For automation there are many command line options, see F1 - help.

Edited April 17 by JFX

[gbh19930406]

Latest Windows Server 2022 20348.2402 cannot run latest WinNTSetup 5.3.4, program said cannot find BCDBoot.exe and cannot keep running. However, WinNTSetup 5.3.4 can run on the Latest Windows 11 Pro 22631.3447. Both of two systems have bcdboot.exe which under /Windows/system32/. Please help to check what's wrong with v5.3.4, thx a lot. Plus, wimlib is upgraded to 1.14.4 (released February 24, 2024), and please add support for Windows Server 2025 thx.

[JFX]

Yes, there were some reports of this with Server 2022.
I can't reproduce it and checking if a file exist, is the most basic feature.

I could only assume something like an antivirus or filter driver that does interfere,
but it does not happen if I install Server 2022 with WinNTSetup. The new system does not show any problem.

The version display of wimlib and wimgapi will be removed, it just leads to wrong assumption and
some people start updating them manually, what only causes problems.

[Antonino]

so does that mean we will have no choice between wimlib and wimgapi? can we at least use the latter if that is the case?

[Atari800XL]

Good day to everybody. I have been out of the loop for a while, sorry about that.

I'm not a big fan of Windows 11, but the new LTSC 2024h2 leaked build 26100 seems to be a decent build.

On Windows 10, I used to run a short install_wim_tweak script on the install.wim before applying, to remove some components like Defender, Search and Cortana. However, this doesn't seem to work anymore with Windows 11.

 

My question to you kind and knowledgeable people on this board:

- Do you guys know of a method to remove Defender from install.wim, or at least some way to (temporarily) turn it off, etc.?

- Do we really have to learn to live with Defender, or there other ways to tame it?

- Does WinNTSetup have any capabilities to assist with this?

 

If this was discussed in this thread before, please excuse my laziness, I will try to read up on the matter.

Thank you!