[SOLVED] Windows 10 22H2 - windows update error 0x800f0831

tgeo · Nov 12, 2023

Hello,

First my OS details:

Edition Windows 10 Enterprise
Version 22H2
Installed on ‎10/‎7/‎2021
OS build 19045.3208
Experience Windows Feature Experience Pack 1000.19041.1000.0

Windows Update seems stuck to version 19045.3208 (July 2023). It fails when it tries to install "2023-10 Cumulative Update for Windows 10 Version 22H2 for x64-based Systems (KB5031356)" (19045.3570 to my understanding), so it seems to been failing regularly since July.

Error I get while installing this update:

There were some problems installing updates, but we'll try again later. If you keep seeing this and want to search the web or contact support for information, this may help: (0x800f0831)

I am attaching my DISM and CBS log files. I tried manually running DISM tools (dism /online /restore health and sfc /scannow) but it did not help.
I also run SFCFix.exe.

Code:

Due to the nature of your corruptions, scan times have been extended by
approximately 15-20 minutes. Please be patient and allow the operation to
complete.


Deployment Image Servicing and Management tool
Version: 10.0.19041.844

Image Version: 10.0.19045.3208

[==========================100.0%==========================]
Error: 0x800f081f

The source files could not be found.
Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see https://go.microsoft.com/fwlink/?LinkId=243077.

The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log

And it says It has found no errors...

tgeo · Nov 12, 2023

here are the attached logs.

Thanks in advance

Maxstar · Nov 12, 2023

Hi and welcome to Sysnative,

Step 1. Download

SFCFix and save it to your desktop.

Warning: This fix was written specifically for this system. Do not run this fix on another system.

Save any work you have open, and close all programs.
Download the attachment SFCFix.zip and save it to your desktop.
Drag the SFCFix.zip file over the SFCFix.exe executable and release it.

SFCFix will launch, let it complete.
Once done, a file will appear on your desktop, called SFCFix.txt.
Post the logfile (SFCFix.txt) as attachment in your next reply.

Step 2. Run the following DISM command and post the result. If it fails attach a new copy of the CBS log.

Code:

DISM /online /cleanup-image /RestoreHealth

tgeo · Nov 13, 2023

Hello Maxstar, thanks for looking into this.

attached the SFCFix.txt seems to have run successfully.

DISM seems to have failed again but at something totally different this time.

Code:

C:\WINDOWS\system32>DISM /online /cleanup-image /RestoreHealth

Deployment Image Servicing and Management tool
Version: 10.0.19041.844

Image Version: 10.0.19045.3208

[==========================100.0%==========================]
Error: 0x800f081f

The source files could not be found.
Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see https://go.microsoft.com/fwlink/?LinkId=243077.

The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log

Attaching DISM and CBS logs

Maxstar · Nov 13, 2023

Hi,

Step 1. Download

ComponentsScanner and save it to your desktop.

Right-click ComponentsScanner.exe and select "Run as administrator", click Yes on the UAC (User Account Control) prompt which appears.
Follow the on-screen instructions.
Once complete, a report will be saved to your desktop called ComponentsScanner.txt.
Post the logfile ComponentsScanner.txt as attachment into your next reply.

Step 2. Upload your COMPONENTS hive.

Navigate to C:\Windows\System32\Config and locate the COMPONENTS file.
Please copy this file to your desktop.
Note: If you receive an error that this file is in-use, simply reboot your computer and try again.
Right-click on this file on your desktop and select Send To > Compressed (zipped) folder. This will create a file named COMPONENTS.ZIP on your desktop.
If the file is too large to upload here, upload the file to www.wetransfer.com and post the link in your next reply.

tgeo · Nov 13, 2023

Hello,

components scanner pretty much came back empty like last time.
Here both of them attached.

Thanks

Maxstar · Nov 13, 2023

Step 1.
Warning: This fix was written specifically for this system. Do not run this fix on another system.

Save any work you have open, and close all programs.
Download the attachment SFCFix.zip and save it to your desktop.
Drag the SFCFix.zip file over the SFCFix.exe executable and release it.

