Share via


System Update Readiness Tool is included as a part of Windows 8 and Windows Server 2012

Recently, while investigating an issue related to a .NET Framework hotfix installation problem, I reviewed the contents of the System Update Readiness Tool knowledge base article.  I noticed that the contents have been updated since the release of Windows 8.  Instead of needing to download and run a separate tool, the diagnostic and repair functionality in the System Update Readiness Tool is now built into Windows in Windows 8 and Windows Server 2012.  This change should make it much easier to investigate and fix issues on Windows 8 and Windows Server 2012 such as the one I described a while ago in this blog post.

You can find more detailed information about how to use System Update Readiness Tool functionality in Windows 8 and Windows Server 2012 in this blog post from the Windows servicing team.

Comments

  • Anonymous
    March 25, 2013
    Another great command you can use with /Cleanup-Image is /StartComponentCleanup, this will check if any updates are superseded and it will uninstall them dism /online /Cleanup-Image /StartComponentCleanup

  • Anonymous
    March 20, 2014
    I've written that command in Windows 8, but it says "Error: 87". Any idea which coul help me?

  • Anonymous
    March 28, 2014
    I have the same problem with mine.

  • Anonymous
    March 31, 2014
    The comment has been removed

  • Anonymous
    March 31, 2014
    I have also seen Error code 87, which can also be that you are not putting a space in front of the /.  It should be dism /online, not dism/online.  Aaron has it correct in his post, but I have run into that before and it took me a while to figure that out

  • Anonymous
    May 13, 2014
    The comment has been removed

  • Anonymous
    May 13, 2014
    The comment has been removed

  • Anonymous
    May 14, 2014
    Just a note, /AnalyzeComponentStore and /ResetBase are NOT supported in version prior to Windows 8.1 or Windows Server 2012 R2.  I should have said this in my first post. And another warning, if your Windows Update site is not the Microsoft site but a secondary site (at work), the /RestoreHealth may not work as expected because some images may not be available on a secondary Windows Update site.  For this case, use /LimitAccess to disallow DISM from contacting Windows Update for repair.  This is probably already mentioned in the blog linked above but not bad to have this here.

  • Anonymous
    August 31, 2015
    Windows 8.1 is bad for Computers.

  • Anonymous
    August 31, 2015
    Hi Anonymous - I'm sorry that you have had a bad experience with Windows 8.1.  There is information at www.microsoft.com/.../windows-10-upgrade about how to do a free upgrade to Windows 10, so you may want to look at that to see if it addresses the issues you're seeing with Windows 8.1.

    • Anonymous
      November 04, 2017
      Everything wrong with win8.1 is worse in win10. You don't even own your computer anymore in win10. Why are microsoft game partners "System Services" in win8.1?
  • Anonymous
    December 17, 2016
    How do I get to the right hand side of the spread sheet cand see the things on the far right side.