This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(304, 93%, 39%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDH%3C/text%3E%3C/svg%3E)
Since KB5003173 was release in May there has been an issue with current CU not including the required SSU to be installed.
Is this going to be fixed in upcoming updates? This is an issue because current updates supersedes this update but they cannot be installed as the SSU in the May update is a pre-requisite.
This is creating issues for organizations that use WSUS as current updates are downloaded to client machines from the WSUS server and fail to install because the SSU version is incorrect.
If an update is cumulative it need to include the SSU update required to install itself.
Articles for reference on the issue.
https://redmondmag.com/articles/2021/06/24/windows-security-patch-blocked.aspx
https://techcommunity.microsoft.com/t5/configuration-manager-blog/known-issue-the-june-2021-windows-10-security-update-is-reported/ba-p/2471737
Microsoft released a separate SSU yesterday that takes care of this issue.
KB5005260 - https://support.microsoft.com/en-us/topic/kb5005260-servicing-stack-update-for-windows-10-version-2004-20h2-and-21h1-august-10-2021-ec4c5daa-2cec-4b06-be93-037f150fe3ba
I have sent an email to the MVP distro list asking for an explanation. I'll reply pointing to this thread too.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(300.8, 90%, 39%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EL%3C/text%3E%3C/svg%3E)
We are also seeing this in our environment, the May CU for Windows 10 20H2 is required before the July update will install, however the July update is marked as superceding the May update, and many of our clients are no longer seeing the May update as required, and simply error out trying to load the July update.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(297.6, 24%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERH%3C/text%3E%3C/svg%3E)
@David Henderson
Thanks for your posting on Q&A.
What is the version of the clients in your environment? The clients tried to install the KB5003173 but it shown that the update isn't applicable for the computer. Am I right?
I tested it in my lab environment. The windows version is windows 10 2004. I tried to install the KB4598481 then I installed the KB5003173 successfully.
In my opinion, the SSU is integrated into the latest CUs in Windows 10 2004 and the later. There is no need to approve the SSUs for the windows 10 2004 and the later versions.
Hope the above will be helpful. Thanks for your time.
Regards,
Rita
If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
I am working with 20H2, using WSUS to distribute updates.
The issue is recent Cumulative Updates require the SSU update in the May CU KB5003173 to be installed.
Current Cumulative updates supersedes previous updates.
When clients attempt to update to the current update they receive error 0x80242017.
If you have a client that is behind on updates for any number of reasons, new install, recently updated to feature update, or offline for another reason and it scans against WSUS for updates it will see the current CU from July, on installation attempt it will fail. The May CU is also approved, but the July update supersedes this update so the client will only attempt to install the July update.
@David Henderson
Thanks for your feedback.
According to this link, we have to install the May 11, 2021 update (KB5003173) before we install the latest cumulative update:
Please try to install the KB5003173 Cumulative Update first and then we could try to install the latest Cumulative Update.
Note that we may need to install KB4598481 before installing the KB5003173 due to my lab test.
In additioin, I found a related link for your reference.
Hope the above will be helpful.
Regards,
Rita
If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
I am aware of the prerequisite, but that is the problem.
When using WSUS to distribute updates it is not possible to require an update that is superseded without marking the newer updates as Not Approved.
This is an issue when you have no way of targeting devices that need this pre-requisite while also providing the current update.
KB5005260 was released as an SSU Update.
Method 3: Windows Server Update Services
This update is also available through Windows Server Update Services (WSUS).