AeonX, hi, regarding Mail replied to its topic.
Regarding clean updates, since 1803 (started in 1903, then backported), a base version of the component needs to be kept for updates to work as they are Delta compressed, enabling smaller updates (compare 1607 vs 1803+ in update size).
What clean updates does without Servicing Stack compatibility is overly aggressive in regards to what's possible with updateability, basically you can also remove WinSxS itself while at it.
I am thinking of adding an option to choose on the components page:
- keep update compatibility
clean updates kept enabled, WinSxS components locked from removal as is
- remove WinSxS/Servicing Stack compatibility
enables deep cleaning not just of updates but of components as well, as it is now when servicing stack compatibility disabled
clean updates is then unnecessary, could be disabled with Custom locked
should force the removal of Windows Update and WinSxS
What do you think, would this option alleviate some confusion or create more?