Blog Post

Windows IT Pro Blog
3 MIN READ

Windows 10 quality updates explained and the end of delta updates

Mike Benson's avatar
Mike Benson
Icon for Microsoft rankMicrosoft
Jul 11, 2018

Update 2/5/2019: Based on customer feedback, we are extending Delta update publication for Windows 10 versions 1607, 1703, 1709, and 1803. We will continue to provide Delta updates via the Microsoft Update Catalog through April 9th, 2019, which will be the last delta update available.


With Windows 10, quality updates are cumulative. Installing the most recent update ensures that you receive any previous updates you may have missed. We used a cumulative update model to reduce ecosystem fragmentation, and to make it easier for IT admins and end users to stay up to date and secure. However, cumulative updates can prove challenging when it comes to the size of the update and the impact that size can have on your organization’s valuable network bandwidth.

When a new Windows 10 feature update is released, the first cumulative update is generally between 100-200 MB in size. Across all versions of Windows 10, cumulative updates grow as additional components and features get serviced, pushing the size to somewhere between 1-1.2 GB. Generally, this happens within the first 6-8 months after the release of a feature update.

To help you reduce the burden on your network bandwidth, yet still receive the same equivalent update, Microsoft designed three different update types:

  • Full updates have all the necessary components and files that have changed since the last feature update. We refer to this as the latest cumulative update, or LCU. It can quickly grow to a little over 1 GB in size, but typically stays that size for the lifetime of that supported version of Windows 10.
  • Express updates generate differential downloads for every component in the full update based on several historical bases. For example, the latest May LCU contains tcpip.sys. We will generate a differential for all tcpip.sys file changes from April to May, March to May, and from the original feature release to May. A device leveraging express updates will use network protocol to determine optimal differentials, then download only what is needed, which is typically around 150-200 MB in size each month. Ultimately, the more up to date a device is, the smaller the size of the differential download. Devices connected directly to Windows Server Update Services (WSUS), System Center Configuration Manager, or a third-party update manager that supports express updates will receive these smaller payloads.
  • Delta updates include only the components that changed in the most recent quality update. Delta updates will only install if a device already has the previous month’s update installed. For example, assume in May that we changed tcpip.sys and ntfs.sys, but did not change notepad.exe. A device that downloads the delta update will get the latest version of tcpip.sys and ntfs.sys, but not notepad.exe. Delta updates include the full component (not just the individual files) that changed. As a result, they are larger than express updates, often around 300-500 MB in size.

Regardless of which type of update is installed on a device, that update is fully cumulative and installing the latest update will ensure that the device has all the necessary quality and security improvements.

This raises an important question: why make delta updates available if express updates are more optimized and don’t require the previous month’s update already be installed? Delta updates were originally created because the express update protocol was only available to devices connecting directly to Windows Update or Windows Server Update Services. In January 2017, the express protocol was extended to all 3rd party update management systems; however, we continued to ship delta updates to give companies and third-party update management tools time to implement support for express updates.

Currently delta updates are available for the following versions of Windows 10:

  • Windows 10, version 1607
  • Windows 10, version 1703
  • Windows 10, version 1709
  • Windows 10, version 1803

Now that express update support for third-party update managers has been available for over a year, we plan to stop shipping delta updates. Beginning February 12, 2019 Microsoft will end its practice of creating delta updates for all versions of Windows 10. Express updates are much smaller in size, and simplifying the cumulative options available will reduce complexity for IT administrators.

For more information on optimizing update bandwidth and more details about express updates, see Optimize Windows 10 update delivery. To learn more about Windows as a service, check out the new Windows as a service page on the Windows IT Pro Center.

Updated May 29, 2019
Version 3.0

60 Comments

  • wroot's avatar
    wroot
    Silver Contributor

    Well, that will take a while as i don't look after their laptop that often. But will have that in mind if i encounter this issue again.

  • Oleg,
    I don't think deleting the SoftwareDistribution folder should have had an impact.   Any chance you also enabled a language pack or feature on demand (FoD) (.NET 3.5, many others)?  Enabling language packs and features on demand triggers a new download of the quality update to make sure you have the latest language strings and any updates for the components in the FoD.

     

     

    One way to see if you have the current LCU is to look at the windows version and then compare to the release information page.  If you get into this state again it would be interesting to see what the winver is before and after you delete the SoftwareDistribution folder.

     

    https://www.microsoft.com/en-us/itpro/windows-10/release-information

     

    Mike

  • wroot's avatar
    wroot
    Silver Contributor

    Mike, but when i have deleted SoftwareDistribution folder on parents laptop it then found new CU update and installed it.

  • Hello Mike

    I see. I forgot about the branch office scenario.

    Of course, I actually am working somewhere with a branch office but that office does not use an upstream WSUS over WAN; it is cheaper to connect to the Internet than to connect to the main office. Our orders are to keep the redundant traffic off that WAN link. So, the branch office admin has a separate WSUS deployment.

     

  • Oleg,
    For your parents machine, which I'm assuming is connected directly to Windows Update, when it downloads a feature update it also downloads and installs the latest cumulative update (LCU) at the same time.  So when they upgraded to 1803, then were already fully up to date on LCU's.  

    Example:

    1803 released in April

    April patch tuesday, first 1803 LCU released (I'll call this 1804B)

    May patch tuesday, another 1803 LCU released (I'll call this 1805B)

    If your parents machine upgraded on May 22nd (one week after patch tuesday) they would download and install both the feature update and the 1805B LCU.  They would only see a single reboot, and their machine would be fully up to date.

    Mike

  • Mr. Mysterious,

    That is correct - if you enable express on WSUS, the update you download to the server is much larger (typically over 4GB in size).  Then each client that connects to WSUS gets the much smaller download size.  So it works well in scenarios where enterprises have branch offices with slower download links while their central location has a much larger pipe.

    The file is larger on WSUS because it contains all the baselines that any client could ask for, as well as all SKU's and architectures.  While the clients only download the SKU, architecture, and specific component differentials that they need.

    Mike

  • The definition you gave for "Express updates" contradicts the https://docs.microsoft.com/en-us/windows/deployment/update/waas-manage-updates-wsus. In WSUS, not only an express update is not smaller, it is significantly larger; but, allegedly, it installs faster.

     

    Of course, it is still possible that these two are the same: The update is larger for the sever, but clients download less. If that's the case, I don't use them; size matters much more on the Internet connection, not on the local network connection.

  • wroot's avatar
    wroot
    Silver Contributor

    Thanks. I think it is not isolated to WSUS only though. I had a same issue after my parents laptop has been updated to 1803. It couldn't find latest CU, although it found Flash player updates. Using Windows Update there.

  • Hello Oleg,
    Thanks for the feedback.  I'll forward your question to the folks responsible for WSUS and how we publish to WSUS.  That does sound pretty annoying.

     

    Mike

  • wroot's avatar
    wroot
    Silver Contributor

    Hey. Maybe you also will fix an issue with Windows 10 not seeing a few latest CU updates on WSUS after a feature update. This has been an issue with 1703 and newer versions (maybe even earlier). I now have a script wiping SoftwareDistribution on every startup, because i can't find any other way to make it pull the latest CU from WSUS otherwise (although WSUS shows that they are needed). This is one of the most annoying sides of "windows as a service"..

     

    P.S. this site is so bullsh. It constantly eats my comments (yeah, i had this page opened for a while, it's not a reason to fail to authenticate when posting a comment), it is HORRIBLE on mobile.