How to fix Windows update error 0x800f0816?
Prefer to fix it yourself? The manual steps follow.
- 6methods
- 5 minutes to 2 hours
- Easy to intermediate
Applies to Windows 11 and Windows 10 updates from Windows Update or the Microsoft Update Catalog, and the same code in CBS.log on Windows Server and older Windows versions
6 methods in this guide
Hi, I was trying to install the recent Windows updates, but I keep getting the 0x800f0816 error. Can you give me any advice on what I should do, please?
Error 0x800f0816 means Windows stopped while it was unpacking and staging an update, so the update is not installed. It is a servicing code, and the real reason is usually written a few lines higher in CBS.log. Restart the PC fully and run Windows Update again first.
0x800f0816 is the servicing code CBS_E_DPX_JOB_STATE_SAVED: Windows stopped staging the update and saved the job for later. Restart with Start > Power > Restart and run Windows Update again (Fix 1). If the same update fails again, read CBS.log for the error just above 0x800f0816 (Fix 2), then reset the update cache or install the update by hand (Fix 3 and Fix 4).
| Error | 0x800f0816, shown as Install error - 0x800f0816 in Windows Update, or as 800F0816 in Update history on older Windows. |
|---|---|
| Where it appears | Settings > Windows Update and Update history when a monthly or cumulative update fails, and in C:\Windows\Logs\CBS\CBS.log. |
| Main cause | The servicing stack (CBS) could not finish staging the update package. The code is the result, and the reason is usually another error logged just before it. |
| Fastest fix | A full Restart, not Shut down, then Check for updates again (Fix 1). |
| Also written as | 800F0816, 0x800F0816, CBS_E_DPX_JOB_STATE_SAVED, Failed to stage execution chain. |
| Affects | Windows 11, Windows 10 and Windows Server. Users reported it on Windows 7 and Vista as early as 2011. |
| Microsoft's status | Not a known issue of one update. The code is not in Microsoft's Windows Update error list, because it comes from the servicing stack, not the Windows Update client. |
| Where the cause is written | C:\Windows\Logs\CBS\CBS.log: the lines just above HRESULT = 0x800f0816. |
| Time to fix | 5 to 30 minutes for Fix 1 to Fix 4. Up to two hours for the repair reinstall in Fix 6. |
Facts checked on 16 October 2026. Steps written for Windows 11 (25H2 and 26H2) and Windows 10 22H2.
What Windows update error 0x800f0816 means
0x800f0816 belongs to Component Based Servicing (CBS), the part of Windows that installs updates, drivers and Windows features. In CBS.log its name is CBS_E_DPX_JOB_STATE_SAVED. DPX is the part of servicing that unpacks update packages. The name says the unpacking job was stopped and its state was saved, so the update could not be staged in this attempt.
Microsoft does not explain the code on any support page we found, and it is not in Microsoft's Windows Update error code list. What the logs posted on Microsoft Q&A show is consistent: the code appears on the lines Failed to stage execution chain and Failed to process single phase execution, and right after them CBS writes Reboot mark cleared.
| What you see | Where | What it tells you |
|---|---|---|
| Install error - 0x800f0816 | Settings > Windows Update on Windows 11 and Windows 10 | The update failed during installation, not during download. |
| Failed to install, error 0x800f0816 | Settings > Windows Update > Update history | The KB number on the same line is the update to retry or install by hand. |
| Code 800F0816 | Update history on Windows 7 and Vista | The same code without 0x. Those systems no longer get updates. |
| Failed to stage execution chain. [HRESULT = 0x800f0816 - CBS_E_DPX_JOB_STATE_SAVED] | C:\Windows\Logs\CBS\CBS.log | Staging stopped. The reason is in the lines above. |

In logs that users posted, CBS sometimes marks the 0x800f0816 lines as Info, not Error, and writes another failure first. That is why the same generic repair works on one PC and not on another: the real cause differs.
Why error 0x800f0816 appears
The causes are ordered from the most likely to the least likely. They follow from what the code means and from the logs posted on Microsoft's forums. We could not find a Microsoft page that ranks them.
| Cause | How often | How to tell | Fix |
|---|---|---|---|
| The staging was interrupted and waits for a restart, or the PC was only shut down or put to sleep. | Most often | The first failure of this update, or Settings shows Restart now. | Fix 1 |
| Another servicing error happened first, for example a missing component, and 0x800f0816 only follows it. | Often | CBS.log shows an Error line with a different HRESULT just above 0x800f0816. | Fix 2 |
| The downloaded update in the cache is damaged or incomplete, so every retry unpacks the same bad files. | Often | The same KB fails at every retry, other updates install. | Fix 3, Fix 4 |
| The component store is damaged, so the update has nothing valid to build on. | Sometimes | CBS.log names missing or corrupt components, and SFC finds errors. | Fix 5 |
| The servicing stack or the update state is broken beyond repair. | Rarely | Every update fails for weeks, and DISM cannot repair the store. | Fix 6 |

