Back to Blog

0x800F0823 CBS_E_NEW_SERVICING_STACK_REQUIRED When Adding a Windows Update

Christopher 4 min read
referencewindows

0x800F0823 is a Windows servicing error named CBS_E_NEW_SERVICING_STACK_REQUIRED. It appears when you add a cumulative update to an offline Windows image with DISM or Add-WindowsPackage, and when Wusa.exe installs a .msu package from a script. Microsoft's article for servicing stack update KB5031539 quotes the DISM failure as follows.

[HRESULT = 0x800f0823 - CBS_E_NEW_SERVICING_STACK_REQUIRED]

When you install the .msu package by hand on a running computer, Windows shows this message for the same cause.

The Windows Modules Installer must be updated before you can install this package.
Please update the Windows Modules Installer on the computer, then retry Setup.

What it means

The update needs a newer servicing stack than the one in the image or on the computer. The servicing stack is the component that installs Windows updates, and DISM relies on it. Since February 2021 the monthly cumulative update for Windows 10, version 2004 and later includes the latest servicing stack update. In rare cases a change in the cumulative update's format requires a standalone servicing stack update to be installed first.

How to find the cause

Find the failure in the DISM log. DISM.log in %windir%\Logs\DISM is the primary log for every offline action DISM runs.

Select-String -Path "$env:windir\Logs\DISM\dism.log" -Pattern '0x800f0823' -SimpleMatch

For a failure on a running computer, also search %windir%\Logs\CBS\CBS.log. DISM.log points to CBS.log for more detail on online servicing failures.

List the packages already in the mounted image to see which cumulative update it was last serviced with. Replace C:\offline with your mount folder.

Get-WindowsPackage -Path "C:\offline"

Compare that list with the update you're adding. For a Windows 10, version 21H2 or 22H2 image, Microsoft documents one case. DISM returns 0x800f0823 for cumulative updates from April 23, 2024 (KB5036979) onward when the image has none of the cumulative updates released from July 25, 2023 (KB5028244) through April 9, 2024 (KB5036892). For other versions, read the cumulative update's KB article for a servicing stack update listed as a prerequisite.

Fixes

For a Windows 10, version 21H2 or 22H2 image in Microsoft's documented case, download the standalone servicing stack update KB5031539 from the Microsoft Update Catalog. Add it to the mounted image before the cumulative update, then save the image. Replace 1 with the index of the edition you service and the file names with the packages you downloaded.

Mount-WindowsImage -ImagePath "C:\images\install.wim" -Index 1 -Path "C:\offline"
Add-WindowsPackage -Path "C:\offline" -PackagePath "C:\updates\ssu-kb5031539.msu"
Add-WindowsPackage -Path "C:\offline" -PackagePath "C:\updates\cumulative-update.msu"
Dismount-WindowsImage -Path "C:\offline" -Save

For an image that needs a servicing stack update listed in the cumulative update's KB article, add that update first in the same way, then add the cumulative update.

For an image with no standalone prerequisite, follow Microsoft's servicing sequence for install.wim. Add the combined cumulative update as the servicing stack step, add any language packs, Features on Demand, and optional components, then add the same cumulative update again as the last update.

On a running computer that shows the Windows Modules Installer message, update the servicing stack through Windows Update, then install the .msu package again.

Related errors

Where ET Ducky shows it

I build ET Ducky. Its patch management installs Windows updates through winget and Windows Update in rings. You'd tag a few machines as your first ring and schedule updates to that tag before the rest. A patch is marked successful only when services come back up with no crash loops. A regression in a ring pauses the deployment.

Sources

Windows updates in patch rings

Read how ET Ducky installs Windows updates in rings and checks each host after the reboot before the update reaches the next ring.

Read the patch management docs