|
| 1 | +--- |
| 2 | +title: Troubleshoot Windows Installation Error 0x800f0831 CBS E STORE CORRUPTION_Windows |
| 3 | +description: Learn how to resolve Windows Update installation error 0x800f0831 CBS E STORE CORRUPTION_Windows. |
| 4 | +ms.date: 10/21/2025 |
| 5 | +manager: dcscontentpm |
| 6 | +audience: itpro |
| 7 | +ms.topic: troubleshooting |
| 8 | +ms.reviewer: scotro,mwesley |
| 9 | +ms.custom: |
| 10 | +- sap:windows servicing,updates and features on demand\windows update fails - installation stops with error |
| 11 | +- pcy:WinComm Devices Deploy |
| 12 | +--- |
| 13 | +# Troubleshoot Windows Update installation error 0x800f0831 CBS_E_STORE_CORRUPTION |
| 14 | +Windows Update error 0x800f0831 (CBS_E_STORE_CORRUPTION) typically occurs if an update doesn't install the required package files correctly. This article helps you understand the root cause of the issue and the necessary steps to resolve it effectively. |
| 15 | + |
| 16 | + |
| 17 | +## Prerequisites |
| 18 | +Before you troubleshoot, follow the steps in [Back up an Azure VM from the VM settings](/azure/backup/backup-azure-vms-first-look-arm?branch=main&branchFallbackFrom=pr-en-us-9456) to back up the OS disk. |
| 19 | + |
| 20 | +## Symptoms |
| 21 | + |
| 22 | +When you try to install any update by using the standalone installer (.msu), or you try to install a Windows update, you receive one of the following error messages: |
| 23 | + |
| 24 | +> Some updates were not installed |
| 25 | +
|
| 26 | +:::image type="content" source="media/following-updates-were-not-installed.png" alt-text="Screenshot of the installation error message."::: |
| 27 | + |
| 28 | +> Updates failed |
| 29 | +
|
| 30 | +:::image type="content" source="media/windows-update-failed.png" alt-text="Screenshot of the Windows Update failed error message."::: |
| 31 | + |
| 32 | +## Cause |
| 33 | + |
| 34 | +This error can occur for one of the following reasons: |
| 35 | + |
| 36 | +- The update was never installed. |
| 37 | +- The update is installed but some packages aren't applied to the registry. |
| 38 | + |
| 39 | + |
| 40 | +To locate the installation packages in the system, search for the following registry subkey: |
| 41 | + |
| 42 | +```output HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages``` |
| 43 | + |
| 44 | +To investigate the cause further, examine the CBS.log file (C:\windows\logs\CBS). For more information on how to collect these logs, see [Fix Windows Update corruptions and installation failures](fix-windows-update-errors.md#logging) |
| 45 | + |
| 46 | +```output |
| 47 | +Info CBS Store corruption, manifest missing for package: Package_123_for_KB3192392~31bf3856ad364e35~amd64~~6.3.1.4 |
| 48 | +
|
| 49 | +Error CBS Failed to resolve package 'Package_123_for_KB3192392~31bf3856ad364e35~amd64~~6.3.1.4' [HRESULT = 0x800f0831 - CBS_E_STORE_CORRUPTION] |
| 50 | +
|
| 51 | +Info CBS Mark store corruption flag because of package: Package_123_for_KB3192392~31bf3856ad364e35~amd64~~6.3.1.4. [HRESULT = 0x800f0831 - CBS_E_STORE_CORRUPTION] |
| 52 | +
|
| 53 | +Info CBS Failed to resolve package [HRESULT = 0x800f0831 - CBS_E_STORE_CORRUPTION] |
| 54 | +``` |
| 55 | +> [!NOTE] |
| 56 | +> The package and error details may vary depending on the OS version and the KB update. However, when this error is logged, the recommended solution in this article will apply. |
| 57 | +> [!NOTE] |
| 58 | +> For more information about how to collect the CBS.log file, see [Fix Windows Update corruptions and installation failures](fix-windows-update-errors.md#logging). For more information on how to use TroubleshoortingScript (TSS) tool version 2, see [Introduction to TroubleShootingScript toolset (TSS)](../../windows-client/windows-tss/introduction-to-troubleshootingscript-toolset-tss.md) |
| 59 | +
|
| 60 | +## Resolution |
| 61 | + |
| 62 | +If the update is installed, remove and reinstall it. If the update is not installed, install it. |
| 63 | + |
| 64 | + |
| 65 | +### Here are the steps to remove and install the update: |
| 66 | + |
| 67 | +1. Reproduce the issue by trying to install the update or feature that's experiencing issues. This action logs the latest data into the CBS log. |
| 68 | +1. Verify that you have the correct update after you identify the package that the CBS process is calling out. |
| 69 | +1. Navigate to [Microsoft Update Catalog](https://www.catalog.update.microsoft.com/Home.aspx), and search for the KB number that you identified. |
| 70 | +1. Select the appropriate KB version for the OS version and architecture, and then download the file to a temporary folder ("temp") on drive C. |
| 71 | +1. Open an administrative Command Prompt window, and run the following command on the folder: |
| 72 | + |
| 73 | + ```output |
| 74 | + cd \ |
| 75 | + cd temp |
| 76 | + expand -F:* windows10.0-kb4462937-x64_9e250691ae6d00cdf677707e83435a612c3264ea.msu C:\temp |
| 77 | + ``` |
| 78 | + |
| 79 | + **Note:** In this command, substitute the actual name of the downloaded file. |
| 80 | + |
| 81 | +1. In the expanded packages, locate the .cab file that uses the following format, depending on the OS version: |
| 82 | + |
| 83 | + windows 10.0-KB*xxxxxxx*-x64.cab |
| 84 | + |
| 85 | +1. Run the following command at an administrative command prompt: |
| 86 | + |
| 87 | + ```output |
| 88 | + Dism /online /remove-package /packagepath:C:\temp\windows10.0-kb4462937-x64.cab |
| 89 | + ``` |
| 90 | + |
| 91 | + **Note:** In this command, substitute the actual name of the .cab file. |
| 92 | + |
| 93 | +1. Restart the computer if you're prompted to do that. |
| 94 | +2. Run the following command at an administrative command prompt: |
| 95 | + |
| 96 | + ```output |
| 97 | + Dism /online /add-package /packagepath:C:\temp\windows10.0-kb4462937-x64.cab |
| 98 | + ``` |
| 99 | + |
| 100 | +1. Restart the computer. |
| 101 | +1. Try again to install the update or feature. |
| 102 | + |
| 103 | +### If the update isn't installed |
| 104 | + |
| 105 | +1. Navigate to the [Microsoft Update Catalog](https://www.catalog.update.microsoft.com/Home.aspx), and download the update to a temporary folder ("temp") on drive C. |
| 106 | +1. At an administrative command prompt, run the following command on the folder: |
| 107 | + |
| 108 | + ```output |
| 109 | + cd \ |
| 110 | + cd temp |
| 111 | + expand -F:* windows10.0-kb4462937-x64_9e250691ae6d00cdf677707e83435a612c3264ea.msu C:\temp |
| 112 | + ``` |
| 113 | + |
| 114 | + **Note:** In this command, substitute the actual name of the downloaded file. |
| 115 | + |
| 116 | +1. In the expanded packages, locate the .cab file that uses the following format, depending on the OS version: |
| 117 | + |
| 118 | + windows 10.0-KB*xxxxxxx*-x64.cab |
| 119 | + |
| 120 | +1. At an administrative command prompt, run the following command: |
| 121 | + |
| 122 | + ```output |
| 123 | + Dism /online /add-package /packagepath:C:\temp\windows10.0-kb4462937-x64.cab |
| 124 | + ``` |
| 125 | + |
| 126 | + **Note:** In this command, substitute the actual name of the .cab file. |
| 127 | + |
| 128 | +1. Restart the computer. |
| 129 | + |
| 130 | +1. Try again to install the update or feature. |
| 131 | + |
| 132 | +### In-place upgrade process |
| 133 | + |
| 134 | +> [!NOTE] |
| 135 | +> For **virtual machines running in Azure** encountering this specific Windows update error, this error has been reviewed, and it is strongly suggested to do an In-place upgrade (IPU) as a simple and effective solution to recover the VM. When the IPU completes, the machine’s OS will be reinstalled while retaining the current configuration of the machine which is the ideal situation. For additional information, see [In-place upgrade for supported VMs running Windows in Azure](../../azure/virtual-machines/windows/in-place-system-upgrade.md) |
0 commit comments