A Windows installation screen shows cloud and USB setup options, protected files, and x64 and ARM64 chips.
Microsoft has released another Setup Dynamic Update for Windows 11. KB5135609 is dated November 19, 2026, and applies to Windows 11, versions 25H2 and 26H2, all editions. Microsoft describes it in one line: it fixes security vulnerabilities in Windows Setup binaries and in other files Setup uses during feature updates.

Most home users won't notice it, and most of them don't need to. If you build installation media, run WSUS or plan in-place upgrades, it's worth checking, because Setup now has a newer set of files than your images may have.

A Windows installation screen shows cloud and USB setup options, protected files, and x64 and ARM64 chips. What KB5135609 actually is​

The KB page lists these installation details:

  • Applies to: Windows 11 version 25H2 and version 26H2, all editions
  • Purpose: fixes security vulnerabilities in Setup binaries and other files Setup uses for feature updates
  • Prerequisites: none
  • Restart: Microsoft says you might not have to restart after installing it. That isn't a promise that no restart will ever be needed.
  • Replaces: KB5128977
  • File information: a downloadable CSV file that opens in Notepad or Excel. Microsoft notes that the English (United States) package may contain files for other languages.

Microsoft doesn't publish CVE numbers, severity ratings, exploitation status or the names of the affected files on the page. "Security vulnerabilities" is all the detail you get. The CSV is a file list, not a security advisory, so you can't work out the threat from it.

Summary: KB5135609 is a security refresh of the Setup files for 25H2 and 26H2. It's not a cumulative update, and it's not a feature upgrade.

What the Update Catalog shows​

The Microsoft Update Catalog has separate entries for each version and architecture. Search results show "2026-11 Setup Dynamic Update for Windows 11, version 26H2 for x64-based Systems (KB5135609)" next to matching 25H2 entries. All of them are listed under the product "Windows 10 and later Dynamic Update" with the classification "Critical Updates."

PackageLast updatedSize
25H2 / 26H2, x6411/19/202618.5 MB (19,439,165 bytes)
25H2 / 26H2, ARM6411/19/202618.1 MB (18,984,792 bytes)

The x64 and ARM64 sizes are the same for both versions. The 25H2 x64 entry lists 18.5 MB (19439165 bytes), and the ARM64 entry lists 18.1 MB (18984792 bytes). The same catalog results also show a separate November 19 Setup Dynamic Update for version 26H1, KB5135185. That's a different package for a different release. It isn't covered by KB5135609.

The replacement chain​

KB5135609 replaces KB5128977, which arrived only weeks earlier. Neowin's coverage listed it as "KB5128977: Setup Dynamic Update for Windows 11, versions 25H2 and 26H2: October 28, 2026," with the same security-focused description. WindowsForum's earlier coverage of that release showed that KB5128977 itself replaced KB5127216.

So that's two security-focused Setup Dynamic Updates for 25H2/26H2 in about three weeks. If your media-refresh routine runs monthly, it already covers this. If you refresh "when we get around to it," it probably doesn't.

Microsoft only says that KB5135609 replaces KB5128977. Don't read that as "replaces every earlier Setup Dynamic Update." The KB page doesn't say that.

Where Setup Dynamic Updates fit in a feature update​

Microsoft's deployment documentation on Microsoft Learn explains how Dynamic Update works. When a feature update starts, whether from media or through Windows Update, Dynamic Update is one of the first steps. Setup contacts a Microsoft endpoint, downloads the Dynamic Update packages and applies them to the installation media. Microsoft lists five kinds of package:

  1. Updates to Setup.exe and other files Setup uses for feature updates. KB5135609 is this kind.
  2. Safe OS updates for the Windows Recovery Environment (WinRE)
  3. Servicing stack updates needed to finish the feature update
  4. The latest cumulative (quality) update
  5. Drivers that manufacturers have published specifically for Dynamic Update

KB5135609 covers only the Setup category. It does not refresh WinRE. Safe OS updates are separate packages. NinjaOne's KB catalog, for example, lists KB5132060 as a Safe OS Dynamic Update that improves WinRE and applies to all editions of Windows 11 25H2 and 26H2, among others. If you're servicing an image, you need both kinds of package.