SFCFix will launch, let it complete.
Once done, a file will appear on your desktop, called SFCFix.txt.
Post the logfile (SFCFix.txt) as attachment in your next reply.

Step 2. Run the following DISM command and post the result. If it fails attach a new copy of the CBS log.

Code:

DISM /online /cleanup-image /RestoreHealth

tgeo · Nov 13, 2023

Hello thanks again,

here are the (seems successful) results of the script.

DISM completed successfully

Code:

C:\WINDOWS\system32>DISM /online /cleanup-image /RestoreHealth

Deployment Image Servicing and Management tool
Version: 10.0.19041.844

Image Version: 10.0.19045.3208

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

wow. Will reboot next and try windows update and let you know how it goes!

Maxstar · Nov 13, 2023

Great, let me know the result, if it fails attach a new copy of the CBS logs.

tgeo · Nov 13, 2023

hmm Windows update failed again with (0x80073701)

attached the CBS logs.

its seems to error at:

Code:

2023-11-13 11:49:01, Error                 CSI    00000330@2023/11/13:09:49:01.747 (F) onecore\base\wcp\componentstore\csd_locking.cpp(95): Error STATUS_SXS_ASSEMBLY_MISSING originated in function CCSDirectTransaction::LockComponent expression: (null)
[gle=0x80004005]
2023-11-13 11:49:01, Error                 CSI    00000331 (F) STATUS_SXS_ASSEMBLY_MISSING #7796425# from CCSDirectTransaction::OperateEnding at index 0 of 1 operations, disposition 2[gle=0xd015000c]
2023-11-13 11:49:01, Error                 CSI    00000332 (F) HRESULT_FROM_WIN32(ERROR_SXS_ASSEMBLY_MISSING) #7796280# from Windows::ServicingAPI::CCSITransaction::ICSITransaction_PinDeployment(Flags = 0, a = MultiPoint-Tools-Opt-Deployment, version 10.0.19041.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}, cb = (null), s = (null), rid = 'MultiPoint-Tools-Opt-Package~31bf3856ad364e35~amd64~~10.0.19041.1.f5cd5662361482633d272661260f4c7e', rah = (null), manpath = (null), catpath = (null), ed = 0, disp = 0)[gle=0x80073701]

Maxstar · Nov 13, 2023

It seems a number of registry keys are missing.

Here's the first fix.

Warning: This fix was written specifically for this system. Do not run this fix on another system.

Save any work you have open, and close all programs.
Download the attachment SFCFixScript.txt and save it to your desktop.
Drag the SFCFixScript.txt file over the SFCFix.exe executable and release it.

SFCFix will launch, let it complete.
Once done, a file will appear on your desktop, called SFCFix.txt.
Post the logfile (SFCFix.txt) as attachment in your next reply.

Afterwards attempt to update. If it fails attach a new copy of the CBS logs.

tgeo · Nov 13, 2023

hello, logfile attached

update fails again, CBS logs attached. seems like another set of registry keys if I can understand correctly the patterns you are searching for.

Maxstar · Nov 13, 2023

Here's the first fix.

Warning: This fix was written specifically for this system. Do not run this fix on another system.

Save any work you have open, and close all programs.
Download the attachment SFCFixScript.txt and save it to your desktop.
Drag the SFCFixScript.txt file over the SFCFix.exe executable and release it.

SFCFix will launch, let it complete.
Once done, a file will appear on your desktop, called SFCFix.txt.
Post the logfile (SFCFix.txt) as attachment in your next reply.

Afterwards attempt to update. If it fails attach a new copy of the CBS logs.

tgeo · Nov 13, 2023

it seems that this is going to drag, sorry about that.
still failed below the logs

Maxstar · Nov 13, 2023

Yes, this going to be a tough job since we need to replace approx 250+ registry keys, and they are also related to (expired) preview updates.
The quickest way to resolve this issue is to perform a in-place-upgrade. Otherwise I'll need to setup a VM with all the required updates, but a repair install will save us both a lot of time.
So let me know if you want to try to perform a repair install.

