• Article
  • 6 minutes to read

Applies to: Windows x, version 1809 and afterward versions, Windows 8.1, Windows Server 2012 R2, Windows 7, Windows Server 2008 R2
Original KB number: 947821

Symptom

Windows updates and service packs may fail to install if there are abuse errors. For example, an update might not install if a system file is damaged. The DISM or System Update Readiness tool may aid yous to fix some Windows abuse errors.

This article is intended for Support agents and IT professionals. If you are home users and looking for more information about fixing Windows update errors, see Set up Windows Update errors.

Resolution for Windows eight.1, Windows 10 and Windows Server 2012 R2

To resolve this problem, utilize the inbox Deployment Prototype Servicing and Management (DISM) tool. Then, install the Windows update or service pack again.

  1. Open an elevated command prompt. To do this, open Beginning carte or Kickoff screen, type Control Prompt, correct-select Command Prompt, and then select Run as administrator. If you are prompted for an administrator password or for a confirmation, type the password, or select Let.

  2. Type the following command, so printing Enter. It may accept several minutes for the command performance to be completed.

                      DISM.exe /Online /Cleanup-image /Restorehealth

    Of import

    When you run this command, DISM uses Windows Update to provide the files that are required to ready corruptions. Still, if your Windows Update client is already cleaved, use a running Windows installation as the repair source, or utilize 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 exercise this, run the following command instead:

                      DISM.exe /Online /Cleanup-Image /RestoreHealth /Source:C:\RepairSource\Windows /LimitAccess

    Note

    Supersede the C:\RepairSource\Windows placeholder with the location of your repair source. For more data about using the DISM tool to repair Windows, reference Repair a Windows Image.

  3. Blazon the sfc /scannow control and press Enter. It may take several minutes for the command operation to exist completed.

  4. Shut the command prompt, and then run Windows Update again.

DISM creates a log file (%windir%/Logs/CBS/CBS.log) that captures any issues that the tool institute or stock-still. %windir% is the binder in which Windows is installed. For example, the %windir% folder is C:\Windows.

Resolution for Windows seven and Windows Server 2008 R2

To resolve this problem, use the System Update Readiness tool. Then, install the Windows update or service pack again.

  1. Download the Organization Update Readiness tool.

    Become to Microsoft Update Catalog and download the tool that corresponds to the version of Windows that is running on your computer. For more information about how to find the version of Windows that you installed, run across Find out if your computer is running the 32-scrap or 64-chip version of Windows.

    Annotation

    This tool is updated regularly, nosotros recommend that you ever download the latest version. This tool is not available in every supported language. Check the link below to run across if it is bachelor in your linguistic communication.

  2. Install and run the tool.

    1. Select Download on the Download Heart webpage, then do i of the following:

      • To install the tool immediately, select Open or Run, and then follow the instructions on your screen.
      • To install the tool later, select Save, and and so download the installation file to your calculator. When you're ready to install the tool, double-select the file.

    2. In the Windows Update Standalone Installer dialog box, select Yes.

      Select Yes to install hotfix for Windows KB947821 in the Windows Update Standalone Installer dialog box.

  3. When the tool is being installed, information technology 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 select Cancel.

    Download and Install updates window that shows the updates are being installed progress.

  4. When you meet Installation complete, select Close.

    Download and install Updates window shows the installation complete.

  5. Reinstall the update or service pack you lot were trying to install previously.

To manually set up abuse errors that the tool detects but can't be fixed, see How to set errors that are found in the CheckSUR log file.

Resolution - Download the parcel from Microsoft Update Catalog straight

You lot tin also try to directly download the update package from Microsoft Update Catalog, and so install the update package manually.

For example, you lot may have problems when you try to install updates from Windows Update. In this state of affairs, y'all can download the update parcel and attempt to install the update manually. To do this, follow these steps:

  1. Open Microsoft Update Itemize page for KB3006137.

  2. Discover the update that applies to your operating system appropriately in the search results, and then select the Download button.

    Microsoft Update Catalog select the Download button.

  3. Select the link of the file to download the update.

    Microsoft Update Catalog select file download link.

  4. Select Shut after the download process is done. Then, you can discover a folder that contains the update packet in the location that you lot specified.

  5. Open up the binder, and then double-select the update package to install the update.