Summary: Internet-connected upgrades pick up Setup Dynamic Updates by themselves. Offline media only gets them if you add them.

How to get it: three channels​

The KB page lists three distribution channels, all marked available:

  • Windows Update: downloads and installs automatically. Home users and unmanaged PCs don't need to do anything.
  • Microsoft Update Catalog: the standalone package for manual download or for media servicing.
  • Windows Server Update Services (WSUS): syncs automatically if WSUS is set to Product: Windows 11 and Classification: Update.

A WSUS labeling mismatch worth checking​

The product and classification labels don't match between sources. The KB page tells WSUS admins to sync Windows 11 / Update. The Catalog lists the package as Windows 10 and later Dynamic Update / Critical Updates. The evidence available doesn't show which metadata your WSUS server will actually use. If this package doesn't appear after a sync, check that your product and classification selections cover both labels before you blame the network.

Refreshing installation media: the procedure and where it goes wrong​

Microsoft's Learn guide gives the full media-servicing process, with sample PowerShell scripts. Some environments can't reach Microsoft's servers during Setup. In that case, Microsoft says you can still do a media-based feature update by downloading the Dynamic Update packages and applying them to the image before Setup runs. A short version for Setup Dynamic Updates:

  1. Get matching packages. Download the Setup Dynamic Update, the Safe OS Dynamic Update and the latest cumulative update from the Catalog. Microsoft advises using packages from the same month as the cumulative update. If a Setup or Safe OS Dynamic Update isn't available for that month, use the most recent version of each.
  2. Work on a copy. Microsoft's script copies the original media to a new folder, so you can start over from a known state if something fails.
  3. Service WinRE, the install.wim editions and WinPE (boot.wim) in Microsoft's order. Apply the latest cumulative update last on each image. Starting with Windows 11 24H2, some cumulative updates require checkpoint cumulative updates to be installed first.
  4. Add the Setup Dynamic Update late in the process. It's step 26 in Microsoft's sequence. It simply copies the individual files in the Setup Dynamic Update package to the new media. The package isn't installed with DISM. Its files are copied onto the media.
  5. Replace setup.exe, setuphost.exe and the boot manager files with the versions you saved from the serviced WinPE image.

Common failure points​

  • Mismatched Setup binaries. Microsoft warns that if the setup.exe and setuphost.exe in boot.wim don't match the copies in the media's \sources folder, Windows Setup will fail during installation. Saving setuphost.exe is required starting with Windows 11 24H2.
  • Failed tasks. Microsoft says to resolve each task failure before moving on, and not to distribute images from failed tasks.
  • Image cleanup errors. Installing Optional Components or .NET offline creates pending operations that make cleanup fail. Microsoft's script installs them after cleanup and before export.

Controlling Dynamic Update in Setup​

Windows Setup's /DynamicUpdate switch accepts Enable, Disable, NoDrivers, NoLCU and NoDriversNoLCU. For example, setup /auto upgrade /dynamicupdate disable turns off all Dynamic Update operations. If you disable it, your media has to already contain current packages like KB5135609. This is general Setup behavior. Microsoft doesn't require a specific command to install this KB.

Who should care?​

  • Home users: Windows Update handles it automatically.
  • IT admins using WSUS or update management tools: make sure the package syncs, keeping the labeling mismatch in mind.
  • Image builders and deployment teams: refresh your 25H2 and 26H2 media. If you service media on a regular schedule, this is the main reason to act.
  • Security teams: with no CVE details published, there's no way to rank this fix by severity. Treat it as a routine but real security update to the upgrade path.

Patching the installer isn't the most exciting job, but Setup runs with high privileges on every PC it upgrades.

 

References

  1. KB5135609: Setup Dynamic Update for Windows 11, versions 25H2 and 26H2: November 19, 2026 | Microsoft Support Microsoft Support 2026-11-19T00:00:00+00:00
  2. Microsoft released Windows 11 KB5128977, KB5130881 setup & recovery updates - Neowin neowin.net
  3. Microsoft Update Catalog catalog.update.microsoft.com