tgeo · Nov 13, 2023

sure Maxstar just a quick question, will the repair install retain all my files/programs/apps settings (i.e. firefox sessions) installed? if everything will be retained I have no issues trying this to save us both some time.

thanks again for all your help, it is invaluable.

Maxstar · Nov 13, 2023

Yes, normally it will not affect any of your personal files/settings etc. But I always suggest to make a complete backup (system image) first.

Windows 10 Repair Install
This will reinstall and update the operating system and fix any corruptions, without removing any file or program. But make always a backup of all your important data!

Go to this Microsoft page and under the title Create Windows 10 installation media press on Download tool now.
Save the tool on your Desktop and double click to run it.
On the License terms page, if you accept the license terms, select Accept.
On the What do you want to do page, select Create installation media (USB....) and then select Next.
Choose the ISO file option. Once the download is complete, right click the ISO and select the option Mount.
Open the Windows File Explorer and open mounted ISO, and run the setup.exe file.
Follow the instructions and click on the option Change what to keep.
Select the option Keep personal files and apps and click next.
Windows Setup will now start the in-place upgrade installation to repair Windows.

tgeo · Nov 14, 2023

Ok, in my case this was more complicated so I'll indicate the steps here in case someone in the future faces the same issues.

Everything updates, and the OS build info updated to the more recent:

Edition Windows 10 Enterprise
Version 22H2
Installed on ‎13/‎11/‎2023
OS build 19045.3570
Experience Windows Feature Experience Pack 1000.19052.1000.0

So. I tried downloading the ISO with the Media Creation Tool as @Maxstar pointed above, however this only works for Home/Pro Editions. Mine being an Enterprise one (I think it is an old VL from a friend but it used to be Windows 8 and a lot of years have passed since) it was unable to provide and ISO that could repair the installation. So:

I used this script to download 21H2 version of Windows 10 Enterprise as an ISO, as 22H2 seems to be pulled from public channels and replaced with 11. I do not want yet to upgrade to 11.
I followed Maxstar's instructions above, mounted the ISO, ran the setup.exe it took a couple of hours to upgrade and repair, and worked great without touching my files and programs.
Now I was updating correctly but was in 19044. (21H2)
Then I found feature update 22h2 enablement package in reddit, as it seems to have been pulled away from every MS source in favor of Windows 11. Downloaded it for x64 and applied and now I was in 19045.
Updated once again, and now I am in the latest version and windows update works correctly.

@Maxstar thanks a lot for your invaluable help! The work that you do here is amazing.
A quick question. I suspect my corruption in the first place might be related with me installing all cumulative update previews. I see there is also one now but I am kind of reluctant. What is your recommendation in general regarding update previews?

Maxstar · Nov 14, 2023

Hi,

Sorry, with the Enterprise version you can't use the Media Creation Tool. To download the ISO for Windows 10 Enterprise you'll to login at Microsoft's download center or the Evaluation Center.

tgeo said:
What is your recommendation in general regarding update previews?

Preview updates are (non-security) releases and it is basically a beta release for the upcoming cumulative update which will be released on patch Tuesday. Preview updates may contain bugs which can cause problems with newer updates. Personally, I do not recommend to install such updates, except on systems and/or virtual machines for testing purposes.

tgeo · Nov 14, 2023

thanks a lot for the feedback. marking this as solved

[SOLVED] Windows 10 22H2 - windows update error 0x800f0831

Member

Attachments

Member

Attachments

Windows Update Moderator, Security Analyst

Attachments

Member

Attachments

Windows Update Moderator, Security Analyst

Member

Attachments

Windows Update Moderator, Security Analyst

Attachments

Member

Attachments

Windows Update Moderator, Security Analyst

Member

Attachments

Windows Update Moderator, Security Analyst

Attachments

Member

Attachments

Windows Update Moderator, Security Analyst

Attachments

Member

Attachments

Windows Update Moderator, Security Analyst

Member

Windows Update Moderator, Security Analyst

Member

Windows Update Moderator, Security Analyst

Member