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
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.
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:
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 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
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
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
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