How to fix Update Error 0x800f0831 in Windows or Windows Server

In this article, we shall discuss how to fix Update Error 0x800f0831 in Windows. Windows Update errors 0x800f0831 often times indicates a missing manifest file or servicing component corruption in the Component Store (WinSxS). Please see Backing Up OpenShift Is Not the Same as Recovering It, Veeam Agent for Windows deployment failing with Access Denied, and Restoring a Physical Ubuntu Server to VMware using Veeam Agent and Export as Virtual Disks.

When Windows Servicing tries to change a package state such as superseding or removing a KB package. It fails because it cannot locate the necessary precursor file as the case maybe. Below is an error message similar to what will appear in the Windows event log when you continue to troubleshoot this issue.

Package kb777778 failed to be changed to the absent state as shown in the image below. Status: 0x800f0831. Initiating changes for package kb777778. Current state is superseded. Target state is absent. Client id: This means this device is not updated prompt arbiter. is not updated promptly

Also, see Action required: Update Devolutions Remote Desktop Manager Before July 21, How to Back Up and Restore Microsoft Entra ID with Veeam Backup & Replication v13, and Azure Resource Inventory (ARI) for Engineers: Improving Control and Compliance.

Connect to Device Remotely

You can check or perform diagnostics remotely or locally as the case may be. Since this is a remote device, I will be connecting using the Computer Management tool. There are other numerous tools out there, even Remote Desktop Management Tool you can use to connect to a device remotely.

For me, I will launch the Computer Management, then click on Action and select connect to another computer. Then, enter the target hostname or IP address and click OK.

Navigate to System Tools > Event Viewer > Windows Logs > Setup to inspect Event IDs 1014 and 1015 etc. As you can see below, we have a warning error “0 of 928 instances of system store corruption have been repaired. Unrepaired corruptions may lead to failures in future system servicing”.

As you can see also, system store corruption detection and repair has completed was detected. Status: 0x0, total instances of corruption found: 928, total instances of corruption repaired: 0.

Note: Therefore, both event IDs “1015 or 1014” indicates instances of system store corruption where 0 instances were repaired automatically

Also, you will notice the following informational message “Initiating changes for package KB5101650. Current state is Absent. Target state is Staged. Client id: UpdateAgentLCU”.

Please see Azure Load Balancer: Configuring for SQL Server Always On Availability Group Listener on Azure Virtual Machines, and Azure Virtual Desktop: Build Custom Session Host Images Using Image Builder Templates [Part 07].

Download the Missing Cumulative Update or Package

Note: Ideally, you are to manually download or remove these packages. A lot of guides recommend this steps. But, letting Windows perform the cleanup is preferrable to manually forcing removal or installing these packages as Windows servicing can properly handle package dependencies and component relations as there are no visible errors with the Windows update client in the log.

If you would like to follow this step if applicable to you. You will need to manually download the missing or superseded Update package (e.g., KB777778 as it applies to me or its prerequisite package) directly from the Microsoft Update Catalog:

1. Open your browser and navigate to the Microsoft Update Catalog.
2. Search for the KB number referenced in your Event Logs.
3. Download the exact .msu file matching your operating system architecture.
4. Extract or save the file to a temporary directory (e.g., C:\Update).

But in my case, all updates have been performed successfully. So, there is no need applying the above due to the following event log we discussed above “event IDs “1015 or 1014” indicates instances of system store corruption where 0 instances were repaired automatically”.

Tis update found has been suceesfully applied.

Therefore, no more update needed to be applied. Therefore, we will take the second option to repair the component store.

Please see Veeam Agent for Windows: VSS Error Caused by Old SQL Server References, How to implement Azure Private Link for Azure Virtual Desktop [Part 06], and Azure Virtual Desktop: Autoscaling Implementing and Monitoring Session Hosts [Part 05].

Fix Windows Store Corruption Using DISM

Open an elevated Command Prompt and select run as Administrator, and execute the DISM tool to repair the Component Store using the downloaded package or Windows Update online services as a source (preferrable in my case).

Option A: Online Repair via Windows Update

DISM /Online /Cleanup-Image /ScanHealth

DISM /Online /Cleanup-Image /RestoreHealth

sfc /scannow

This table outlines the essential command sequence for resolving Windows servicing errors like 0x800f0831

Option B: Offline Repair Using Downloaded Package Source

If your device cannot reach Windows Update or is blocked in a corporate environment. Please point DISM directly to an extracted WIM/CAB or mounted ISO image as shown below:

DISM.exe /Online /Cleanup-Image /RestoreHealth /Source:C:\Update\Package.cab /LimitAccess

Once DISM finishes the repair operation successfully. This means that the restore operation completed successfully. Then, restart the device.

Re-open Event Viewer and navigate to Applications and Services Logs > Microsoft > Windows > WindowsUpdateClient > Operational. Trigger a manual update check. Look for Event ID 41: An update was downloaded, followed by successful installation logs.

I will recommend you to promptly apply Windows Updates (Patches) when released in order to avoid these issues going forward.

I hope you found you fund this guide on “how to fix Update Error 0x800f0831 in Windows or Windows Server” very useful. Please feel free to leave a comment below.