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
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.
Support Escalation Engineer