Note: Make sure you download and run the most recent version of CheckSUR.exe, as it gets updated periodically.
Using the CheckSur log
- If the System Update Readiness tool has fixed all found errors, the CheckSUR.log will show the following:Summary: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.
Seconds executed: 100
Found 10 errors
Fixed 10 errors
- 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:
winsxs\manifests\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.0.6002.18005_none_676975d87cc9b6e6.manifestSteps to resolve this issue
- Download the package that contains the missing files. For this example you should download the Windows6.0-KB958690-x64.msu.
- Copy the Windows6.0-KB958690-x64.msu to the Packages folder under %WinDir%\Temp\CheckSUR. You may need to create the directory.
- Re-run the System Update Readiness tool.
- 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.
- 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
- 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 followingSummary:
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_6701d52e8fdf8d45Steps to resolve this issue
- 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.
- 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.
- Paste the files into the proper subdirectory under %windir%\winsxs
- 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
Article ID: 2700601 - Last Review: Nov 14, 2016 - Revision: 1