Why an SSU Refuses to Install Standalone via wusa on Windows 11

You try to install a Servicing Stack Update SSU standalone using wusa.exe on Windows 11 and get error 0x800f0826 or a message that the update is not applicable. This happens because SSUs have a special dependency chain that wusa.exe does not resolve automatically. This article explains the technical reason for the failure and shows you the correct methods to install the SSU.

Servicing Stack Updates prepare the Windows Update components to accept the latest cumulative updates. Unlike a standard cumulative update, an SSU requires a minimum baseline version of the servicing stack already present on the system. When you run wusa.exe on the .msu file, it checks the current servicing stack version and refuses to install if the baseline is not met. The fix involves either installing the prerequisite SSUs in order or using DISM with the /Source parameter to bypass the version check.

You will learn the exact dependency rule that causes the failure and three reliable workarounds: installing SSUs sequentially, using DISM offline servicing, and using the Add-WindowsPackage PowerShell cmdlet. Each method has a specific use case depending on whether the system is online or offline.

Why the Servicing Stack Update Fails to Install via wusa.exe

The root cause is a deliberate design constraint in the Windows servicing stack. The wusa.exe tool, which handles .msu files, performs a prerequisite check before applying any update. For a Servicing Stack Update, this check compares the version of the servicing stack already installed on the system against the minimum version required by the new SSU. If the installed servicing stack version is lower, wusa.exe returns error 0x800f0826 or 0x80070002 and does not install the update.

This behavior prevents a broken servicing stack scenario. If wusa.exe installed an SSU that expects a higher baseline than what is present, the Windows Update components could become non-functional. Microsoft publishes SSUs in a cumulative sequence. For example, SSU version 10.0.22621.3672 requires that the system already has SSU version 10.0.22621.3527 or later. When you download the latest SSU from the Microsoft Update Catalog and try to run it standalone, wusa.exe sees the version gap and blocks the installation.

Another factor is that wusa.exe does not download missing prerequisites. It expects all dependencies to be satisfied before it runs. For cumulative updates, the dependency is usually just the latest SSU, but for the SSU itself, the dependency is a previous SSU that wusa.exe will not fetch automatically. This is the core reason the standalone .msu file appears to “refuse” to install.

The error is not a sign of a corrupted file or an incompatible system architecture. The .msu file is valid. The system simply lacks the required baseline servicing stack version. The solution is to install the intermediate SSU versions first, or to use a different installation tool that does not enforce the version check.

Steps to Install the Servicing Stack Update Correctly

You have three methods to bypass the wusa.exe version check. Choose the method that matches your environment.

Method 1: Install SSUs in Sequential Order Using wusa.exe

This method works when you can identify and obtain all intermediate SSU versions between the current system version and the target SSU.

1. Check the current servicing stack version
   Open PowerShell as Administrator. Run: Get-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion" | Select-Object CurrentBuild, CurrentVersion, ReleaseId. Note the CurrentBuild value, for example 22621. The servicing stack version is listed under HKLM:\SYSTEM\CurrentControlSet\Control\Session Manager\Environment as OSVersion in some builds, or check dism /online /get-currentedition. A more direct method: run wmic os get buildnumber and then look up the servicing stack baseline for that build in Microsoft’s documentation.
2. Download the required intermediate SSUs
   Go to the Microsoft Update Catalog at catalog.update.microsoft.com. Search for “Servicing Stack Update” plus your build number, for example “Servicing Stack Update 22621”. Sort by date ascending. Download the SSU that is newer than your current servicing stack version but older than the one that failed. If your current SSU version is 10.0.22621.3000 and the failing SSU is 10.0.22621.3672, look for SSU version 10.0.22621.3400 or similar.
3. Install the intermediate SSU
   Run wusa.exe with the intermediate .msu file: wusa.exe C:\path\SSU_intermediate.msu /quiet /norestart. Wait for the installation to complete. If it succeeds, restart the system.
