Reducing Windows 10 version 22H2 monthly LCU package size

Maxstar

Windows Update Moderator, Security Analyst
Staff member
Joined
Aug 16, 2015
Posts
14,486
Location
The Netherlands
Microsoft releases security and quality updates for Windows every month, resulting in a substantial amount of content that can quickly consume the network bandwidth of users operating on slower networks. To reduce the demands on your network, Microsoft is now taking a page from the Windows 11 playbook and reducing the size of Windows 10 update packages.

Windows 11 cumulative updates are more efficient than update packages for Windows 10. This is achieved through efficient packaging, including the removal of reverse differentials from the cumulative update package. To understand how the update size for Windows 11 is reduced, refer to How Microsoft reduced Windows 11 update size by 40%.

Microsoft is bringing the same functionality to Windows 10, version 22H2, thereby decreasing the size of the monthly latest cumulative update (LCU) package. This feature will be available starting with the April 23, 2024 (KB5036979) monthly release, which helps you and your organization to conserve network bandwidth.

Simply approve and apply the update as you would do today. Devices on Windows 10, version 22H2 will observe a dip in size from 830 MB in the April 9, 2024 (KB5036892) release to approximately 650 MB in the April 23, 2024 (KB5036979) release.

Source: Reducing Windows 10, version 22H2 monthly LCU package size
 
When you prefer a manually cleanup of the WinSxS folder you can disable the "StartComponentCleanup" task as follows:

1. Open Task Sheduler and navigate to: Library > Microsoft > Windows > Servicing.
2. Right click the "StartComponentCleanup" task and set it to disabled.
3. Then you can run the following commands manually to check and cleanup the WinSxS store if needed.

Code:
DISM /online /cleanup-image /AnalyzeComponentStore
DISM /online /cleanup-image /StartComponentCleanup

I have disabled the "StartComponentCleanup" task on most of my VM's which I'm using as source for update issues...
 
Back
Top