Do you see, the SCCM patching issue with Windows 10 KB5003637 June Cumulative Update? If so, you are not alone. The entire MEM community is struggling with this if you have configured to Decline superseded updates immediately policy.
Most of the time, the patch Tuesday comes with many issues for IT Pros/IT Admins. But after a recent announcement from Microsoft, they started deploying Windows SSUs and LCUs together with one cumulative update for Windows 10.
Microsoft MVP Bryan Dam explains this issue in the Twitter thread with all the details. Well, it’s not a good situation when May month’s CU is a prerequisite for June month’s CU.
Issue with Windows 10 KB5003637 Patching
Microsoft announced that they would combine the latest servicing stack update (SSU) for your operating system with the latest cumulative update (LCU). But, there is some confusion about June 2021 LCU patch KB5003637 that it has a prerequisite that the May 2021 CU KB5003173 must be installed.
You might face Windows 10 KB5003637 installation issues: 1. when your device didn’t install, the cumulative update for May (KB5003173), and 2. You have enabled the following policy in your SCCM / Configuration Manager / WSUS.
NOTE! – The Supersedence behavior is set to immediately expire a superseded software update. This is applicable for WSUS-related patching also.
Fix SCCM Patching Issue with Windows 10 KB5003637
If you see SCCM patching issue with Windows 10 KB5003637 LCU, you need to make sure that Windows 10 device has KB5003173 CU installed. Otherwise, try to push the standalone SSU that is required for KB5003637.
The best option from my perspective is to wait for Microsoft to come back with a clearer answer for a subset of systems. I assume you might not have a larger percentage of systems with this issue. Or raise a ticket with Microsoft support to get an official answer from them.
Resources
- Windows 10 21H1 Patch KB5003637 | June 2021 | Intune | Outlook | Excel | 3D Paint | Defender | Remote Desktop | Microsoft Edge
Author
Anoop is Microsoft MVP! He is a Solution Architect in enterprise client management with more than 20 years of experience (calculation done in 2021) in IT. He is a blogger, Speaker, and Local User Group HTMD Community leader. His main focus is on Device Management technologies like SCCM 2012, Current Branch, and Intune. E writes about ConfigMgr, Windows 11, Windows 10, Azure AD, Microsoft Intune, Windows 365, AVD, etc…
Interesting I was in the process of creating a fresh 20H2 image WIM file for enterprise injecting KB5003637 cab file with Add-WindowsPackage came back with an error.
“Package_for_RollupFix~31bf3856ad364e35~amd64~~19041.1052.1.13” requires Servicing Stack v10.0.19041.903 but current Servicing Stack is v10.0.19041.740
Downloaded the KB5003637 MSU from the catalogue then extracted , it split the files to SSU-19041.1022-x64.cab and Windows10-KB5003637-x64.cab. I was then able to install the SSU first with the above commands then the CU.
Thank you for posting this information, I’ve had a few devices with this issue and was head scratching a little as to why the June update wouldn’t appear.
Deployed May, installed & June CU appeared very shortly after a check-in!