How to fix Windows update error 0x800f0823?

Error 0x800f0823 means the update needs a newer servicing stack, the part of Windows that installs updates, than the one on your PC. It appears after a PC skipped updates for a while. Update the servicing stack first, usually by installing the newest cumulative update, then try the failed update again.

Facts checked on 16 October 2026. Steps written for Windows 11 (25H2 and 26H2) and Windows 10 22H2.

What Windows update error 0x800f0823 means

0x800f0823 is a code of Component Based Servicing (CBS), the engine that installs Windows updates. Its name is CBS_E_NEW_SERVICING_STACK_REQUIRED. In plain words: the update you are installing was built for a newer installer than the one your PC has, so Windows refuses to start.

Microsoft Learn says the error can appear whether you install from Windows Update or from a downloaded file. In Windows 11 Settings it is shown next to the update as Install error - 0x800f0823. Searches for install error - 0x800f0823 come from that line.

Why error 0x800f0823 appears

The causes are ordered from the most likely to the least likely. The first one is Microsoft's own explanation. The others follow from how servicing stack updates are delivered.

Microsoft Learn explains that Windows Update normally keeps the servicing stack current on its own. Since February 2021, starting with KB4601382, the monthly cumulative update on Windows 10 2004 and later includes the latest servicing stack update. Microsoft calls this a single combined cumulative update.

That is good news for the fix. On Windows 11 and on Windows 10 22H2 you do not hunt for a separate SSU: the newest cumulative update installs the new servicing stack first and the rest of the update after it.

How to fix Windows update error 0x800f0823

Fix 1 to Fix 4 all do the same thing in different ways: they put a newer servicing stack on the PC. Start with the first one that fits your situation. Fix 5 and Fix 6 are the general repairs when the stack cannot be updated at all.

Fix 1. Install every update Windows Update offers, then try again

15 to 45 minutesNo riskA home or office PC on Windows 11 or Windows 10 22H2 that shows Install error - 0x800f0823 in Settings.

Microsoft says Windows Update normally installs servicing stack updates by itself. A PC that skipped updates often still has the newer cumulative update queued, and that update brings the servicing stack the failed package asks for.

1. Open Settings > Windows Update. On Windows 10 it is Settings > Update & Security > Windows Update.
2. If updates are paused, select Resume updates.
3. Select Check for updates and let Windows download and install everything offered.
4. Restart the PC when asked. Use Restart, not Shut down.
5. Open Windows Update again and select Check for updates once more. Repeat until nothing new is offered.
6. Press Win + R, type winver and press Enter. Note the OS build for the next fix if the error stays.

Fix 2. Install the newest cumulative update from the Microsoft Update Catalog

20 to 40 minutesLow riskFix 1 failed, the PC skipped months of updates, or you tried to install an older KB by hand.

This is Microsoft's resolution for 0x800f0823 on current Windows versions. The newest security update includes the SSU and the cumulative update, so installing it updates the servicing stack before anything else.

To find the newest KB number, open Microsoft's update history page for your version: Windows 11 at support.microsoft.com/help/5065323, Windows 10 2004 and later at support.microsoft.com/help/5018682. Use the KB at the top of the list for your version, not the one that failed.

1. Check your Windows version. Press Windows key + R, type winver and press Enter. Note the version (for example 25H2) and the OS build.
2. Find the KB number. Open Settings > Windows Update. A failed or pending update is listed with its KB number; earlier ones are under Update history.
3. Check the processor type. Open Settings > System > About and look at System type: an x64-based PC needs the x64 file, an ARM-based PC (for example Snapdragon) needs the arm64 file.
4. Search the catalog. Open the Microsoft Update Catalog at catalog.update.microsoft.com in your browser, type the KB number (for example KB5124010) in the search box and press Enter.
5. Pick the right row. Find the row whose title names your Windows version and your processor type (x64-based or arm64-based) and select Download on that row.
6. Download every file listed. A window lists one or more .msu links. Download all of them into one empty folder, for example C:\packages. On Windows 11 24H2 and later the list can include earlier checkpoint updates that the new one needs.
7. Install a single file. If there is only one file, double-click it and confirm the installation in the Windows Update Standalone Installer.
8. Install several files with DISM. If there are several files, open an elevated Terminal or Command Prompt and run DISM with the newest file. DISM finds the other files in the same folder and installs them in the right order.

   DISM /Online /Add-Package /PackagePath:C:\packages\<newest-file>.msu

9. Restart. Restart the PC when the installation finishes, then run winver again: the OS build should have changed.

These steps were written for Windows 11 24H2 and later; Windows 10 22H2. The full page with the other versions and what each result means: Install an update from the Microsoft Update Catalog

Fix 3. Extract the servicing stack from the update file and install it first

