Home » How To » How to fix Windows Update Errors Using DISM or System Update Readiness tool

If there are corruption errors, Windows updates and service packs may fail to install. If a system file is damaged, you may not install the update. If your system file is corrupted, you may fix Windows Update Errors using the DISM or System Update Readiness tool.

fix-windows-update-errors-using-dism

How to fix Windows update errors:

Windows 10, Windows 8.1, Windows 8, Windows Server 2012 R2 or Windows Server 2012

To resolve this problem, Windows see the inbox Deployment Image Servicing and Management (DISM) tool to fix the Windows update error and try to install the Windows update or service pack again.

  • Swipe in from the right edge of your device screen then tap Search and then type Command Prompt in the Search box to open an elevated command prompt. Or if you are using mouse, point the cursor to the lower-left corner and then click Search. Type Command Prompt in the Search box, right-click Command Prompt, and then click on the option Run as administrator. Type the password if you are prompted for an administrator password or click Allow for a confirmation.
  • Type the following command written below, and then press/tap Enter.

It may take a few minutes for the command operation to get completed so be patience.

DISM.exe /Online /Cleanup-image /Restorehealth

Please note that when you run this command, DISM uses Windows Update to find the files that are needed to fix corruption. However, if your Windows Update client is already damaged, use a Windows side-by-side folder from a removable media, such as the Windows DVD or from a network share as the source of the files or use a running Windows installation as the repair source. Run the following command to do this:

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

Important Note: Replace the C:\RepairSource\Windows placeholder according to the location of your repair source.

  • Type the following command written below, and then press/tap Enter.

 It may take a few minutes for the command operation to get completed so be patience.

sfc /scannow        

  • Now close the command prompt and run Windows Update again.

Note: DISM creates a log file (%windir%/Logs/CBS/CBS.log) that holds any issues that the tool found or fixed. %windir% is the folder where Windows is installed.

For Windows 7, Windows Vista, Windows Server 2008 R2 or Windows Server 2008

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

  1. Download the System Update Readiness tool according to the version of Windows running on your computer (32 or 64-bit version of Windows).

The System Update Readiness tool is updated regularly so it is recommended to you that download the latest version always.

  1. Install and run the tool.
  • On the Download Center webpage, click Download and then do one of the following:
  • Click Open or Run to install the tool immediately and then follow on screen instructions.
  • Or if you want to install the tool later, click Save, and then download the installation file to your computer. Double-click the file when you are ready to install it.
  • Click Yes in the Windows Update Standalone Installer dialog box.
  • The tool starts installing and automatically runs. Though it takes less than 15 minutes to run, but on some devices, it may take much longer. Don’t click/tap on Cancel button even if the progress bar seems to stop because scan is still running.
  • Click Close when the installation process is complete.
  • Now try to reinstall the update or service pack that you were trying to install earlier but failed to install.

Description of the common corruption errors that may reflect

For your reference, the following list includes the possible error code with Windows Update:

Code     Error      Description

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.

How to Fix Errors Found in the CheckSUR.log

Follow the instructions written in this article to manually fix corruption errors that the tool detects but you are unable to fix them.

Download the package directly from Microsoft Update Catalog

You may try to download the update package directly from Microsoft Update Catalog and then manually install the update package.

For instance, you may be facing issues while trying to install update 3006137 from Windows Update in Windows 7 and this situation it will be a better option to download the update package and try to install the update manually again. To do this, follow the steps written below:

  • Open Internet Explorer and open Microsoft Update Catalog there.
  • In the search box, type the update number that you want to download and then, click Search.
  • In the search results, find the update that is appropriate to your operating system and then click Add for adding the update to your basket.
  • To open your basket, click on view basket.
  • Select a location for the update you are downloading by clicking on the browse button and then click on Continue.
  • Once the download process is done, click Close. Now you can find a folder contains the update package at the location you specified to it.
  • To install the update, open the folder and then double click on the update package.

If you are able of installing the Windows update or service pack successfully, you are finished, but if System Update Readiness Tool cannot find the cause of the problem and your problem is not fixed, contact expert technicians for further assistance.

What does the System Update Readiness Tool do?

Verifies the integrity of resources

The System Update Readiness Tool verifies the integrity of the following resources:

  1. Files of the following directories:
  • %SYSTEMROOT%\Servicing\Packages
  • %SYSTEMROOT%\WinSxS\Manifests
  1. Registry data 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 because if the System Update Readiness Tool finds incorrect manifests, registry data, or Cabinets, it tend to replace the incorrect data with a corrected version.

Logging

The System Update Readiness Tool creates a log file that holds any issues found or fixed by the tool. The log file location may be either of the following:

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

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

Follow the steps written below to manually fix corruption errors that the System Update Readiness Tool detects, but unable to fix:

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

Important Note: %SYSTEMROOT% is an environment variable that saves the folder where Windows is installed.

  • Find out the packages that the tool can’t fix. For instance, you may see 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.1.6.mum   …

In this case, KB958690 is the corrupted package.

  • Download the package from Microsoft Update Catalog or Microsoft Download Center.
  • Copy the package (.msu) to the %SYSTEMROOT%\CheckSUR\packages directory. You need to create the directory as this directory doesn’t exist by default.
  • Run the System Update Readiness Tool again.

Like every other suite of software application, Windows also has some flaws. Although Microsoft always try to find the solution for the issue as soon as they are detected. If you are a Windows user and facing any problem, you can seek the assistance of certified technicians of In2pcfix at an affordable cost. We render support for Windows 7 and other versions of Windows.