/build/static/layout/Breadcrumb_cap_w.png

Cumulative Updates for 20H2 Marked Superseded, when it's required due to the built in Servicing Stack Update.

Feb and May's Cumulative Update for 20H2 Marked Superseded, when it's required due to the built in Servicing Stack Update.

This has caused PCs that missed out on Feb or May's Cumulative update to fail when installing Cumulative Updates for March, April, June, July.


Is there a recommended approach for tacking this dilemma now that the SSU is included in Cumulative Updates?    (Thanks Microsoft!).


0 Comments   [ + ] Show comments

Answers (1)

Posted by: bbarnard 3 years ago
White Belt
1

Microsoft indicates the following concerning 20H2 and 21H1 post 2021-05 Cumulative Updates.


Before installing this update


Microsoft now combines the latest servicing stack update (SSU) for your operating system with the latest cumulative update (LCU). For general information about SSUs, see Servicing stack updates and Servicing Stack Updates (SSU): Frequently Asked Questions.


Prerequisite:


For Windows Server Update Services (WSUS) deployment:


Install the May 11, 2021 update (KB5003173) before you install the latest cumulative update.


For offline Deployment Image Servicing and Management (DISM.exe) deployment:


If an image does not have the February 24, 2021 (KB4601382) or later cumulative update, install the January 12, 2021 SSU (KB4598481) and the May 11, 2021 update (KB5003173).


https://support.microsoft.com/en-us/topic/july-13-2021-kb5004237-os-builds-19041-1110-19042-1110-and-19043-1110-ae798d3c-3de3-4c1f-b9d9-7391b71da889


I am currently leaving KB4598481 and KB5003173 active in KACE in order to push out the newer CUs, although it isn't a perfect solution.

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