15 to 30 minutesLow riskThe newest cumulative update fails as a whole, so its built-in servicing stack update never gets a chance to install.

A combined .msu file holds the SSU as a separate .cab file inside it. Michls Tech Blog showed that installing that file alone with DISM updates the servicing stack, after which the cumulative update installs.

1. Download the newest cumulative update for your version and processor as in Fix 2, and copy the .msu file to C:\packages.
2. Right-click Start and select Terminal (Admin) or Command Prompt (Admin). Select Yes when Windows asks for permission.
3. Go to the folder and unpack the .msu file into a new folder. Replace the file name with yours:

   cd C:\packages
   mkdir msu
   expand windows10.0-kb5004760-x64.msu -F:* msu

4. Run dir msu and look for a file whose name starts with SSU-, for example SSU-19041.1081-x64.cab in the blog's Windows 10 example.
5. If the SSU file is not in msu directly, unpack the large KB .cab file the same way and look again:

   mkdir ssu
   expand msu\Windows10.0-KB5004760-x64.cab -F:* ssu

6. Install only the SSU file with DISM. Replace the path with the file you found:

   DISM /Online /Add-Package /PackagePath:C:\packages\ssu\SSU-19041.1081-x64.cab

7. Wait for The operation completed successfully., restart the PC, then install the full .msu file again.

Fix 4. Install the standalone servicing stack update on older Windows versions

15 to 30 minutesLow riskWindows 10 version 1607 or older, an LTSB edition built on those, or Windows Server 2016.

On these versions the servicing stack still ships as its own update. Microsoft's resolution is to find the newest SSU in the catalog, install it, restart and then retry the update that failed.

1. Open the Microsoft Update Catalog at catalog.update.microsoft.com.
2. Search for ssu "Windows 10" on Windows 10 1607 and older, or ssu "Windows Server 2016" on Windows Server 2016. Keep the quotation marks.
3. Sort by Last Updated and pick the newest update that matches your version and processor type.
4. Select Download and save the file.
5. Double-click the file and confirm the installation. Restart the PC when it finishes.
6. Install the update that failed with 0x800f0823 again.

Microsoft also lists the newest SSU per Windows version on its advisory page ADV990001 in the Security Update Guide. Look for the FAQ question "When was the most recent SSU released for each version of Microsoft Windows?"

Fix 5. Reset the Windows Update components

10 minutesLow riskWindows Update fails at the same point every time, even after Fix 1 to Fix 4.

A damaged download in the update cache is used again at every retry, so a new SSU may never be read correctly. Renaming SoftwareDistribution and catroot2 makes Windows download the update again from zero.

1. Open Command Prompt as administrator. Type cmd in the search box, right-click Command Prompt and select Run as administrator. Select Yes when Windows asks for permission.
2. Stop the update services. Type the commands below and press Enter after each one. If Windows says that other services depend on Cryptographic Services, it stops them too. A message that a service is not started is fine.

   net stop wuauserv
   net stop bits
   net stop cryptsvc

3. Delete the download queue files. This clears the list of downloads that the Background Intelligent Transfer Service keeps. If Windows says it cannot find the files, continue.

   del "%ALLUSERSPROFILE%\Application Data\Microsoft\Network\Downloader\qmgr*.dat"

4. Rename the update cache folders. Renaming keeps a copy in case you need it; Windows creates new, empty folders when the services start again. If you get Access is denied, a service is still running: repeat the previous step.

   ren %systemroot%\SoftwareDistribution SoftwareDistribution.old
   ren %systemroot%\System32\catroot2 catroot2.old

5. Start the services again. Type the commands below and press Enter after each one. The requested service has already been started is fine: Windows started it on its own.

   net start cryptsvc
   net start bits
   net start wuauserv

6. Restart and check for updates. Restart the PC. Then select Start > Settings > Windows Update > Check for updates. The first check can take longer than usual because everything is downloaded again.

These steps were written for Windows 11 and Windows 10 (the steps are the same). The full page with the other versions and what each result means: Reset Windows Update components

Fix 6. Reinstall Windows over itself and keep your apps and files

1 to 2 hoursLow riskNothing could update the servicing stack, and every update still fails with 0x800f0823.

A repair reinstall replaces Windows, including the servicing stack, with a current copy of the same version. The new copy no longer needs the old stack to be updated, and apps, files and settings stay.

1. Open Recovery in Settings. Open Settings > System > Recovery. Next to Fix problems using Windows Update, select Reinstall now. This keeps your apps, files and settings.

   

2. Start the reinstall. Choose whether the PC may restart on its own 15 minutes after the installation, then select OK.
3. Wait and restart. Windows Update downloads and installs a repair copy of your current Windows version. Keep the PC plugged in and online, and restart it when asked.

