Error 0x800f0823 when updating Windows 10 Server – what to do?

Error 0x800f0823 occurs exclusively when trying to install a new update through the standard Windows Update tool. By default, the procedure is automatic, but in this case it is terminated with an error. If after that you open the logs (along the path% WinDir% Logs CBS CBS.log), there should be entries of the following type:

Error CBS Package “xxx” requires Servicing Stack v10.0.19041.980 but current Servicing Stack is v10.0.19041.860. [HRESULT = 0x800f0823 – CBS_E_NEW_SERVICING_STACK_REQUIRED]

The error mostly occurs in Windows 10 and Windows Server 2016. However, after any number of attempts, the update will not be installed. The problem has a fairly clear cause and must be fixed.

Causes of Error 0x800f0823

In almost all cases, the fact is that in Windows SSU (Servicing Stack Updates) is very outdated, in Russian – the update stack. Previously, Microsoft released SSUs for all builds of Windows 10 (older than 2004) as a separate update. Since March 2021, the company has changed its approach and is now integrating fresh stacks into cumulative updates.

Thus, if the computer has not received at least one of the latest cumulative data, it will not be able to install the latest update. Instead, the already familiar error 0x800f0823 will be displayed. A similar problem is especially common for those who have disabled automatic updates or the computer has not been connected to the Internet for a long time, has not turned on at all.

How to fix error 0x800f0823?

The solution is trivial, you need to install the latest available SSU. For example, for 2004-21H1 it is KB4598481… When you have received the current SSU, you can install the latest cumulative update. It’s worth starting with KB5003173 if the latter doesn’t work. It is also recommended to install the following updates for Windows Server: KB4132216, KB4485447, KB4487006.

There is also a fallback method that will be required if SSU updates are installed, but you still cannot install a fresh version of Windows. It involves entering a series of commands, and the fastest way to do this is to save it as a file with the bat extension and run it with administrator rights. Here is the code:

net stop bits

net stop wuauserv

net stop appidsvc

net stop cryptsvc

Del “% ALLUSERSPROFILE% Application Data Microsoft Network Downloader *. *”

rmdir% systemroot% SoftwareDistribution / S / Q

rmdir% systemroot% system32 catroot2 / S / Q

sc.exe sdset bits D: (A ;; CCLCSWRPWPDTLOCRRC ;;; SY) (A ;; CCDCLCSWRPWPDTLOCRSDRCWDWO ;;; BA) (A ;; CCLCSWLOCRRC ;;; AU) (A ;; CCLCSWRPWP ;; PU)

sc.exe sdset wuauserv D: (A ;; CCLCSWRPWPDTLOCRRC ;;; SY) (A ;; CCDCLCSWRPWPDTLOCRSDRCWDWO ;;; BA) (A ;; CCLCSWLOCRRC ;;; AU) (A ;; CCLCSWRPWPDTL; PUOC)

cd / d% windir% system32

regsvr32.exe / s atl.dll

regsvr32.exe / s urlmon.dll

regsvr32.exe / s mshtml.dll

regsvr32.exe / s shdocvw.dll

regsvr32.exe / s browseui.dll

regsvr32.exe / s jscript.dll

regsvr32.exe / s vbscript.dll

regsvr32.exe / s scrrun.dll

regsvr32.exe / s msxml.dll

regsvr32.exe / s msxml3.dll

regsvr32.exe / s msxml6.dll

regsvr32.exe / s actxprxy.dll

regsvr32.exe / s softpub.dll

regsvr32.exe / s wintrust.dll

regsvr32.exe / s dssenh.dll

regsvr32.exe / s rsaenh.dll

regsvr32.exe / s gpkcsp.dll

regsvr32.exe / s sccbase.dll

regsvr32.exe / s slbcsp.dll

regsvr32.exe / s cryptdlg.dll

regsvr32.exe / s oleaut32.dll

regsvr32.exe / s ole32.dll

regsvr32.exe / s shell32.dll

regsvr32.exe / s initpki.dll

regsvr32.exe / s wuapi.dll

regsvr32.exe / s wuaueng.dll

regsvr32.exe / s wuaueng1.dll

regsvr32.exe / s wucltui.dll

regsvr32.exe / s wups.dll

regsvr32.exe / s wups2.dll

regsvr32.exe / s wuweb.dll

regsvr32.exe / s qmgr.dll

regsvr32.exe / s qmgrprxy.dll

regsvr32.exe / s wucltux.dll

regsvr32.exe / s muweb.dll

regsvr32.exe / s wuwebv.dll

netsh winsock reset

netsh winsock reset proxy

net start bits

net start wuauserv

net start appidsvc

net start cryptsvc

After the above procedure and the installation of a suitable SSU, Windows 10 and Server should update normally without error 0x800f0823. However, we hope that in the comments you will report on the work done and we will find out exactly whether it worked or not.

Leave a Comment