Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Starting with Windows 11, version 24H2, checkpoint cumulative updates might precede monthly security updates and optional non-security preview updates. However, update processes involving Windows Update and Windows Server Update Services (WSUS) remain unchanged. This article covers how you can use Microsoft Update Catalog to easily update your devices (or images) through checkpoint cumulative updates.
Note
General users in non-IT-managed settings get these updates automatically from the Windows Update channel. This article is intended for IT admins.
Checkpoint cumulative updates
Starting with Windows 11, version 24H2, monthly cumulative updates use a differential model. Each monthly update carries only the changes since the most recent checkpoint. This change means that the checkpoint update must be present on the device before you can install the target update.
This change allows you to get features and security enhancements via the latest cumulative update through smaller, incremental updates. This way, you can save time, bandwidth, and hard drive space.
Microsoft periodically releases cumulative updates as checkpoints. The subsequent updates consist of multiple files:
- The update package files associated with the checkpoints
- New update package files that contain incremental binary differentials against the version of binaries in the last checkpoint
This process might be repeated multiple times, thereby generating multiple checkpoints during the lifecycle of a given Windows release. Applicable Windows servicing stack can merge all the checkpoints and only download and install content that's missing on the device, especially via Windows Update or WSUS.
If any checkpoint cumulative updates precede a target update, a device or image needs to install all prior checkpoint cumulative updates before it can install the target update. In other words, a post-checkpoint latest cumulative update can be applied to images/devices that are on that checkpoint or on a subsequent latest cumulative update. For updates sourced from Windows Update and WSUS, this process happens seamlessly. You can continue to use the same tools and processes that you currently use for approving and deploying updates. Updating through a checkpoint cumulative updates positions you to efficiently install future checkpoint cumulative updates.
Applicability
A checkpoint cumulative update is just another monthly cumulative update that informs how subsequent updates are built. There's no policy change or new requirement for when users must install these updates. However, it's a best practice to install monthly security updates at the earliest opportunity to keep your devices protected and productive.
Update Windows installation media
This feature doesn't introduce any change to the applicability of monthly security updates. As before, these updates apply to the main OS (install.wim) and to WinPE (boot.wim) but not to WinRE (winre.wim).
WinRE is serviced by applying the servicing stack update from a cumulative update (latest cumulative update doesn't apply) and SafeOS Dynamic Update. This is how it worked before the introduction of checkpoint cumulative updates. There's no change to WinRE servicing. Applying the servicing stack update followed by SafeOS Dynamic Update is the only way to service WinRE. For more information, see Update Windows installation media with Dynamic Update.
Updating from the Microsoft Update Catalog
Monthly Windows updates are available through multiple release channels. Microsoft Update Catalog is one of the channels available to IT-managed organizations and general users. It's listed in the release notes of each Windows security and non-security update, documented on Windows 11 update history pages. You can find it under the heading "How to get this update" on each release note. That section explains how to install this update depending on your selected release channel.
To use Microsoft Update Catalog to install a given monthly cumulative update, first determine and download the prior checkpoint cumulative updates. Then choose from two methods to install update files individually and sequentially or all at once.
Finding prior checkpoint cumulative updates
Begin by searching the Microsoft Update Catalog for the KB number corresponding to the desired Windows update. You can find the KB number at the top of each release note on the Windows update history pages for your Windows version (for example, "KBxxxxxxx"). On the search results page, select the option that matches your device architecture (arm64 or x64), and then choose Download.
The download pop-up shows all prior checkpoints for the update so that you can conveniently download all .msu files and install them on your image or device. For example, Microsoft Update Catalog shows the July 2026 cumulative update (KB5101650) has one preceding checkpoint cumulative update, KB5043080.
Installing checkpoint cumulative updates
Checkpoint cumulative updates are available for Arm64 and x64 architectures. Standalone packages for most updates under each KB identifier contain multiple .msu files that require installation in a specific order.
You can install this update by installing all .msu files together (method 1) or by installing each .msu file individually, in order (method 2).
| Capability | WUSA | DISM |
|---|---|---|
Install an .msu package |
Yes | Yes |
| Install on a running OS | Yes | Yes |
| Install an offline image | No | Yes |
| Automatically discover required checkpoint cumulative updates in a package folder | No | Yes |
Method 1: Install all .msu files together
This method automates the appropriate sequencing of all the .msu files for you. For each desired update, take the following steps:
- Download all
.msufiles for the KB corresponding to the desired update from Microsoft Update Catalog. - Place them in the same folder (for example, C:/Packages).
- Use Deployment Image Servicing and Management (DISM.exe) to install the target update with the desired KB number in the name.
DISM uses the folder specified in PackagePath to discover and install all of the .msu files in the correct order.
Note
The command examples in this article use the following placeholders:
- [KB Identifier] - The KB number of the target update (in the format of "KBxxxxxxx")
- [architecture] - Type of processor, specifically [arm64] or [x64]
- [UpdateID] - The unique identifier assigned to the update by the Microsoft Update Catalog
Updating Windows PC
To install this update to a running Windows PC, choose one of the following actions:
Run the following command from an elevated Command Prompt:
DISM /Online /Add-Package /PackagePath:c:\packages\windows11.0-[KB Identifier]-[architecture]_[UpdateID].msuRun the following command from an elevated Windows PowerShell prompt:
Add-WindowsPackage -Online -PackagePath "c:\packages\windows11.0-[KB Identifier]-[architecture]_[UpdateID].msu"
Important
Don't use Windows Update Standalone Installer. It's not fully supported for this method.
Updating Windows Installation media
To install this update to Windows Installation media, see Update Windows installation media with Dynamic Update.
Note
When downloading other Dynamic Update packages, ensure that their month matches the month of the KB for the update you want to install. If the SafeOS Dynamic Update or Setup Dynamic Update isn't available for the same month as this KB, use the most recently published version of each. All Windows updates are cumulative.
To add this update to a mounted image, run a command from an elevated Command Prompt or an elevated Windows PowerShell prompt:
Elevated Command Prompt:
DISM /Image:mountdir /Add-Package /PackagePath:Windows11.0-[KB Identifier]-[architecture].msuElevated Windows PowerShell prompt:
Add-WindowsPackage -Path "c:\offline" -PackagePath "Windows11.0-[KB Identifier]-[architecture].msu" -PreventPending
Method 2: Install each .msu file individually, in order
This method requires you to install all the .msu files sequentially, with the checkpoint update file first. Use DISM or the Windows Update Standalone Installer.
Download and install each .msu file individually by using either DISM or the Windows Update Standalone Installer in the following order:
- Checkpoint cumulative update: windows11.0-[KB Identifier]-[architecture]_[UpdateID].msu
- Latest cumulative update (LCU): windows11.0-[KB Identifier]-[architecture]_[UpdateID].msu
Tip
When you search the Microsoft Update Catalog for the target KB and select your architecture, the download pop-up lists any preceding checkpoint cumulative updates alongside the target update. You can download all .msu files in a single step.
Customization scenarios with checkpoint cumulative updates
The following considerations apply to devices that require customization.
Device has the latest checkpoint cumulative update and doesn't need customization
This scenario involves devices or images that have the latest checkpoint cumulative update installed and don't need Features on Demand (FoD) or language pack customization. Update these devices to the latest target cumulative update with no change to your existing process. You can copy the target .msu file from Microsoft Update Catalog and install it by using Add-WindowsPackage (DISM) or DISM operating system package (.cab or .msu) servicing command-line options.
Examples of eligible devices:
| Device is on | Needs to install |
|---|---|
|
|
|
|
Device needs FoD or language pack customization
Installing FoDs or language packs requires the full cumulative update payload. Sometimes, it can be split across files associated with each preceding checkpoint cumulative update. To customize FoDs or language packs for offline media, install all prior checkpoint cumulative updates and the target cumulative update regardless of whether the device already had any of the prior checkpoint cumulative updates installed. You must use DISM to do this.
- Copy the
.msufiles of the latest cumulative update (the target) and all prior checkpoint cumulative updates to a local folder. Ensure that there are no other.msufiles present. - Mount the
install.wimfile. - Run
DISM /add-packagewith the latest.msufile as the sole target. - Run
/Cleanup-Image /StartComponentCleanup. - Dismount.
- Optional: Run
DISM /export-imageto optimize the image size.
Device doesn't have the latest checkpoint cumulative update and doesn't need customization
Devices that aren't on the latest checkpoint cumulative update and don't need FoD/language pack customization can use one of the two installation methods described in Installing checkpoint cumulative updates.
If there are four total checkpoint cumulative updates available and the device already has the first one installed, DISM installs only the updates needed and in the correct order.