Why didn't the image decrease in size?

S

SunLion

New Member
Messages
17
Reaction score
1
I am a licensed Professional version user.

I renewed today, 2025.02.18.

In my first tests with Windows 11 24H2, I was surprised by the result, that even after removing several components,
the image was still huge.

As an example, version 24H2_Enterprise_LTSC:

- source image: 26100.1742, has install.wim with 4,190,507 KB

- After applying the recent update and removing components etc., install.wim was 6,016,520 KB

Am I forgetting something?

Why didn't the image decrease in size?

Any help will be appreciated!
 

Attachments

Hi,

it's the Servicing Stack compatibility option.
It preserves files Windows updates needs in WinSxS, and image saves files only once, so while that last copy remains in WinSxS, it's as if it wasn't removed, size-wise.
Good news is that the component files and registry are removed from active workspace, Windows/Program Files etc, only the static, non-active copy remains in WinSxS for Cumulative Updates to use.

More correct comparison before and after removal would be all files and folders in the Windows folder, excluding only the WinSxS directory.

If you want to switch that protection off, then you can remove much more like Windows Update and Windows Component Store (WinSxS), but you'll need to update Windows via the NTLite Host Refresh method.
It's basically the Windows in-place upgrade using an updated configured ISO, it keeps all your apps and settings intact.
 
When you're done testing an image, convert the WIM to ESD image format from the Apply screen.

ESD compression will shrink the WIM even more, but it's time consuming and should be avoided until after final testing.
 
I encountered a problem with BypassTPMCheck:

“This computer does not currently meet the system requirements for Windows 11”

How can I overcome this?
 
Are you running a live upgrade? That's a different bypass.
Settings / System / Setup requirement - TPM and Secure Boot - Host
 
That's a live or in-place upgrade. BypassTPM only works if you boot from the ISO.

When you mount an image from a live system, Setup run as an upgrade and requires the AllowUpgradesWithUnsupportedTPMOrCPU bypass, which the "Host" version in NTLite's Settings.
 
I'm trying to update the ISO.
I unpacked the ISO to a folder and I'm doing the process with it.
 
When I do the process, the second option of your images appears.

As I said, I want to update my ISO.

It seems that this is not possible so...
 
Are you saying when NTLite finishes processing an image, Setup will automatically run?

The only thing I can think of is you have Explorer set to auto-mount the newly created ISO, and the ISO has the default autorun.inf to run Setup.exe.
 
Look, what I did was like this:

- I used the update host option, when the menu opens, I selected the folder where I unzipped the ISO that I want to update.

- When the process reaches the end, it has the last option which is to run setup.exe in upgrade mode...

- this is where the TPM problem occurs

From there, there is no way to continue...
 
OK. You're running Host Refresh, which performs a live upgrade to reinstall the image.

The host setting from inside NTLite is what you need, or run this command as Admin before running setup.exe:
Code: 
reg add "HKEY_LOCAL_MACHINE\SYSTEM\Setup\MoSetup" /v AllowUpgradesWithUnsupportedTPMOrCPU /t REG_DWORD /d 1 /f
 
You must log in or register to reply here.
Back
Top