Fix Update Problems With Windows DISM

By | December 26, 2015
Print Friendly, PDF & Email

Fix Windows Update Errors with Windows DISM

Some of the most frustrating Windows problems you can encounter are those that involve Windows Update. It seems that a significant percentage of Windows users encounter errors with Windows Update at least once. And this is especially annoying if you’re trying upgrade from Windows 7 SP1 or Windows 8.1 and you get errors that tell you that your upgrade to Windows 10 has failed and your system updates will be removed and your system restored back to the previous version of Windows.  Sometimes you are not aware of these errors until you’ve wasted and hour or two trying to upgrade to Windows 10.

This information, while not written for upgrading to Windows 10, can solve many problems and error messages you may encounter when trying to upgrade from Windows 7 SP1  or Windows 8.1 to Windows 10, especially error codes 0xC1900101 – 0x30018.

You may find this tip useful for correcting problems with upgrading to Windows 10, as well as fixing the Windows Update component in your version of Windows.

DISM  ( Deployment Image Servicing and Management ) comes with Windows 10 and Windows 8. Windows 7 users will need to download System Update Readiness Tool (links included below).

The following information is from Microsoft (see this page ) and we can give you no warranty expressed or implied that this will fix your errors. And we cannot guarantee that if you use these tools incorrectly that no damage to your Windows OS will result. We publish this only for those of you who’ve tried everything short of reinstalling Windows to fix problems with Windows Update – or who have tried and failed to upgrade their Windows 7 SP1 or Windows 8.1 computer to Windows 10.

Here is the information about fixing Windows Update problems with DISM or System Update Readiness tool.

Fix Windows Update errors by using the DISM or System Update Readiness tool

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

Note for Home users: This article is intended for Support agents and IT professionals. If you’re looking for more information about troubleshooting Windows updates, go to the following Windows website:

See the error codes that you may receive when there are corrupted files.

If you have some other problems that prevent you from installing updates by using Windows Update, view Troubleshoot problems with installing updates.


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

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

  1. 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-clickCommand 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.
  2. 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 /Restorehealth

    Important 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 /LimitAccess

    Note 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.

  3. Type the following command and press Enter.
    It may take several minutes for the command operation to be completed.

    sfc /scannow
  4. Close 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 found or fixed. %windir% is the folder in which Windows is installed. For example, the %windir% folder is C:\Windows.

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.
    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 WindowsThis tool is updated regularly, we recommend that you always download the latest version.

The rest of this article by Microsoft and download links for Windows 7 users can be found here.

2 thoughts on “Fix Update Problems With Windows DISM

  1. JoninOz

    Thank you TC & EB,

    I will file this for future use in my ‘Win 10 Maintenance’ folder.

    May your Ball Drop keep you safe, healthy and forge a Happy New Year to you both, and your families.

    Kind Regards,


  2. John Gregson

    Running Win 10; with all updates.
    File Explorer.
    I have generated a small file in Excel 2010; this has needed some corrections to get a
    final version.
    When I try to open this file using File Explorer, I find this File is most difficult to find.
    In my opinion, I wish that I could get the old Win 7 File explorer back.
    Win 10 seems to have a category called ‘Recent Files’; what does Win 10 consider recent?
    I have a strong dislike for Win 10 File Explorer; any suggestions?


Leave a Reply

Your email address will not be published. Required fields are marked *