Blog Post

Windows IT Pro Blog
2 MIN READ

Reducing Windows 10, version 22H2 monthly LCU package size

santoshkpatil's avatar
santoshkpatil
Icon for Microsoft rankMicrosoft
Apr 24, 2024

Editor's note 4.30.2024 – This post has been updated to add further clarity and context.

If you're using Windows 10, you're about to experience a significant increase in efficiency.

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.

With Windows 11, we optimized cumulative updates through more efficient packaging, including the removal of reverse differentials from the cumulative update package. (To understand how the update size for Windows 11 is reduced, please see How Microsoft reduced Windows 11 update size by 40%.)

Microsoft is now bringing the same functionality to Windows 10, version 22H2, thereby decreasing the size of the monthly latest cumulative update (LCU) package. This means reduced bandwidth usage, faster downloads, minimized network traffic, and improved performance on slow connections. This feature will be available starting with the April 23, 2024 optional non-security preview release.

Devices on Windows 10, version 22H2 will observe a reduction in update package size from 830 MB for the April 9, 2024 monthly security update to approximately 650 MB for the April 23, 2024 optional non-security preview release.

Whether you've been using Windows Update, Windows Update for Business, Windows Autopatch, Windows Server Update Service (WSUS), or Configuration Manager to manage updates for your Windows 10, version 22H2 devices, this transition will be seamless! Simply approve and install LCUs for your Windows 10, version 22H2 devices as you do today, and you will witness the size improvement[i].


[1] Note: If you manage Windows 10, version 22H2 installation media and have not updated that media since July 25, 2023, you may need to apply the October 10, 2023 special standalone servicing stack update before applying the April 23, 2024 or later cumulative update to that installation media.


Continue the conversation. Find best practices. Bookmark the Windows Tech Community, then follow us @MSWindowsITPro on X and on LinkedIn. Looking for support? Visit Windows on Microsoft Q&A.

Updated Apr 30, 2024
Version 3.0
  • AbhinavBajpai's avatar
    AbhinavBajpai
    Copper Contributor

    A small typo there, KB5028244 was released on July 23, 2023. Anyway, most people will understand

  • Thank you Karl-WE for the questions. We have updated the blog to answer most of your questions. You are right that the SSU is combined with LCU and you don’t need to worry about handling any workflows related to SSU on your Windows devices. Yes, the foot note is for a scenario where latest cumulative update is being applied to old Windows 10 22H2 installation media using DISM /offline /add-package.

     

  • Thank you Mabdelgayed for the question. We have updated the blog to answer your question. With WSUS-based deployment, you will be offered the April 23, 2024, or later, cumulative update and it will get installed seamlessly.

  • santoshkpatil thank you so much for the backport!

     

    Can you outline more about "serviced your image"? Do you assume that people would use older ISO or WIM without the current LCUs?

     

    About the SSU: usually they are integrated in the LCU. And before this was the case we had to apply them before the LCU. How is it here?

    Cannot we assume that this SSU will be included into the named or next LCU?

     

    Asking this as many workflows do not expect / handle the SSU anymore, which could come unexpected to provide a standalone SSU.

     

    Thank you very much! 

  • Mabdelgayed's avatar
    Mabdelgayed
    Copper Contributor

    What if i use WSUS service for windows update, will this effect if i installed this update manually on all device.