Editing System. Changes are not going through. Many things are not removed like WordPad.

frewys

frewys

Member
Messages
53
Reaction score
9
Trying to slim the OS in VMware.

Editing and removing components. NTlite goes through the process of applying. For example, WordPad shows being removed but also a 0MB removed, and it is not removed.

I have tried this both on Windows 10 and 11 with the same result.

I save the changes in a preset XML file. When I load the changes they are still there as they never were executed.

What is the reason and can I fix it?
 
Please attach a (full) copy of your preset, so we can see what NTLite is trying to do. That's the only way someone can duplicate your actions.
 
garlin said:
Please attach a (full) copy of your preset, so we can see what NTLite is trying to do. That's the only way someone can duplicate your actions.
Click to expand...
Lol. Is THIS refering to NTlite!!?
I thought it was referring to removing future window updates

That would explain my issues
 
Your preset doesn't include Wordpad on the list of Component removals.

If you remove Windows Component Store (WinSxS), then this image cannot be re-updated after processing. Without WinSxS, DISM (and NTLite) cannot determine what's installed at the component level. The image can still be installed because Setup basically does a WIM file extraction.

It's an one-way trip intended for those who will never update, or re-edit their Windows images.
 
Maybe it is just me but that was not very clear it was referring to NTlite.
It makes perfect sense but I only thought of it cause I was looking for it.
If I am the only one who had this issue then it is on me I guess. For the future maybe add a reference to NTlite in the explanation? Or a compatibility checkmark for NTlite.
Just a suggestion.

Thank you SO much for your attention though :)

Edit: There is no reference to Wordpad. That was why I was trying to remove it post-install.
 
garlin said:
Your preset doesn't include Wordpad on the list of Component removals.

If you remove Windows Component Store (WinSxS), then this image cannot be re-updated after processing. Without WinSxS, DISM (and NTLite) cannot determine what's installed at the component level. The image can still be installed because Setup basically does a WIM file extraction.

It's an one-way trip intended for those who will never update, or re-edit their Windows images.
Click to expand...
Just to clarify. It is just removing the top option Windows component database that breaks NTlite?
Removing the 2 sub-options does not affect NTlite's function?

I am asking cause it looks like I have that selection still in my windows 10 install still ticked in.
The apply section gives me warnings if I remove the Windows component database but NOT the 2 sub-options. But based on what you sad removing the SXS folders breaks NTlite as I am experiencing but it doesn't give me the same warning FYI
 
By deleting the Windows component database component, it breaks the possibility of deleting other components afterwards (if you reload the image to delete components). It is indicated in the description
It's good by deleting the 2 sub components
 
tistou77 said:
By deleting the Windows component database component, it breaks the possibility of deleting other components afterwards (if you reload the image to delete components). It is indicated in the description
It's good by deleting the 2 sub components
Click to expand...
In the content it makes sense and after doing some more research. But it was not clear this was a NTlite breaker. Live and learn.
Thanks
 
You must log in or register to reply here.
Back
Top