This article is intended for Support agents and IT professionals. If you're looking for more information about fixing Windows update errors, please go to the following page:
For Windows 10, Windows 8.1, Windows 8, Windows Server 2012 R2 or Windows Server 2012To resolve this problem, use the inbox Deployment Image Servicing and Management (DISM) tool. Then, install the Windows update or service pack again.
- Open an elevated command prompt. To do this, swipe in from the right edge of the screen, and then tap Search. Or, if you are using a mouse, point to the lower-right corner of the screen, and then click Search. Type Command Prompt in the Search box, right-click Command Prompt, and then click Run as administrator. If you are prompted for an administrator password or for a confirmation, type the password, or click Allow.
- Type the following command, and then press Enter.
It may take several minutes for the command operation to be completed.DISM.exe /Online /Cleanup-image /RestorehealthImportant When you run this command, DISM uses Windows Update to provide the files that are required to fix corruptions. However, if your Windows Update client is already broken, use a running Windows installation as the repair source, or use a Windows side-by-side folder from a network share or from a removable media, such as the Windows DVD, as the source of the files. To do this, run the following command instead:DISM.exe /Online /Cleanup-Image /RestoreHealth /Source:C:\RepairSource\Windows /LimitAccessNote Replace the C:\RepairSource\Windows placeholder with the location of your repair source. For more information about using the DISM tool to repair Windows, reference Repair a Windows Image.
- Type the following command and press Enter.
It may take several minutes for the command operation to be completed.sfc /scannow
- Close the command prompt, and then run Windows Update again.
For Windows 7, Windows Vista, Windows Server 2008 R2 or Windows Server 2008To resolve this problem, use the System Update Readiness tool. Then, install the Windows update or service pack again.
- Download the System Update Readiness tool.
Click the download link in the following table that corresponds to the version of Windows that is running on your computer.
Find out if your computer is running the 32 or 64-bit version of Windows
This tool is updated regularly, we recommend that you always download the latest version. Note This tool is not available in every supported language. Check the link below to see if it is available in your language.
Operating system Download link x86-based (32-bit) versions of Windows 7 SP1 and Windows 7Download the package now. x64-based (64-bit) versions of Windows 7 SP1 and Windows 7Download the package now. x64-based (64-bit) versions of Windows Server 2008 R2 SP1Download the package now. Itanium-based versions of Windows Server 2008 R2 SP1Download the package now. x86-based (32-bit) versions of Windows Vista SP2 and Windows Vista SP1Download the package now. x64-based (64-bit) versions of Windows Vista SP2 and Windows Vista SP1Download the package now. x86-based (32-bit) versions of Windows Server 2008 SP2Download the package now. x64-based (64-bit) versions of Windows Server 2008 SP2Download the package now. Itanium-based versions of Windows Server 2008 SP2Download the package now.
- Install and run the tool.
- Click Download on the Download Center webpage, then do one of the following:
- To install the tool immediately, click Open or Run, and then follow the instructions on your screen.
- To install the tool later, click Save, and then download the installation file to your computer. When you're ready to install the tool, double-click the file.
- In the Windows Update Standalone Installer dialog box, click Yes.
- When the tool is being installed, it automatically runs. Although it typically takes less than 15 minutes to run, it might take much longer on some computers. Even if the progress bar seems to stop, the scan is still running, so don't click Cancel.
- When you see Installation complete, click Close.
- Reinstall the update or service pack you were trying to install previously.
- Click Download on the Download Center webpage, then do one of the following:
Download the package from Microsoft Update Catalog directlyYou can also try to directly download the update package from Microsoft Update Catalog, and then install the update package manually.
- Open Microsoft Update Catalog in Internet Explorer.
- In the search box, input the update number that you want to download. In this example, input 3006137. Then, click Search.
- Find the update that applies to your operating system appropriately in the search results, and then click Add to add the update to your basket.
- Click view basket to open your basket.
- Click Download to download the update in your basket.
- Click Browse to choose a location for the update you are downloading, and then click Continue.
- Click Close after the download process is done. Then, you can find a folder that contains the update package in the location that you specified.
- Open the folder, and then double click the update package to install the update.
The following table lists the possible error code with Windows Update for your reference:
|0x80070002||ERROR_FILE_NOT_FOUND||The system cannot find the file specified.|
|0x8007000D||ERROR_INVALID_DATA||The data is invalid.|
|0x800F081F||CBS_E_SOURCE_MISSING||The source for the package or file not found.|
|0x80073712||ERROR_SXS_COMPONENT_STORE_CORRUPT||The component store is in an inconsistent state.|
|0x800736CC||ERROR_SXS_FILE_HASH_MISMATCH||A component's file does not match the verification information present in the component manifest.|
|0x800705B9||ERROR_XML_PARSE_ERROR||Unable to parse the requested XML data.|
|0x80070246||ERROR_ILLEGAL_CHARACTER||An invalid character was encountered.|
|0x8007370D||ERROR_SXS_IDENTITY_PARSE_ERROR||An identity string is malformed.|
|0x8007370B||ERROR_SXS_INVALID_IDENTITY_ATTRIBUTE_NAME||The name of an attribute in an identity is not within the valid range.|
|0x8007370A||ERROR_SXS_INVALID_IDENTITY_ATTRIBUTE_VALUE||The value of an attribute in an identity is not within the valid range.|
|0x80070057||ERROR_INVALID_PARAMETER||The parameter is incorrect.|
|0x800B0100||TRUST_E_NOSIGNATURE||No signature was present in the subject.|
|0x80092003||CRYPT_E_FILE_ERROR||An error occurred while Windows Update reads or writes to a file.|
|0x800B0101||CERT_E_EXPIRED||A required certificate is not within its validity period when verifying against the current system clock or the time stamp in the signed file.|
|0x8007371B||ERROR_SXS_TRANSACTION_CLOSURE_INCOMPLETE||One or more required members of the transaction are not present.|
|0x80070490||ERROR_NOT_FOUND||Windows could not search for new updates.|
|0x800f0984||PSFX_E_MATCHING_BINARY_MISSING||Matching component directory exist but binary missing|
|0x800f0986||PSFX_E_APPLY_FORWARD_DELTA_FAILED||Applying forward delta failed|
|0x800f0982||PSFX_E_MATCHING_COMPONENT_NOT_FOUND||Can not identify matching component for hydration|
What does the System Update Readiness Tool do
How to fix errors that are found in the CheckSUR.log
To manually fix corruption errors that the System Update Readiness Tool detects but can't fix, follow these steps:
- Open %SYSTEMROOT%\Logs\CBS\CheckSUR.log.
Note %SYSTEMROOT% is an environment variable that saves the folder in which Windows is installed. For example, generally the %SYSTEMROOT% folder is C:\Windows.
- Identify the packages that the tool can't fix. For example, you may find the following in the log file: Summary:In this case, the package that is corrupted is KB958690.
Seconds executed: 264
Found 3 errors
CBS MUM Missing Total Count: 3
Unavailable repair files:
- Download the package from Microsoft Download Center or Microsoft Update Catalog.
- Copy the package (.msu) to the %SYSTEMROOT%\CheckSUR\packages directory. By default, this directory doesn't exist and you need to create the directory.
- Rerun the System Update Readiness Tool.
If you are a technical professional, see How to fix errors found in the CheckSUR.log for a more options on fixing errors in the CheckSUR.log.