Windows 10 left support on 14 October 2025. A Windows 10 PC without Extended Security Updates gets no new monthly updates, so 0x800f0816 there usually comes from an older update that never installed.
How to fix error 0x800f0816
Fix 1 solves the error when the staging was only interrupted. Fix 2 tells you which of the other fixes to use, because the real cause is in CBS.log. Fix 3 and Fix 4 are for one update that keeps failing, and Fix 5 and Fix 6 are the general repairs.
| What you see or have | Start with |
|---|---|
| The first failure, or Settings > Windows Update asks for a restart | Fix 1 |
| The update fails again after a full restart | Fix 2 |
| The same KB fails at every retry, other updates install | Fix 3, then Fix 4 |
| CBS.log names missing or damaged components, or SFC finds errors | Fix 5 |
| Every update fails for weeks and the repairs did not help | Fix 6 |
Fix 1. Restart the PC fully and run Windows Update again
5 to 20 minutesNo riskEveryone, first. Especially when the update failed once, or Windows Update shows a restart button.
The code says the staging job was saved, not that it is impossible. A full restart clears the interrupted servicing work, and the next attempt unpacks the update from the start.
- Save your work and close open apps.
- Open Settings > Windows Update. If you see Restart now, select it.
- If there is no such button, open Start, select the Power button and then Restart. Do not use Shut down or Sleep.
- Wait while Windows shows Working on updates. Do not turn the PC off during this screen.
- Sign in, open Settings > Windows Update and select Check for updates.
- Let the failed update download and install again. Keep a laptop plugged in.
With Fast Startup on, which is the default on most PCs, Shut down does not end the Windows session in full. Restart always does. If you only ever shut the PC down, turning Fast Startup off can help: Turn off Fast Startup.
It worked if: The update installs, asks for a restart, and Update history lists it as Successfully installed.
If not: If the same update fails again with 0x800f0816, read CBS.log with Fix 2.
Fix 2. Find the real error above 0x800f0816 in CBS.log
5 to 10 minutesNo riskThe update failed again after a full restart. This takes five minutes and tells you which of Fix 3 to Fix 6 to use.
0x800f0816 is often written after another servicing error. The first failure in the same attempt is the cause, and it decides the fix.
- Right after the failed update, press Win + R, type
%windir%\Logs\CBSand press Enter. - Copy
CBS.logto the Desktop. Windows keeps the original in use, so open only the copy. - Open the copy in Notepad, press Ctrl + End to go to the newest lines, then press Ctrl + F.
- Search upwards for
0x800f0816. You should findFailed to stage execution chainandFailed to process single phase execution. - Read the 20 to 50 lines above that hit. Look for the first line marked Error or a different
HRESULT. - Note that code and any KB number or package name near it, and use the table below.
| What the lines above show | What it means | Go to |
|---|---|---|
Nothing else, only 0x800f0816 and Reboot mark cleared | The staging was interrupted. | Fix 3 |
0x80073701 or ERROR_SXS_ASSEMBLY_MISSING | A component the update needs is missing from the store. | Fix 5 |
corrupt, hash mismatch or a damaged file name | The download or the component store is damaged. | Fix 3, then Fix 5 |
A KB number with not applicable or superseded | The package does not match this PC or is already replaced. | Fix 4 with the right file |
On a forum thread about update KB4516065 on Windows 7, 0x800f0816 appeared next to error 80073701, a missing component. We give it as a user report, not as a rule: check your own log.
It worked if: You have one other error code or a KB number, and you know which fix to run next.
If not: If you find no other error, or the log is too long to read, go on with Fix 3.
Fix 3. Reset the Windows Update components and download the update again
10 minutesLow riskThe same KB fails with 0x800f0816 at every retry, and CBS.log shows no clear other cause or a damaged file.
Windows reuses the files in its update cache at every retry. If those files are damaged, unpacking fails again in the same place. Renaming the cache folders makes Windows download the update from the start.
- 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.
- 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 - 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" - 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 - 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 - 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

After the reset, open Services and check that Windows Update, Background Intelligent Transfer Service and Cryptographic Services are not set to Disabled. A disabled service stops the new download.

