If you use Windows Server Update Services (WSUS) to manage and deploy your monthly cumulative updates, you must install the May 11, 2021 update (KB5003173) before you install the latest cumulative update.
Microsoft now combines the latest servicing stack update (SSU) for your operating system with the latest LCU. For general information about SSUs, see Servicing stack updates and Servicing Stack Updates (SSU): Frequently Asked Questions.
So KB5003637 (June) cannot be applied over KB5001330 (April). KB5003173 (May) must be applied first. This means that KB5003173 can’t really be superseded as in past procedure, and it should be set as a prerequsite for relevance of KB5003637.
This will also occur in the future any time Microsoft includes a new SSU in the previous month’s cumulative update.
we have given a Note in the fixlets which mentions about the Pre-requisites to be installed.
Regarding not superseding the May update, I believe it is not correct since MS also mentions the same and we may end up in getting few more queries from users asking why the Fixlet is not yet superseded.
we can suggest to add below supersedence setting which makes any applicable superseded patches relevant to endpoints
_BESClient_WindowsOS_EnableSupersededEval=1
Thank you for responding! Your efforts in keeping up with Microsoft’s monthly changes are appreciated.
Microsoft is no longer releasing the SSU separately from the Windows CU. So there is no way to install KB5003637 (June) without first installing KB5003173 (May), because the SSU that is contained in KB5003173 (May) is necessary to install KB5003637 (June).
So if a machine’s last patch is KB5001330 (April), then what should be relevant is KB5003173 (May).
If a machine has KB5003173 (May), what should be relevant is KB5003637 (June).
It is not helpful to make KB5003637 (June) relevant on a machine that only has KB5001330 (April), because it fails if you try to install it.
It is not helpful to supersede KB5003173 (May) with KB5003637 (June) because KB5003173 (May) must be installed first.
I’m also still digging in to this, and the new behavior seems specific to Windows 10 build 21H1.
For Windows Server and earlier versions of Windows 10, the standalone MS21-JUN Servicing Stack Update (SSU) KB5003711 still seems to be the correct prerequisite.
4. Why are the 20H2 and 2004 rows no longer included in the table?
The Windows 10 20H2 and Windows 10 2004 Security Stack Update is included in the Update Package as of the March 2021 release. If you have not yet updated to the current release, the previous Security Stack Update for these versions is KB4598481. This version needs to be installed before updating to the March 2021 update.
So for version 1909 and older (and corresponding Windows Server versions), there is still a SSU. But 2004 (AKA 20H1) and newer have the SSU rolled into the CU.
We are all used to the indeterminate time taken for a ‘Microsoft Minute’ when copying files.
Perhaps we have to also become used to the indeterminate meaning of ‘cumulative’ because some cumulative updates are dependent upon a previous update being applied.