4. Install the target SSU
   After the restart, run wusa.exe with the target SSU .msu file: wusa.exe C:\path\SSU_target.msu /quiet /norestart. This should now succeed because the servicing stack version meets the baseline.

Method 2: Use DISM with the /Source Parameter to Bypass Version Check

This method uses DISM to install the SSU from a .cab file, which does not perform the same prerequisite check as wusa.exe. You must extract the .cab from the .msu file.

1. Extract the .cab file from the .msu
   Create a folder on your desktop named SSU_Extracted. Run: expand -F: C:\path\SSU.msu C:\Users\YourName\Desktop\SSU_Extracted. This extracts the .cab file and a .xml file. The .cab file is usually named Windows11.0-KBxxxxxxx-x64.cab or similar.
2. Install the .cab using DISM
   Open an elevated Command Prompt. Run: dism /Online /Add-Package /PackagePath:C:\Users\YourName\Desktop\SSU_Extracted\Windows11.0-KBxxxxxxx-x64.cab. DISM will add the package without the strict version check that wusa.exe enforces. The operation may take several minutes.
3. Verify the installation
   After completion, run: dism /Online /Get-Packages /Format:Table. Look for the SSU in the list. Its status should show as “Installed”. Restart the system.

Method 3: Use PowerShell Add-WindowsPackage for Offline Images

If you are servicing an offline Windows image VHD or WIM file, the Add-WindowsPackage cmdlet also bypasses the wusa version check.

1. Mount the offline image
   Run: Mount-WindowsImage -ImagePath C:\path\install.wim -Index 1 -Path C:\Mount. Use the correct index for your edition.
2. Install the SSU .cab
   Run: Add-WindowsPackage -PackagePath C:\Users\YourName\Desktop\SSU_Extracted\Windows11.0-KBxxxxxxx-x64.cab -Path C:\Mount. The cmdlet will add the package without the version dependency check.
3. Commit the changes and dismount
   Run: Dismount-WindowsImage -Path C:\Mount -Save. The image now contains the updated servicing stack.

Common Issues When Installing SSUs via wusa.exe

Error 0x800f0826: The update is not applicable to your computer

This is the most common error. It means the current servicing stack version is below the baseline required by the SSU. Use Method 1 or Method 2 above. Do not attempt to force install with wusa.exe switches like /force. The /force switch does not bypass the version check for SSUs.

Error 0x80070002: The system cannot find the file specified

This error can appear if the .msu file is corrupted or if the file path contains spaces. Verify the file hash from the Microsoft Update Catalog. Extract the .cab and try DISM installation as in Method 2. If the .cab file also fails, download the SSU again.

SSU installs but cumulative update still fails

If the SSU installs via DISM but a subsequent cumulative update fails, the servicing stack may still be incomplete. Use DISM to check the package list: dism /Online /Get-Packages /Format:Table. Look for any SSU packages with a status of “Install Pending”. If present, restart the system and run Windows Update again. If the issue persists, use the Windows Update Troubleshooter: Settings > System > Troubleshoot > Other troubleshooters > Windows Update > Run.

Cannot extract .cab from .msu

If the expand command fails, the .msu file may be damaged. Redownload the SSU from the Microsoft Update Catalog. Ensure you select the correct architecture x64 or ARM64 for your system. Use a tool like 7-Zip to open the .msu file directly and copy the .cab file manually.

Item	wusa.exe .msu	DISM .cab
Version check	Enforces baseline SSU version	No version check for SSU packages
File format	MSU only	CAB only
Error handling	Stops on version mismatch	Installs regardless of current SSU version
Offline image support	Not supported	Supported with /Image parameter
PowerShell equivalent	None	Add-WindowsPackage

You can now install a Servicing Stack Update that previously refused to install via wusa.exe. Use the DISM method for the quickest solution on an online system. For offline images, use the PowerShell Add-WindowsPackage cmdlet. If you prefer the sequential method, keep a list of SSU versions for your build number so you can install them in order without searching each time. After the SSU is installed, run Windows Update to verify that cumulative updates apply correctly.