Final conclusion regarding Removals

Status
Not open for further replies.

koppees

Member
Messages
52
Reaction score
2
After intensive testing for a couple months, I have reahed to the final conclusion that it is not worth the hassle to remove anything else, except FOD packages. By removing regular Windows features (which removal is in many cases totally bugged), you only gain some disk space, but ZERO performance. Use UUP Dump ISO creation tool to exclude appx packages you don't need. You can also exclude Winre.wim and Edge browser. And that's the most optimal way to create Windows installation image.
 
That kind of feedback is not very constructive, everyone knows it's easiest to install full Windows and be done with it.

Been using Lite Template for years (before it was as a template), and other than Remove Reinstalls after CU install, haven't had any hassle.
Also removals are only for an individual, not to create image for others.
And common mistake is to think you need to remove all or nothing. That is why I put tricky components in red, I don't remove those in my workstation.

Other than removing Search, Defender and VBS, it's not primarily about the performance, but the clutter and privacy.
When a firewall prompts how many binaries want a connection to the internet, it's not a good feeling running full Windows.
Then setting up everything, turning off options left and right - it's simpler to remove it.
 
OK, let's be constructive.

Can we have a list of all Windows packages, which are needed for update to work, and which are not?
 
OK, let's be constructive.

Can we have a list of all Windows packages, which are needed for update to work, and which are not?
Windows updates can be installed from Ntlite if you wish to remove the Windows update.

There is also compatibility setting in Ntlite which you can turn off or on certain things you wish to remove/not remove.
 
This is not, what I asked. There are close to 1000 different data packages on an unedited 24H2 ISO. Some of them can be removed, some of them can't, for Windows update to work.
 
This is not, what I asked. There are close to 1000 different data packages on an unedited 24H2 ISO. Some of them can be removed, some of them can't, for Windows update to work.
Just remove windows update and use Ntlite instead to update if you are worried about removing the wrong thing that might break it. You can then control when and what you want. I have done the same thing on my system and works a treat.
 
I am not worried about anything. Instead, I have an idea, how to make much more optimized Windows installation image than just using NTLite.
 
I am not worried about anything. Instead, I have an idea, how to make much more optimized Windows installation image than just using NTLite.
Each to there own but if you would rather use a different program or do something else besides Ntlite there are other forums that will assist.

I have been using Ntlite for the longest time and there is nothing else I would rather use.
 
OK, let's be constructive.

Can we have a list of all Windows packages, which are needed for update to work, and which are not?
Just keep enabled Components - toolbar - Compatibility - Windows Update.
While at it, enable/disable any other compatibilities of interest.
Then use for example Gaming or Lite template, if you don't know what you don't need.

If you see it not working, open a new topic with the report and a preset how to see the issue.

If you meant literal Windows packages, and not NTLite components, I don't have that information.
 
Of course I meant literal Windows packages.

The deeper I dig the more bugs and problems I keep finding. I am sorry, but this software is not worth of 40€ a year. It should be in beta state instead.
 
Of course I meant literal Windows packages.

The deeper I dig the more bugs and problems I keep finding. I am sorry, but this software is not worth of 40€. It should be in beta state instead.
When you get to it, open a topic with one of those bugs and I'll check.
 
It's called Windows Update, once a month.
Either:
- disable or remove it and update via NTLite - Install Updates or Host Refresh
- run Remove Reinstalls after each update

edit:
- and of course if you force Windows to rebuild, like restore health, it will restore, how is that a surprise.
I'll see about possibility to workaround the restore health pathway.
We can continue on your other/same topic, this one is pointless.
 
Status
Not open for further replies.
Back
Top