Partager via

The New and Improved CheckSUR

  • Article

One of the most used and arguably most efficient tools that we utilize when troubleshooting Servicing issues, prior to Windows 8/Windows 2012, is the System Update Readiness tool(also known as CheckSUR). However, as we continue to improve our operating systems, we must continue to improve our troubleshooting tools as well. Thus, I want to introduce the “Updated CheckSur”

Improvements for the System Update Readiness Tool in Windows 7 and Windows Server 2008 R2
https://support.microsoft.com/en-us/kb/2966583

In short, previously, CheckSUR would load its payload locally on the machine and run the executable to attempt to resolve any discrepancies it detects in the package store.

With these improvements, the utility no longer carries a payload.  It also doesn’t require repeated downloads of the CheckSUR package that was previously required. The new CheckSUR package will stay installed until removed by the user.

I’m sure you’re wondering: without the payload, how will CheckSUR resolve any issues? After installing this patch and rebooting (which is required), the CheckSUR functionality is now exposed through the DISM command:

DISM /Online /Cleanup-Image /Scanhealth

This command should seem familiar if you have used DISM for troubleshooting on any Win8+ operating system. There is, however, no restorehealth/checkhealth with this update.  Scanhealth provides the same functionality as restorehealth in Win8+ OS’s and the CheckSUR tool did previously.

Another new feature is that CheckSUR will now also detect corruption on components for Internet Explorer.

A few extra points to note:

  • The “Updated CheckSUR” is specific to only run on Windows 7 SP1 and Windows 2008 R2 SP1
  • CheckSUR can only be run on an online OS
  • CheckSUR can be used as a scheduled proactive method by scheduling a task to run /scanhealth as a desired time to ensure that the system is periodically checked for corruption
  • Manual steps that previously could be utilized to run CheckSUR are no longer available with the update to CheckSUR

One of my favorite parts of the update is that the results are still logged in the c:\windows\logs\CBS\checksur.log and still gives the same layout and information surrounding its findings once the file has been accessed and opened. I will be creating another article shortly that discusses some steps to take when you encounter a CheckSUR.log with errors.

Thank You
Nicholas Debnam
Support Escalation Engineer

Comments

  • Anonymous
    July 23, 2015
    Excellent article. Good to know this information.
  • Anonymous
    July 23, 2015
    Nicholas: after reading its still unclear from this article, when was SUR actually being enhanced for this new capability? In May 2014, or now in July 2015? Differently said, I dont understand the actuality of this post: why did you write this headsup today, and not 1 year ago?
  • Anonymous
    July 23, 2015
    The link for the 2008 R2 version is from 2014? I tried to install anyway and it says it's already installed.

    "The scanhealth option is unknown." also occurs if I try and run it.

    How do I tell if I've got the latest CheckSUR?
  • Anonymous
    August 07, 2015
    Hi John,

    Thanks for the info. I wonder why you waited a year (judging by file dates in the KB arricle) to share this :) I have a couple of suggestions for your next post about errors.

    1. Why does pretty much every machine show unavailable repair files related to IE spelling and hyphenation in the log?http://pastebin.com/mUUZyG9z

    2. What would you advise in this http://pastebin.com/Xt2vGAfL case?

    Thanks,
    Vadim

  • Anonymous
    August 09, 2015
    The comment has been removed
  • Anonymous
    August 09, 2015
    Justin, if you check within the Control Panel (or using any other method that you prefer to view installed updates) and search for "KB2966583" it will tell you if it is installed or not. If you are receiving "The scanhealth option is unknown" error from running the DISM command my guess is because this KB actually is not installed on the machine.
  • Anonymous
    August 10, 2015
    Hi Vadim,

    If the results from the CheckSUR package are restricted to the IE Catalogue and Mum files they can be ignored.

    Regarding your second issue, DISM's repair source is the default packaging method that the machine uses. For example, if the machine gets updates from WU only, then it will use WU as the repair source. If it uses WSUS/ConfigMan or some 3rd party patching method, it will use that. Try giving the machine direct access to WU and rerun the command and review the results.
  • Anonymous
    August 18, 2015
    Morning, Not sure what is meant by "•CheckSUR can only be run on an online OS"? Is this for internet access? None of our 2008 R2 servers have internet access and all are updated via our WSUS server. Does this than mean that this update will not work on those?
    Thanks,
    Tony
  • Anonymous
    August 18, 2015
    @Tony,

    Online means the OS is up and running. If the OS was a virtual machine, you cannot mount the VHD/VHDX in some other OS and run CHECKSUR against it.
  • Anonymous
    August 18, 2015
    @Tony,

    Online means the OS is up and running. If the OS was a virtual machine, you cannot mount the VHD/VHDX in some other OS and run CHECKSUR against it.
  • Anonymous
    May 17, 2017
    To those having issues with error "The scanhealth option is unknown" -- I had the same issue when I left off the /Cleanup-Image flag. Apparently the /Scanhealth flag is a sub-option to /Cleanup-Image.
  • Anonymous
    August 19, 2017
    I guess an updated tool is good and all, but if it doesnt go download missing KB MSU's that it knows it needs to apply, whats the point?