Search results

Several settings lock the relevant UI elements after deployment. It would be nice to know if a setting I'm changing is going to lock after installing. 2024.3.9783.0

I notice that the "reapply tasks across editons" selects the Boot.wim and WinRE images in addition to the install.wim Does this break anything? Should I make sure those wims are left alone? It seems to remove the same stuff from them as the install.

I've forced NTLite to use DISM.exe and want to create an image that uses Recovery/LZMS compression, but still is in the WIM format, not ESD In the Settings.xml file the default settings is <WimCompression>2</WimCompression> which I assume translates to "DISM /Compress:max" with 1 representing...

Does it perform any better or is it less common to return errors or bug out? I know it might sound like a dumb question but I guess I'm paranoid a little and I also really like to squeeze the most out of my hardware. And I definitely don't mind sacrificing a few extra GB for my OS to do it...

There are a few of the settings in the xml file that I'm confused as to what they do exactly or want to make sure <DisableProtections>false</DisableProtections> <ForceDismExe>false</ForceDismExe> (I assume this forces to only use DISM.exe?) <ForceWimLib>false</ForceWimLib> (And this I assume...

I'm trying to disable the wim compression and make it none in the settings.xml file but I can't find any reference online to which number is equal to "none" compression. It's set to 2 by default, maybe 0?

I've noticed that NTLite still halves the WIM file size even when ESD export isn't selected. So I suspect some sort of compression or optimization is going on beyond just removing components. I really don't think I remove 4GB worth of components. Can anyone help me address this or find out...