Recent content by Pater

I used a 24h2 iso with latest preview update integrated via NTLite, installed in VirtualBox VM, then ctrl-shift-f3 and had the same issue. I then did "Power off the machine" (not send shutdown signal) and booted the VM again, and at that point it allowed ctrl-shift-f3. It is some bug. MS better...

On this version I'm also having the issue when selecting previously made presets (2024.11 ones, so recent), and I go to the Apply page, it will state "No pending changes, use the toolbar above or the navigation menu on the left to change some options..." when in fact 600 items are shown to be...

Hi, NTLite v2024.12.10216: I was noticing that when I add (not mount) a .wim, and I right-click on it to save.convert it as .esd, the result is that it will only offer to save as .wim (and that is indeed how it saves it). I tried reverting to earlier versions of NTLite and had to go back to...

So in the newer hardware scenario, you said you won't remove WinSxS. But then newer hardware would install the .wim faster, meaning it would matter less if the .wim is bigger. And you'd retain ability to install features post-install. With older hardware you like removing WinSxS; plus you said...

So test install times of .wim vs .esd -- see if it's worth it to you. So test whether including all features in your .wim hurts your intended purpose in any way whatsoever. So test whether or not "waiting longer" for an image to install is worth it (time) vs investing in faster hardware...

Since what you want to achieve does not appear to be possible: perhaps rather than asking yourself "at which point will I need to install a feature in a VM" you may have to ask yourself: "what does it hurt to have all the features installed in those VMs"?

Yeah :D Given that what he desires is incongruous with the reality of things, and the fact wim size is his focus, he is either going to have to create various images for his specific purposes, or create an image with all features installed and then disabling services or such relating to these...

Have you tried to install/enable all the Windows Features and capturing that as your Master image, and then creating NTLite'd images from that according to your purpose(s)?

No, "123" is just an example password. Yes, I included that section in case you want to create a local user with automatic login. In my case this is added mainly because there are various reboots actuated by my autounattend.xml where automated tasks are performed, but in general I also prefer...

Here's an example from my autounattend.xml (root of iso) that creates a local user account with a more richly populated OOBE section. It creates a local user account named "User" with auto-login (requires pass in that scenario) <AutoLogon> <Password>...

But that point right there is well taken. It would then only become an issue to look into when future version of uwp apps that one might like to retain in the image would possibly require newer/specific versions of said runtime(s), upon which one would then have to figure out which to retain...

Yes, most definitely it would :) I guess what I was getting to was that the SystemApps seemed rather stable for a long period of time, and NTLite was programmed to address them (allow their removal). So what I'm suggesting is that it would merely be a broadening of the detection of those...

Yes, it is UWP apps updating in background. I think what I'm pointing out is that the type and amount (and versions) of these remained stable for me for a good while, to now see this jump to x64-x86 varieties and more of them, plus what would seem to be reduntant version of the same app with the...

I liked keeping modern Calc in there plus the Webp and other format support is handy because certain image viewers rely on it, etc. Resulting .3007 NTLite'd image install.esd size: 1.33gb. My Dec build was about the same size (little smaller, see above) and I've been running that live for...

Captured a WIn11 23h2 image from sysprep VM, updated to 22631.3007. Used the same preset to lite-n it using NTLite v2023.12.9553 --here are some findings: Resulting install.wim (not .esd) is 0.03 bigger than Dec 2023 build state. -- not much, but then I removed a few additional components in...