How to fix errors found in the CheckSUR.log

Article ID: 2700601 - View products that this article applies to.
Expand all | Collapse all

Introduction

This article describes how to resolve servicing corruption that the System Update Readiness tool (CheckSUR) has found but is unable to correct on its own. You can find this information in the %WinDir%\Logs\CBS\CheckSUR.log

Note: Make sure you download and run the most recent version of CheckSUR.exe, as it gets updated periodically.
http://support.microsoft.com/kb/947821

Using the CheckSur log
  1. If the System Update Readiness tool has fixed all found errors, the CheckSUR.log will show the following:

    Summary:
    Seconds executed: 100
    Found 10 errors
    Fixed 10 errors
    In this scenario you should no longer have any servicing corruption on your computer. If you are still getting errors after this you will need to troubleshoot the specific error message, to find the root cause of the failure.
  2. If you get the Unavailable repair files message, this indicates that some of the inconsistent files found by the tool cannot be fixed as the correct versions of the replacement files are not carried by the tool. After this message appears, the CheckSUR.log will show the following:

    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
    servicing\packages\Package_for_KB958690_sc~31bf3856ad364e35~amd64~~6.0.1.6.mum
    servicing\packages\Package_for_KB958690~31bf3856ad364e35~amd64~~6.0.1.6.mum  
    servicing\packages\Package_for_KB958690_sc_0~31bf3856ad364e35~amd64~~6.0.1.6.cat  
    servicing\packages\Package_for_KB958690_sc~31bf3856ad364e35~amd64~~6.0.1.6.cat
    servicing\packages\Package_for_KB958690~31bf3856ad364e35~amd64~~6.0.1.6.cat
    winsxs\manifests\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.0.6002.18005_none_0b4ada54c46c45b0.manifest
    winsxs\manifests\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.0.6002.18005_none_676975d87cc9b6e6.manifest
    Steps to resolve this issue
    1. Download the package that contains the missing files. For this example you should download the Windows6.0-KB958690-x64.msu.
    2. Copy the Windows6.0-KB958690-x64.msu to the Packages folder under %WinDir%\Temp\CheckSUR. You may need to create the directory.
    3. Re-run the System Update Readiness tool.
    4. If it is not obvious what package the missing files came from, you will need to get these files from another machine. Make sure the machine you are copying files from is the same OS version and system architecture.
    5. Copy the files to the %WinDir%\Temp\CheckSUR directory of the corrupted computer in the following subdirectory format and then re-run the System Update Readiness tool:
      • All files of type *.mum and *.cat should be placed in the %WinDir%\Temp\CheckSUR\Packages directory
      • All files of type *.manifest should be placed in the %windir%\temp\CheckSUR\manifests directory

  3. If you get a Payload File Missing message, then the binary required is not available. This means that the issue is not fixed. The CheckSUR.log will show the following

    Summary:
    Seconds executed: 100
    Found 3 errors
    Fix 1 errors
    CSI Payload File Missing Total count: 3
    Fix CSI Payload File Missing Total Count: 1

    (f) CSI Payload File Missing 0x00000000 admparse.dll x86_microsoft-windows-ie-adminkitmostfiles_31bf3856ad364e35_6.0.6000.16386_none_abfb5fd109dad8b8 servicing_31bf3856ad364e35_6.0.6000.16386_none_23ddbf36a8a961bc
    (f) CSI Payload File Missing 0x00000000 bootmgr x86_microsoft-windows-b..re-bootmanager-pcat_31bf3856ad364e35_6.0.6000.16386_none_c0f2f087b6457236
    (fix) CSI Payload File Missing 0x00000000 bootmgr x86_microsoft-windows-b..re-bootmanager-pcat_31bf3856ad364e35_6.0.6000.16386_none_c0f2f087b6457236
    (f) CSI Payload File Missing 0x00000000 winload.exe x86_microsoft-windows-b..environment-windows_31bf3856ad364e35_6.0.6000.16386_none_6701d52e8fdf8d45
    Steps to resolve this issue
    1. Find out which payload files are missing by looking at CheckSUR.log. Identify any line that have (f) that is not followed by (fix). From the previous example there are two payload files that were not fixed.
    2. You will need to get these files from another machine. Make sure the machine you are copying files from is the same OS version and system architecture.
    3. Paste the files into the proper subdirectory under %windir%\winsxs

Note: Before placing the files in the appropriate locations, you may need to grant yourself permissions to edit the folder’s contents; below is a quick guide on how to achieve this.
  • At an elevated command prompt: takeown /f <Path_And_File_Name>
    Example: takeown /f C:\Windows\winsxs\ x86_microsoft-windows-ie-adminkitmostfiles_31bf3856ad364e35_6.0.6000.16386_none_abfb5fd109dad8b8
  • Now grant full access to the file:  icacls <Path_And_File_Name> /grant Administrators:F
    Example: icacls C:\Windows\winsxs\x86_microsoft-windows-ie-adminkitmostfiles_31bf3856ad364e35_6.0.6000.16386_none_abfb5fd109dad8b8 /grant Administrators:F
  • Now replace the file with a known good copy:  <Copy Path_And_File_Name_Of_Source_File Path_And_File_Name_Of_Destination>
    Example: copy C:\Temp\admparse.dll c:\Windows\winsxs\x86_microsoft-windows-ieadminkitmostfiles_31bf3856ad364e35_6.0.6000.16386_none_abfb5fd109dad8b8\admparse.dll

Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use for other considerations.

Properties

Article ID: 2700601 - Last Review: April 12, 2012 - Revision: 1.0
APPLIES TO
  • Windows Vista Enterprise
  • Windows 7 Enterprise
  • Windows 7 Professional
  • Windows 7 Ultimate
  • Windows Server 2008 Datacenter
  • Windows Server 2008 Enterprise
  • Windows Server 2008 R2 Datacenter
  • Windows Server 2008 R2 Enterprise
  • Windows Server 2008 R2 Standard
  • Windows Server 2008 Standard
Keywords: 
KB2700601

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com