SCCM Software Update Issue

[forkies]

We have had a bit of a lapse in our windows update and have since resolved this, however we have just tried to deploy the June Cumulative Update (KB5003637) for our devices and it is coming up "Not Required". Having delved into this we have found it is because their is a prerequisite for this to have the May CU update (KB5003173) installed.

 

If we download the MSU for the May CU and install it, we can install the June CU. However, we cannot deploy the May CU via SCCM as this has been marked as Expired and Superseded by the June CU.

 

Given we have not deployed the May CU due to some issues with windows update, we are currently sitting on a OS version from March 2021 (KB5000802).

 

Has anybody else come across this issue? We cannot deploy May CU as it has expired, but we cannot deploy June CU as it requires May CU on the device.

 

Thinking of just deploying the MSU for the May CU to a device group targeted by OS version just to get the update out and then can deploy the June CU as normal.

 

Any advice would be appreciated.

TIA,

Tom

[Oaktech]

Script it with the standalone MSU or CAB file...

 

 

https://www.danielengberg.com/install-msu-powershell-specific-kb/

[Katy]

This is causing problems for a lot of ConfigMgr admins, it's been raised with Microsoft and hopefully future updates aren't going to be released marked as both requiring and superseding the previous one.

[forkies]

Thanks, found an article in the end detailing the issue as you have said. I have decided to deploy it via the MSU for the mean time in SCCM, will await the MS advice while we use the work around.

 

Thanks!

Tom

[Steve21]

Thanks, found an article in the end detailing the issue as you have said. I have decided to deploy it via the MSU for the mean time in SCCM, will await the MS advice while we use the work around.

 

Thanks!

Tom

 

Change the auto decline in sccm to a longer period rather than instant (we use 3 months) and then re-authorise the update manually in wsus and it’ll sync back to sccm on its sync

 

Steve