Request for (automatic) obsolete Service Stack detection

pmikep

Active Member
It seems that Microsoft updates the Service Stack for Win10 from time to time.

For example, here's a new SS that I downloaded tonight while updating a fresh 1909 iso.

Capture037.jpg

If one has downloaded updates to Win10 in NTLite from, say, August, and then does another update check in November. the new SS is downloaded, but, if one does not use NTLite's Trim function to delete old/obsolete KB's, then the old SS is kept in the update folder too.

Capture038.jpg

The first time I saw this, I was tempted to keep both Service Stacks because I'm using to NTLite flagging problematic KB's in red.

I presume that it is not good to have two SS KB's. But when I do a manual Trim, then the old one goes away.

So is there a way that NTLite can flag the older, presumably obsolete SS in this list? (Perhaps because NTLite sees the same string "Service Stack"?)

Or should NTLite do an "auto-Trim" before looking for Updates to keep this from happening?
 
Hi,

yes, it can do that, and it's a good idea. You can check how NTLite unchecks other cumulative updates, including .NET, if a user selects more than one.

Reason why servicing stack wasn't done in that first batch is because in Win7 there is an old stack that is needed as a pre-requisite, so that made me think maybe people might need more freedom in integrating multiple ones.
Now after some more thought I realize that it's best to filter out those as well and handle this one exclusion.

Will do for next, to allow only one stack selection, and newest is selected by default.
As for easier trimming and flagging obsolete updates, that would be nice as well, will add to the list, but it might wait depending on the sequence of other tasks.
Easiest, and would clarify a lot, is to dim or separate the "External" updates, those are the obsolete + unknown/user.

On it, sir.
 
Done in 7742, do you like the external update separation, any suggestions?
 
Back
Top