It worked if: Windows Update downloads the update again and installs it after a restart.
If not: Install the update by hand with Fix 4.
Fix 4. Install the failing update by hand from the Microsoft Update Catalog
15 to 30 minutesLow riskOne KB fails with 0x800f0816 after Fix 1 and Fix 3, and other updates install.
A fresh .msu file from the catalog is a complete package that does not depend on the Windows Update cache. If it does not match the PC, the standalone installer says so in words instead of a code.
Note the KB number of the failed update in Update history first. The procedure below finds the right file for your Windows version and installs it.
- Check your Windows version. Press Windows key + R, type winver and press Enter. Note the version (for example 25H2) and the OS build.
- 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.
- 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.
- 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.
- 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.
- 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.
- Install a single file. If there is only one file, double-click it and confirm the installation in the Windows Update Standalone Installer.
- 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 - 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

It worked if: The installer finishes, asks for a restart, and Update history lists the KB as installed.
If not: If the file also fails, repair the component store with Fix 5.
Fix 5. Repair the component store and system files with DISM and SFC
15 to 40 minutesNo riskCBS.log names missing or corrupt components, such as 0x80073701, or Fix 3 and Fix 4 did not help.
An update is unpacked on top of the components already in the store. If one of them is missing or damaged, staging stops. DISM with RestoreHealth replaces damaged components, and SFC then repairs system files.
- Open an elevated command window. Right-click Start and select Terminal (Admin), or type cmd in the search box, right-click Command Prompt and select Run as administrator. Select Yes when Windows asks for permission.

Search for cmd and choose Run as administrator. Screenshot: Windows 11 26H2. - Run DISM first. Type the command below and press Enter. DISM downloads clean copies of damaged components from Windows Update, so it can take several minutes. Wait until it says The operation completed successfully.
DISM.exe /Online /Cleanup-Image /RestoreHealth
DISM /RestoreHealth running. Screenshot: Windows 11 26H2. - Run System File Checker. In the same window, type the command below and press Enter. Do not close the window until the verification reaches 100%.
sfc /scannow
sfc /scannow at 100%. Screenshot: Windows 11 26H2. - Read the result and restart. Compare the last message with the table below this guide, then restart the PC so that repaired files are loaded.

The result line tells you what SFC did. Screenshot: Windows 11 26H2.
These steps were written for Windows 11 24H2 and 25H2. The full page with the other versions and what each result means: Run DISM and SFC to repair Windows system files
Run DISM right after a fresh restart, when no update is installing. Then restart again and retry the update with Fix 1 or Fix 4.
It worked if: DISM reports The operation completed successfully., SFC finds no integrity violations or repairs them, and the update installs.
If not: If DISM cannot repair the store, reinstall Windows over itself with Fix 6.
Fix 6. Reinstall Windows over itself and keep your apps and files
1 to 2 hoursLow riskEvery update fails with 0x800f0816 for weeks, and Fix 1 to Fix 5 did not help.
A repair reinstall replaces the servicing stack, the component store and the update state with a clean copy of the same Windows version, so the next update has a working base. Apps, files and settings stay.
- 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.

Fix problems using Windows Update reinstalls the current version and keeps apps, files and settings. Screenshot: Windows 11 26H2. - Start the reinstall. Choose whether the PC may restart on its own 15 minutes after the installation, then select OK.
- 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 installation files from Microsoft, run setup and choose Upgrade this PC now or Keep personal files and apps.

