Fix the SCCM Patch Deployment issue with Windows Cumulative Updates. Let’s discuss the SCCM Patch Deployment issue with Windows 10 or Windows 11 Cumulative Updates.
The July cumulative update KB5004245 for Windows 10 1909 might also have similar ConfigMgr (a.k.a SCCM) patching issues.
Since the last two months, Microsoft has started deviating from the standard they introduced a while back to combine Windows SSUs and LCUs. This is what we can notice with June and July cumulative updates for Windows 10. This is causing problems/confusion for IT admins.
➡️SCCM Patch Software Update Deployment Process Guide.
SCCM admins faced a similar issue with last month’s cumulative update KB5003637 as well. The scenario becomes more critical when you have configured to Decline superseded updates immediately policy. We have a post where we discussed the issue with June CU for Windows 10.
- Fix Windows Update Issues For Windows 11 Errors Troubleshooting Tips HTMD Blog (anoopcnair.com)
- Fix Windows Update Error 0x8007005 Failed To Restart
- Windows Upgrade Troubleshooting with Logs
- Enable Windows 11 Patching using SCCM WSUS
- Upgrade to Windows 11 using Intune Feature Update Deployment Policy
SCCM Patch Deployment issue with Windows Cumulative Updates ConfigMgr
Let’s check the prerequisite for deploying Windows 10 July CU KB5004237. This prerequisite is only applicable for WSUS/SCCM patch deployment scenarios. Don’t worry about this if you are using WUfB/Intune to deploy patches.
NOTE! – The July CU KB5004237 is applicable for Windows 10 2004, 20H2, and 21H1.
As mentioned above, the latest servicing stack update (SSU) for your operating system should be part of the latest cumulative update (LCU). You don’t need to install it separately. But, this is not true with June and July 2021 cumulative updates.
Issue: The prerequisite for WSUS/SCCM patch deployment is installing the May 11, 2021 update (KB5003173) before installing the latest cumulative update, KB5004237.
If you have not installed KB5003173, then the CU patch deployment of July month might fail or give inconsistent reports like “this” patch is not applicable for “this” Windows version. You need to ensure that all the devices are already installed with KB5003173 before installing the July CU update (KB5004237) for Windows 10 2004, 20H2, and 21H1.
Fix SCCM Patch Deployment issue with Cumulative Updates
The latest cumulative update for Windows 10 1909 version kb5004245(July CU) and this patch also has a dependency on previous cumulative patches and SSU. The prerequisite for Windows 10 1909 July CU (kb5004245) is a bit more complex than the previous releases.
You must install either of the following before installing the July cumulative update (LCU) for 1909. Otherwise, the SCCM patch installation will fail, or the reports will show the LCU for July is not applicable, etc.
- Servicing stack update (SSU) (KB5001406)
- Latest SSU (KB5004748)
Recover Expired Updates from SCCM/WSUS
Let’s learn how to recover Expired Updates from the ConfigMgr console. The SCCM patch management is not very easy if you are new to this process. I have a blog post that talks about an end-to-end process of the recovery of expired updates.
SCCM Recover Expired Updates from Admin Console | ConfigMgr
Anoop C Nair is Microsoft MVP! He is a Device Management Admin with more than 20 years of experience (calculation done in 2021) in IT. He is Blogger, Speaker, and Local User Group HTMD Community leader. His main focus is on Device Management technologies like SCCM 2012, Current Branch, and Intune. He writes about ConfigMgr, Windows 11, Windows 10, Azure AD, Microsoft Intune, Windows 365, AVD, etc.
2 thoughts on “SCCM Patch Deployment issue with Windows Cumulative Updates ConfigMgr”
the new update KB5004237 does not install on my laptop and give an error saying some files may be missing and the code is 0x8007000d. how do i sort this out. please help
There is a reddit thread with this and we are experiencing this issue on about 1% of our computer population that we’ve applied the update so far. We have a case open with Microsoft so far, but no progress.