If the Windows update or service pack installed successfully, yous are finished. If the trouble is not fixed, or if System Update Readiness Tool cannot find the crusade, contact u.s. for more assistance.

Description of the mutual corruption errors

The following table lists the possible error code with Windows Update for your reference:

Code Fault Description
0x80070002 ERROR_FILE_NOT_FOUND The arrangement cannot find the file specified.
0x8007000D ERROR_INVALID_DATA The information is invalid.
0x800F081F CBS_E_SOURCE_MISSING The source for the package or file non found.
0x80073712 ERROR_SXS_COMPONENT_STORE_CORRUPT The component store is in an inconsistent land.
0x800736CC ERROR_SXS_FILE_HASH_MISMATCH A component'south file does not lucifer 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 proper noun 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 non within the valid range.
0x80070057 ERROR_INVALID_PARAMETER The parameter is wrong.
0x800B0100 TRUST_E_NOSIGNATURE No signature was present in the field of study.
0x80092003 CRYPT_E_FILE_ERROR An mistake occurred while Windows Update reads or writes to a file.
0x800B0101 CERT_E_EXPIRED A required certificate is not inside its validity period when verifying confronting the current system clock or the fourth dimension stamp in the signed file.
0x8007371B ERROR_SXS_TRANSACTION_CLOSURE_INCOMPLETE Ane 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 only binary missing
0x800f0986 PSFX_E_APPLY_FORWARD_DELTA_FAILED Applying forrad delta failed
0x800f0982 PSFX_E_MATCHING_COMPONENT_NOT_FOUND Tin can't place matching component for hydration

Verify the integrity of resources

The Organization Update Readiness tool verifies the integrity of the following resources:

  • Files that are located in the following directories:
    • %SYSTEMROOT%\Servicing\Packages
    • %SYSTEMROOT%\WinSxS\Manifests
  • Registry data that is located under the following registry subkeys:
    • HKEY_LOCAL_MACHINE\Components
    • HKEY_LOCAL_MACHINE\Schema
    • HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Component Based Servicing

This list may be updated at any time.

When the System Update Readiness tool detects wrong manifests, Cabinets, or registry data, it may supervene upon the incorrect information with a corrected version.

Logging

The System Update Readiness tool creates a log file that captures any issues that the tool found or stock-still. The log file is located hither:

  • %SYSTEMROOT%\Logs\CBS\CheckSUR.log
  • %SYSTEMROOT%\Logs\CBS\CheckSUR.persist.log

How to fix errors that are found in the CheckSUR log file

To manually ready abuse errors that the Organisation Update Readiness tool detects but tin't fix, follow these steps:

  1. Open %SYSTEMROOT%\Logs\CBS\CheckSUR.log.

    Note

    %SYSTEMROOT% is an environs variable that saves the folder in which Windows is installed. For case, by and large the %SYSTEMROOT% folder is C:\Windows.

  2. Place the packages that the tool can't ready. For example, you may find the following in the log file:

                      Summary:  Seconds executed: 264   Found 3 errors   CBS MUM Missing Total Count: 3   Unavailable repair files:    servicing\packages\Package_for_KB958690_sc_0~31bf3856ad364e35~amd64~~6.0.one.half-dozen.mum   ...

    In this case, the package that is corrupted is KB958690.

  3. Download the package from Microsoft Download Center or Microsoft Update Catalog.

  4. Re-create the bundle (.msu) to the %SYSTEMROOT%\CheckSUR\packages directory. By default, this directory doesn't be and you need to create the directory.

  5. Rerun the System Update Readiness tool.

If you are a technical professional, see How to set up errors found in the CheckSUR.log for a more option on fixing errors in the CheckSUR.log.