KB5094135: The Servicing Stack Update Bundled With June 2026’s Windows 11 Patch — What It Is and When It Matters

If you see KB5094135 in your Windows Update history but never explicitly installed it, that is not a mistake. It installed automatically — silently, correctly, and exactly as intended.

KB5094135 is a Servicing Stack Update released June 9, 2026 for Windows 11 versions 25H2 and 24H2. Microsoft bundled it inside KB5094126 — the June 2026 Patch Tuesday cumulative update — so it installs as part of that package without requiring any separate action.

For most users, KB5094135 requires nothing. For IT administrators managing enterprise deployments, understanding what it is and how it fits into the update chain is worth knowing.

What Is KB5094135?

KB5094135 is a Servicing Stack Update — commonly abbreviated SSU — for Windows 11 versions 25H2 and 24H2. It updates the servicing stack to version 26100.8648.

The servicing stack is the set of Windows components responsible for installing, updating, and removing updates. Think of it as the machinery inside Windows Update — not the content of any particular update, but the delivery mechanism that makes all updates possible.

When Microsoft ships a servicing stack update, it improves the reliability of future update installations, fixes bugs in the update delivery process, and ensures that upcoming update packages can install correctly. Without a current servicing stack, some updates will fail to install regardless of how correct everything else is.

KB5094135 is the June 2026 version of that servicing stack maintenance for Windows 11 25H2 and 24H2.

Why Is KB5094135 Bundled With KB5094126?

Previously, servicing stack updates shipped separately from cumulative updates. This created a recurring problem — systems would attempt to install the cumulative update before the servicing stack update, causing installation failures. The required order (SSU first, then cumulative update) was documented but frequently not followed.

Microsoft’s solution was to bundle the SSU inside the cumulative update package. When you install KB5094126, the installer automatically extracts and applies KB5094135 first as part of the same process, before the cumulative content installs. The ordering problem is eliminated by removing the ordering decision entirely.

Microsoft’s own documentation for KB5094126 confirms this relationship, listing KB5094135 explicitly in the file manifest: “For a list of the files provided in the servicing stack update, download the file information for the SSU (KB5094135) — version 26100.8648.”

This is the same design principle behind KB5043080 — the September 2024 checkpoint update that became a permanent prerequisite for all subsequent Windows 11 updates. The difference is that KB5043080 remains a separate prerequisite that must be installed before other updates, while KB5094135 is embedded inside KB5094126 and installs transparently.

Which Windows Versions Does KB5094135 Apply To?

KB5094135 applies specifically to Windows 11 versions 25H2 and 24H2. Each major Windows version has its own corresponding SSU for the June 2026 update cycle.

If you are managing Windows 11 23H2 or Windows 10 systems and see KB5094135 referenced in documentation, those systems received a different SSU as part of their respective June 2026 updates.

Do You Need to Do Anything About KB5094135?

For home and standard office users — no.

If KB5094126 installed successfully through Windows Update, KB5094135 is already on your system. Check Settings, Windows Update, Update History and you will see both KB5094135 and KB5094126 listed with Successfully installed status, both dated June 9, 2026.

You can also verify via PowerShell. Open PowerShell as administrator and run:

powershell

Get-HotFix -Id KB5094135

If it returns installation details, the SSU is present. If it returns nothing, KB5094135 did not install correctly alongside KB5094126.

When KB5094135 Matters Separately

There are specific scenarios where KB5094135 becomes relevant as a distinct component.

Enterprise deployment via WSUS or Configuration Manager

When deploying updates through WSUS or Microsoft Configuration Manager, SSU packages can sometimes be approved, deployed, or superseded independently of the cumulative update they were bundled with. IT administrators should verify that KB5094135 is not blocked or incorrectly superseded in their WSUS configuration in ways that would prevent it from installing alongside KB5094126.

If 0x80244022 or other update errors are appearing on managed devices after June 2026, checking whether KB5094135 installed correctly is one diagnostic step in the troubleshooting chain.

Windows image creation

Organizations building custom Windows installation images for deployment need to ensure KB5094135 is incorporated into the image alongside KB5094126. An image built with KB5094126 content but without KB5094135 correctly applied may encounter failures when subsequent updates attempt to install.

Troubleshooting later update failures

If a subsequent update — such as the June 23 preview KB5095093 or the July Patch Tuesday KB5101650 — fails to install after June 2026, verifying that KB5094135 installed correctly as part of KB5094126 is worth checking. A missing or failed SSU installation can produce update failures that appear unrelated to the servicing stack.

How KB5094135 Relates to the Broader June 2026 Update Chain

KB5094135 sits at the base of the June 2026 update sequence for Windows 11 25H2 and 24H2.

KB5043080 — the September 2024 checkpoint update — is the prerequisite that must already be present before KB5094126 (and therefore KB5094135) can install. KB5094135 then becomes part of the foundation that KB5095093 and KB5101650 build on in subsequent months.

The chain looks like this:

KB5043080 (prerequisite checkpoint) comes first. KB5094126 with bundled KB5094135 follows. KB5095093 (June 23 optional preview) builds on that. KB5101650 (July Patch Tuesday) completes the sequence.

Each layer depends on the layers beneath it. KB5094135 is one of those foundational layers — invisible in normal operation, critical when something goes wrong.

Can KB5094135 Be Uninstalled?

No. Like all servicing stack updates, KB5094135 cannot be removed after installation.

The SSU becomes part of Windows’ update infrastructure once installed. Running the Windows Update Standalone Installer with the /uninstall switch will not work. Attempting DISM /remove-package on the SSU component will also not work — Microsoft does not provide an uninstallation path for servicing stack components.

If you need to revert to a system state before KB5094135, restoring a complete system image from before June 9, 2026 is the only path.

Additionally, because KB5094135 is bundled within KB5094126, the standard caution applies: running Windows Update Standalone Installer with /uninstall on the combined package targets the cumulative update, not the SSU. The SSU cannot be removed even by uninstalling KB5094126.

Frequently Asked Questions