Reason
Description
The update is superseded
As updates for a component are released, the updated component will supersede an older component that is already on the system. When this occurs, the previous update is marked as superseded. If the update that you're trying to install already has a newer version of the payload on your system, you may encounter this error message.
Search for the update on the Windows Update catalog: Windows Update Catalog
Click on the Package Details tab to view the list of updates that are superseded
The update is already installed
If the update that you're trying to install was previously installed, for example, by another update that carried the same payload, you may encounter this error message.
See KB 4023262 How to Verify that MS17-010 is installed
Wrong update for architecture
Trying to install a 32bit (x86) update on a 64bit (x64) system or vice versa. If the update that you're trying to install does not match the architecture for your CPU, you may encounter this error message.
Missing prerequisite updates
Some updates require a prerequisite update before they can be applied to a system. If you are missing a prerequisite update, you may encounter this error message.
Windows 8.1 / Windows Server 2012 R2
KB 2919442: March 2014 Servicing Stack Update for Windows 8.1 and Windows Server 2012 R2
KB 2919355: Windows RT 8.1, Windows 8.1 and Windows Server 2012 R2 Update: April 2014
KB 3173424: Servicing stack update for Windows 8.1 and Windows Server 2012 R2: July 12, 2016
To see if they are installed, run the PowerShell cmd: get-hotfix KB3173424,KB2919355,KB2919442
Windows 8 / Windows Server 2012
3173426 Servicing stack update for Windows Server 2012: July 12, 2016
Win7/2008R2 Servicing stack update
Service Pack 1
3177467 Servicing stack update for Windows 7 SP1 and Windows Server 2008 R2 SP1: September 20, 2016]
Windows Vista / Windows Server 2008
Service Pack 2
Windows XP / Windows Server 2003
Service Pack 2
Component Store Corruption
Component Store Corruption / CBS_STORE_CORRUPTION You will need to analyze the cbs.log to see if this is your scenario. You should see error or text similar to: 0x800f0831 - CBS_E_STORE_CORRUPTION
See: SFC /Scannow and DISM /RestoreHealth Process
If these fail to resolve, collect new CBS.log and search for CheckSUR to see the results of DISM command
The Trusted Installer fails to execute
The service responsible for package installation is the Trusted Installer Service.
The service name in the services snap-in (services.msc) for Trusted Installer is theWindows Modules Installer service.
Some customers may have disabled this service in error.
Service startup failures are logged in the System event log.
Verify the Windows Modules Installer service is not disabled, and there are no errors in the System event log.