Your files are meant to stay, but a failed reinstall can leave Windows unable to start. Back up what you cannot lose first: Back up your files (Windows Backup, File History, Time Machine). Keep a laptop plugged in for the whole process.
It worked if: The PC starts into the same desktop with your apps and files, and Windows Update installs updates again.
If not: Read the next section before you reset the PC.
If error 0x800f0816 is still there
Collect the facts before you try anything bigger. Support staff and administrators need the same few things to find the cause.
- The KB number from Settings > Windows Update > Update history.
- The Windows version and build: press Win + R, type
winverand press Enter. - A copy of
C:\Windows\Logs\CBS\CBS.logtaken right after a failed attempt, and the other HRESULT you found in Fix 2. - Whether the same file from the Microsoft Update Catalog also failed (Fix 4).
| What the log or the PC shows | What to do |
|---|---|
| Work or school PC, updates from the organization | Do not reset anything. Send the administrator the KB, the build and CBS.log. |
| The PC lost power or froze during an update | Check the drive for errors first: Check a disk for errors (chkdsk) |
| Other programs also fail to install or update | Test with a clean boot to rule out a third-party service: How to perform a clean boot in Windows |
| The repair reinstall is missing or fails | Use Reset this PC with Keep my files: Reinstall Windows without losing files. Apps are removed, your files stay. |
0x800f0816 is a servicing state, not a hardware fault. The exception is a drive that reports errors in chkdsk, because a failing drive can damage the update cache and the component store again after each repair.
How to keep error 0x800f0816 from coming back
- Restart with Restart when Windows Update asks, the same day if you can.
- Keep a laptop plugged in while updates install.
- Let one update or feature install finish before you start the next one.
- Install updates only from Windows Update or catalog.update.microsoft.com.
- Do not turn the PC off on the Working on updates screen.
- Do not delete files in
C:\Windows\WinSxSorC:\Windows\Logs\CBSby hand. - Do not use registry cleaners or update blockers that remove servicing data.
- Do not leave updates uninstalled for weeks. The security fixes are in them.
Frequently asked questions
What does error 0x800f0816 mean?
It means Windows stopped while unpacking and staging an update, and saved the job instead of finishing it. Its name in CBS.log is CBS_E_DPX_JOB_STATE_SAVED, and it comes from the servicing stack that installs updates, not from the Windows Update download client. The update is not installed. A full restart and a new attempt fix it in many cases. When it returns, the real reason is usually another error a few lines higher in CBS.log.
Is 0x800f0816 a download error?
No. The update was downloaded, and the failure happens when Windows unpacks and stages it. That is why the message says Install error, not Download error. A damaged download can still be the reason, because Windows reuses the files in its cache. Resetting the Windows Update components in Fix 3 removes that cache, so the update is downloaded again from the start.
Why is 0x800f0816 not in Microsoft's error code list?
Microsoft's Windows Update error code list covers the codes of the Windows Update client, such as the 0x8024 family. Codes that start with 0x800f08 belong to Component Based Servicing, which actually installs the packages. They appear in CBS.log under their own names, such as CBS_E_DPX_JOB_STATE_SAVED, but Microsoft does not describe each of them on a support page. We could not find an official description of this one.
How do I fix 0x800f0816 on Windows 7?
Windows 7 lost support on 14 January 2020, so most of its updates are no longer offered, and fixing this error there brings little. In 2011 users reported 800F0816 on Windows 7 and Vista with updates such as KB2507938 and KB2533623. One of them ran the troubleshooter, SFC, a clean boot and the System Update Readiness Tool KB947821, and the update still failed. If you must keep Windows 7, read CBS.log as in Fix 2. Moving to a supported Windows is the real solution.
Will the Windows Update troubleshooter fix 0x800f0816?
Rarely. The troubleshooter restarts services and clears some settings, but it does not repair a damaged component or redo an interrupted staging. A user on Microsoft's forum reported that it said it had fixed a problem while the update still failed. A full restart in Fix 1 and the cache reset in Fix 3 do the same useful parts more reliably.
Can I hide or skip the update that fails with 0x800f0816?
You can pause updates in Settings > Windows Update for a few weeks, but you should not skip a security or cumulative update for good. Monthly cumulative updates include the fixes of earlier months, so the next one may install even when an older one failed. If it fails too, the cause is on the PC, and Fix 2 to Fix 5 apply.
Will a repair reinstall delete my files?
No, not the repair reinstall in Fix 6. Fix problems using Windows Update, and Windows Setup with Keep personal files and apps or Upgrade this PC now, 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.
Should I turn off my antivirus to fix 0x800f0816?
No. No source ties this servicing code to security software, and turning protection off leaves the PC exposed without touching the cause. Restart, read CBS.log, reset the update cache and repair the component store. If you suspect another program interferes with updates in general, test with a clean boot instead: How to perform a clean boot in Windows.
Is 0x800f0816 the same as 0x800f0806 or 0x800f0826?
No. They are different codes from the same servicing family. 0x800f0806 is CBS_E_PENDING, which means earlier work still waits for a restart, and it has its own guide: 0x800f0806. We could not confirm the meaning of 0x800f0826 from a Microsoft source. A full restart helps with all of them, but the later fixes differ, so check the exact code in Update history.
Sources
- Microsoft Q&A: Installation of cumulative update fails on Windows Server 2016 (CBS.log lines with HRESULT 0x800f0816 CBS_E_DPX_JOB_STATE_SAVED) (learn.microsoft.com)
- Microsoft Learn: Windows Update error code list by component (the code is not listed) (learn.microsoft.com)
- Microsoft Q&A: Error code 800F0816 installing updates (Windows 7 and Vista reports, 2011) (learn.microsoft.com)
Did this fix work?
One click, no account. It tells the next reader which guides are worth their time.
Questions and experiences: fix Windows update error 0x800f0816
Still broken, or found a fix we did not cover? Ask here: members and our editors answer. Reading is open; writing needs a free account.
…