These steps were written for Windows 11 22H2 and later. The full page with the other versions and what each result means: Reinstall Windows without losing files

If Fix problems using Windows Update is missing, download the Windows 11 installation files from Microsoft, open the ISO, run setup.exe and keep Keep personal files and apps. On Windows 10 22H2 use the Windows 10 media the same way.

If error 0x800f0823 is still there

Read the servicing log before you try anything else. It names the package and both servicing stack versions, which tells you how far behind the PC is.

1. Press Win + R, type %windir%\Logs\CBS and press Enter.
2. Copy CBS.log to the Desktop and open the copy in Notepad.
3. Press Ctrl + F and search for 0x800f0823.
4. Read the line: requires Servicing Stack shows what the update needs, but current Servicing Stack is shows what the PC has.
5. Compare the needed version with the build of the newest update you installed. If it is still lower, the SSU did not install.

How to keep error 0x800f0823 from coming back

Frequently asked questions

What does error 0x800f0823 mean?

It means the update you are installing needs a newer servicing stack than the one on your PC. Its internal name is CBS_E_NEW_SERVICING_STACK_REQUIRED. The servicing stack is the part of Windows that installs updates, and Microsoft says it gets out of date when a PC skips updates. The update file is not damaged. Install the newest cumulative update, which carries the new servicing stack, and then try again.

What does Install error - 0x800f0823 mean in Windows Update?

It is how Windows 11 Settings shows the same failure next to the update that did not install. Windows Update tried to install the package, found that the servicing stack was too old, and stopped. Install every other update offered and restart. If the error stays, download the newest cumulative update for your version from the Microsoft Update Catalog and install it by hand, as in Fix 2.

What is a servicing stack update (SSU)?

It is an update for the servicing stack itself, the component that installs Windows updates. Microsoft Learn says it also drives DISM, System File Checker and turning Windows features on or off. Servicing stack updates are small and not released every month. Since February 2021 they ship inside the monthly cumulative update on Windows 10 2004 and later, so most PCs never see them as separate updates.

Where do I download the servicing stack update for Windows 11 or Windows 10 22H2?

You do not download it separately. Microsoft Learn says that on Windows 10 2004 and later, and on Windows 11, the security update includes both the SSU and the cumulative update. Find the newest KB number on Microsoft's update history page for your version, search the Microsoft Update Catalog for that number and install it. If it fails as a whole, Fix 3 shows how to extract the SSU file.

Does error 0x800f0823 happen on Windows 11?

Yes. Microsoft's article on the error lists all supported Windows client and server versions and Azure virtual machines. On Windows 11 it shows in Settings as Install error - 0x800f0823. The fix is the same as on Windows 10 22H2: install the newest cumulative update, through Windows Update or from the catalog. On Windows 11 24H2 and later, the catalog may also list a checkpoint update that must be installed with it.

Why does Windows Update show a different code when CBS.log says 0x800f0823?

Windows Update reports the result of the whole installation, and CBS.log records the reason inside it. In the Windows 10 example on Michls Tech Blog, Windows Update showed 0x80242017 for the cumulative update, and only CBS.log named 0x800f0823 with both servicing stack versions. When the log has that line, treat the problem as an old servicing stack and follow Fix 2 or Fix 3.

Can SFC or DISM RestoreHealth fix error 0x800f0823?

Not by themselves. SFC and DISM repair damaged system files, but they do not install a newer servicing stack, and 0x800f0823 is about the version of that stack, not about damage. Microsoft's resolution is to install the newest SSU or cumulative update. DISM is useful here in a different way: with /Add-Package it can install the SSU file, as in Fix 3.

Can I fix 0x800f0823 by turning off my antivirus?

No. Microsoft ties this code only to an out-of-date servicing stack, and no source we read links it to security software. Turning protection off would leave the PC exposed without changing the servicing stack version. Install the newest cumulative update instead, as in Fix 1 or Fix 2. If you think another program blocks updates in general, test with a clean boot rather than removing protection.

Do I lose my files if I reinstall Windows to fix this?

Not with the repair reinstall in Fix 6. Fix problems using Windows Update, and Windows Setup with Keep personal files and apps, reinstall the same Windows version and keep apps, files and settings. Reset this PC with Keep my files is different: it keeps your files but removes installed apps. Back up the files you cannot lose before any reinstall, and keep a laptop plugged in until it finishes.

Is this page also the answer for як виправити 0x800f0823?

Yes. The code is the same in every language of Windows, and only the words around it are translated. The fixes on this page work on a Ukrainian or any other Windows. The menu names in the steps are the English ones, so follow the position of the items in Settings. The DISM and expand commands and the file names are typed the same way on every PC.