As it turns out, the most popular cause that will trigger this error message is a missing manifest of the previous update package. In other words, the WU (Windows Update) component is not aware of what was last installed, so it refuses to install new update packages. If this scenario is applicable, you can get the issue resolved by installing the missing update manually. Another potential cause that will lead to the 0x800f0831 error is a scenario in which your end-user machine cannot communicate with Windows Update servers. This can either be facilitated by system file corruption or VPN connections or Proxy servers. However, the issue can also be caused by a disabled WU service or a missing .NET 3.5 Framework. In this case, you’ll need to enable the framework from the Windows Features menu or you can install it from a compatible installation media. In rare circumstances, Windows updates might fail with the 0x800f0831 error due to some type of system corruption. This can either be resolved by using System Restore, performing SFC & DISM scans, or by refreshing the components of your OS (via Clean install or Repair install).
How to Troubleshoot and Fix Error 0x800f0831 during Windows Update?
Method 1: Install the missing update manually
If you’re looking for a quick way to expedite the issue, your best chance at getting the problem fixed in one shot is to install the failing update manually. As it turns out, there is one failing update that is mostly reported to cause this issue (KB4512489). If this scenario is applicable, you can use the Microsoft Update Catalog to find and install the missing package manually. This is effective in those situations where the issue is being caused by a corrupted WU dependency. Several affected users have confirmed that this operation worked for them. Here’s a quick guide on using the Microsoft Update Catalog to fix the 0x800f0831 error: In case this operation didn’t allow you to circumvent the 0x800f0831 error or you’re looking for a method that will fix the component that is causing the issue, move down to the next potential fix below.
Method 2: Disable VPN or Proxy server (if applicable)
The second largest cause that might trigger the 0x800f0831 error is some kind of interference that ends up blocking communications between your Windows end-user version and the Windows Update server. In the vast majority of reported cases, this problem was either created by a VPN client or a Proxy server. Some users that were struggling to fix this problem have confirmed that they managed to fix the issue by uninstalling their VPN client or by disabling the Proxy server (depending on the scenario that was applicable). We created two separate guides to accommodate both scenarios that might be applicable, so follow whichever one applies to your current situation. Note: If you use neither a VPN connection or Proxy server, skip the sub-guides below and move directly to Method 3.
Disable a VPN Connection
Disable a Proxy server
If none of these two scenarios where applicable, move down to the next potential fix below.
Method 3: Set the status of Windows Update to Automatic
If the computer that’s experiencing the failed Windows Update installation is part of a shared domain, it’s possible that a network policy or a 3rd party system optimizer tool has ended up disabling the main service responsible for the updating function. If this scenario is applicable, you can get the issue resolved by accessing the Services screen, set the Startup Type to Automatic and start the Windows Update service forcefully. Here’s a quick guide on how to do this: Note: The steps below should be universal, so you should be able to follow it regardless of the Windows version that you’re using. In case the startup type of Windows Update was already set to Automatic and this didn’t resolve the issue, move down to the next method below.
Method 4: Enabling .NET Framework 3.5
If you’re encountering the issue when trying to install a cumulative update, you should explore the possibility of a disabled .NET 3.5 framework. The installation process of cumulative updates is more complex and might fail unless every needed dependency is enabled. Several affected users have confirmed that they managed to fix the issue by using the Windows Features menu to ensure that .NET 3.5 framework is disabled. Here’s a quick guide on ensuring that .NET Framework is enabled on your Windows computer: In case you’re still encountering the same 0x800f0831 error, move down to the next potential fix below.
Method 5: Installing .NET Framework 3.5 via CMD
In case the method above triggered an error once you tried to enabled .NET Framework 3.5 or the option wasn’t available inside the Windows Features screen, you might force the installation yourself by installing the missing framework from an elevated CMD terminal. We are going to create a custom CMD script that will force the installation of .NET Framework 3.5 and enforce the commands automatically. But keep in mind that in order to do this, you will need a compatible Windows installation media. If you don’t have one at the ready, you will need to create one. Note: Here’s how to create compatible installation media for Windows 7 (here) and Windows 10 (here). Once you got the installation media at the ready, follow the instruction below to force the installation of .NET Framework 3.5 from an elevated CMD prompt: In case you’re still encountering the same 0x800f0831 error, move down to the next potential fix below.
Method 6: Performing SFC and DISM Scans
If none of the methods below have allowed you to fix the 0x800f0831 error, it’s very likely that the issue is actually being caused by some kind of system file corruption. In case this scenario is applicable, you should start by running a couple of utilities (DISM and SFC) that are equipped to fix and replace corrupted instances. DISM (Deployment Image Servicing and Management) is a tool that’s heavily reliant on a sub-component of WU. It requires an internet connection in order to fix corrupted system files. On the other hand, SFC (System File Checker) is 100% local and uses a locally cached archive to replace corrupted data with healthy equivalents. Because the two utilities operate differently, we encourage you to run both in quick succession in order to maximize your chances of success. Here’s a quick guide on performing SFC and DISM scans from an elevated CMD prompt: In case you’re still dealing with the same 0x800f0831 error, move down to the final fix below.
Method 7: Using System Restore
If you only started noticing this issue recently after a driver or update installation or after an unexpected machine shutdown, and none of the pending updates are installed, it’s likely that a recent system change has brought about this inability to install updates. If this scenario is applicable, you should be able to fix this issue by using the System Restore utility to revert your computer back to a healthy state when this issue wasn’t occurring. Keep in mind that by default, Windows 7, Windows 8.1 and Windows 10 are configured to save new restore snapshots regularly (at important system events). So unless you’ve modified this default behavior (or a 3rd party application did it for you), you should have plenty of restore snapshots to choose from. But keep in mind that using a System Restore snapshot means that any change you made after the snapshot was created will also be lost. This includes any installed applications, games, and any other system changes that you made during that time period. If you are aware of the consequences, here are the step-by-step instructions to using System Restore to restore your computer back to a healthy state: In case the 0x800f0831 error is still occurring or this method wasn’t applicable, move down to the next potential fix below.
Method 8: Performing a clean install/repair
If you’ve come this far and none of the methods above have allowed you to fix the issue, it’s most likely due to some kind of system corruption that cannot be resolved conventionally. If this scenario is applicable, your only chance of fixing the issue is to reset every Windows component. When it comes to doing this, you have two choices:
Clean install – This is the easiest solution out of the two. You don’t need an installation media and you can deploy this fix directly from the GUI of Windows 10, Windows 8.1 and Windows 7. However, unless you back up your data in advance, expect total personal data loss.Repair install – If you’re looking for a more focused approach, you should go for this method instead. You will need a compatible installation media, but the major advantage is that you will be able to keep all your personal data including apps, applications, personal media, and even some user preferences.
Follow whichever method you find more comfortable with.
[FIX] Windows Failed to Install the following Update with Error 0x800F0986SOLVED: Windows 10 Update Failure Error Failure 80240020’Failure To Install’ Issue In Windows 10 Forces Microsoft To Releases Revised…Windows 10 20H1 2004 Blocked By Windows Security App? Here’s A Solution To…
