Compatibility mode needs to highlight core Windows functions in RED

garlin

Moderator
Staff member
Compatibility mode treats several core Windows functions as equally important (or unimportant) as the optional products.

Making this distinction clear will reduce the volume of removal problems we see today. Users unfamiliar with their importance are disabling protection without understanding the consequences.

OOBE, DISM, and Recommended need to be displayed in bold or red text. Unchecking them should require confirmation.

While NTLite warns you about missing components during Apply, it has not reduced the problem of over-slimmed builds.
The right approach is to avoid changes to OOBE, DISM and Recommended protection before it happens.
 
Last edited:
I sort of agree, with the exception of the Recommended, it's not that hard-limited as OOBE and DISM/Servicing stack.

Thinking about it, the current wish is to have a mode selector when visiting the Components page.
Basically if you select to be able to install updates, it will lock servicing stack compatibility, and vice-versa, if choosing that deeper removals are more important than updateability (or will update via host refresh), it will pre-remove WinSxS, uncheck servicing stack etc.

That wizard/questionnaire could go deeper in the future, do tell if you have ideas, more useful it seems, sooner it will be made.

Thanks.
 
Also locking for connected apps like Xbox Live, which require App Store, MS Account sign-in. We've seen how easy it is break them.
 
Also locking for connected apps like Xbox Live, which require App Store, MS Account sign-in. We've seen how easy it is break them.
There is Microsoft Store compatibility option already that should cover sign ins as well, will need to see some reports of it failing with Win11 to upgrade it.
 
Change some removals to Live processing only, especially when they could break Setup or dont allow them to be removed.

I dont and wouldnt remove DISM or anything related to it where you can service an image either with the tool or DISM with the command line because i guarantee the user will use the resultant build for image servicing at some point.

Gaming and Barebones type presets can be a downright menace when combined with users impatience and lack of experience. They see Xgb installed or iso size of Xgb and their eyes pop forgetting that the preset creator has tested that preset over many months for their own specific needs and purposes.
 
Change some removals to Live processing only, especially when they could break Setup or dont allow them to be removed.

I dont and wouldnt remove DISM or anything related to it where you can service an image either with the tool or DISM with the command line because i guarantee the user will use the resultant build for image servicing at some point.

Gaming and Barebones type presets can be a downright menace when combined with users impatience and lack of experience. They see Xgb installed or iso size of Xgb and their eyes pop forgetting that the preset creator has tested that preset over many months for their own specific needs and purposes.
Okay but m8
1Mb is 1Mb
I choose a no name preset instead of creating one, if the random preset free up 1Mb.
 
when im writing 18gb to disc in a single task even 1gb off the os means beans to me now. i now have a limited set of removals that keeps the os intact because i dont want to create a new image next week when i do something new.

Each to their own though. Its not the presets themselves that are the problem its overzealous users.
Ive said it till im blue in the face you got cherry pick and to test in batches, thats how i got windows 7 x64 installed size of 1.26GB, tested to destruction many times. Some people are not patient and they want a quick fix now. There is no quick fix now or 1 size fits all solution.
 
Last edited:
I choose a no name preset instead of creating one, if the random preset free up 1Mb.

Will you expect support from the preset's author?

What we have are "no warranty" projects which one person is very familiar with their own requirements to make Window work. This may be different for someone else, who doesn't understand what they're removing to free 1MB.
 
Will you expect support from the preset's author?
probably and the author will help where they can but there comes a time when enough is enough, part of the reason i gave up with presets, i dont know if keeping X will fix Y, you got to test it for yourself.
 
Change some removals to Live processing only, especially when they could break Setup or dont allow them to be removed.

I dont and wouldnt remove DISM or anything related to it where you can service an image either with the tool or DISM with the command line because i guarantee the user will use the resultant build for image servicing at some point.

Gaming and Barebones type presets can be a downright menace when combined with users impatience and lack of experience. They see Xgb installed or iso size of Xgb and their eyes pop forgetting that the preset creator has tested that preset over many months for their own specific needs and purposes.
Live-processing only ones are in the OOBE compatibility, unlock that after setup and remove away.
 
Back
Top