Cumulative updates consistently fail with error 0x800f0831

das126

New member
Joined
May 21, 2021
Posts
3
My problem: Windows Update can't install cumulative updates. It gets to 100% and then fails with error 0x800f0831.

DISM /online /cleanup-image /restorehealth always fails with error 0x800f0831 as well.

I've tried downloading the Media Creation Tool and mounting the ISO file. The \sources\ subfolder contains an install.esd file. I've tried running DISM /online /cleanup-image /restorehealth with the arguments /source:ESD:filepath:1 /limitaccess to no avail. (I have checked and :1 is the correct index.) I've tried various syntaxes for the /Source argument: I've tried with and without the :ESD; I've tried removing the :1, I've tried moving the install.esd file to various places on my PC and adjusting the filepath accordingly; I've tried extracting the appropriate WIM file index from the ESD and pointing /Source there instead. All to no avail -- the result is always a 0x800f0831 error when I run DISM /online /cleanup-image /restorehealth /source:XXX /limitaccess.

Help!

Context:

- I have Windows 10 Home, x64, 20H2.
- sfc /scannow says my PC is fine, no problems detected.
- Every time I run the Windows Update troubleshooter, it lists "Check for Windows Update issues" under "Problems Found." If I request more detailed information it says "Resolve Windows Update Issues - Completed" but this never resolves the problem.
- DISM /online /cleanup-image /scanhealth and /checkhealth both say the component store is repairable.
- My CBS.log has the following two lines repeated dozens of times, and I believe this is at least partially the culprit:
2021-05-21 13:19:00, Info CBS Store corruption, manifest missing for package: Microsoft-Windows-MSMQ-Client-Home-Premium-Package~31bf3856ad364e35~amd64~~10.0.19041.572
2021-05-21 13:19:00, Info CBS Mark store corruption flag because of package: Microsoft-Windows-MSMQ-Client-Home-Premium-Package~31bf3856ad364e35~amd64~~10.0.19041.572. [HRESULT = 0x80070490 - ERROR_NOT_FOUND]

- My CBS.log file also shows several dozen other errors, including the following (which are not comprehensive):
2021-05-21 13:18:59, Info CBS Store corruption, manifest missing for package: Microsoft-Windows-Lxss-Optional-Package~31bf3856ad364e35~amd64~~10.0.19041.572
2021-05-21 13:18:59, Info CBS Mark store corruption flag because of package: Microsoft-Windows-Lxss-Optional-Package~31bf3856ad364e35~amd64~~10.0.19041.572. [HRESULT = 0x80070490 - ERROR_NOT_FOUND]

2021-05-21 13:19:01, Info CBS Store corruption, manifest missing for package: Microsoft-Windows-PowerShell-V2-Client-Package~31bf3856ad364e35~amd64~~10.0.19041.546
2021-05-21 13:19:01, Info CBS Mark store corruption flag because of package: Microsoft-Windows-PowerShell-V2-Client-Package~31bf3856ad364e35~amd64~~10.0.19041.546. [HRESULT = 0x80070490 - ERROR_NOT_FOUND]

2021-05-21 13:19:08, Error CBS Failed to resolve package 'HyperV-Compute-Host-merged-Package~31bf3856ad364e35~amd64~~10.0.19041.546' [HRESULT = 0x800f0831 - CBS_E_STORE_CORRUPTION]
2021-05-21 13:19:08, Info CBS Mark store corruption flag because of package: HyperV-Compute-Host-merged-Package~31bf3856ad364e35~amd64~~10.0.19041.546. [HRESULT = 0x800f0831 - CBS_E_STORE_CORRUPTION]

2021-05-21 13:19:08, Info CBS Mark store corruption flag because of package: HyperV-Compute-System-VmDirect-Package~31bf3856ad364e35~amd64~~10.0.19041.572. [HRESULT = 0x800f0831 - CBS_E_STORE_CORRUPTION]
2021-05-21 13:19:08, Info CBS Failed to resolve package: HyperV-Compute-System-VmDirect-Package~31bf3856ad364e35~amd64~~10.0.19041.572 [HRESULT = 0x800f0831 - CBS_E_STORE_CORRUPTION]

2021-05-21 13:19:08, Error CBS Failed to resolve package 'HyperV-Feature-VirtualMachinePlatform-Package~31bf3856ad364e35~amd64~~10.0.19041.572' [HRESULT = 0x800f0831 - CBS_E_STORE_CORRUPTION]
2021-05-21 13:19:08, Info CBS Mark store corruption flag because of package: HyperV-Feature-VirtualMachinePlatform-Package~31bf3856ad364e35~amd64~~10.0.19041.572. [HRESULT = 0x800f0831 - CBS_E_STORE_CORRUPTION]
 
Windows Update can't install cumulative updates; the error message is always 0x800f0831.

DISM /online /cleanup-image /restorehealth always fails with error 0x800f0831.

I've tried downloading the Media Creation Tool and mounting the ISO file. The \sources\ subfolder contains an install.esd file. I've tried running DISM /online /cleanup-image /restorehealth with the arguments /source:ESD:filepath:1 /limitaccess to no avail. (I have checked and :1 is the correct index.) I've tried various syntaxes for the /Source argument: I've tried with and without the :ESD; I've tried removing the :1, I've tried moving the install.esd file to various places on my PC and adjusting the filepath accordingly; I've tried extracting the appropriate WIM file index from the ESD and pointing /Source there instead. All to no avail -- the result is always a 0x800f0831 error when I run DISM /online /cleanup-image /restorehealth /source:XXX /limitaccess.

Context:

- I have Windows 10 Home, x64, 20H2.
- sfc /scannow says my PC is fine, no problems detected.
- Every time I run the Windows Update troubleshooter, it lists "Check for Windows Update issues" under "Problems Found." If I request more detailed information it says "Resolve Windows Update Issues - Completed" but this never resolves the problem.
- DISM /online /cleanup-image /scanhealth and /checkhealth both say the component store is repairable.
- A .zip of my logs\CBS folder is located here.

Thank you for any help you can offer!
 
I apologize for the duplicate post earlier and for skipping the step to run SFCFix before posting my issue on this board.

I have now downloaded and run SFCFix. I have attempted to use the application five times; each time, the application hangs at a different point and fails to complete. The application never ends up creating the log file mentioned. In the most recent run, for example, the application states the following:

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.

DISM then runs, reaches 100%, and generates error 0x800f081f, but the application does not proceed and an SFCfix.txt log file is never created.

I would be grateful for any help anyone may be able to offer.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top