What to do if the corrupt files do not mention an KB code? Re-run the System Update Readiness tool which will use the files in the %windir%\Temp\CheckSUR\servicing\packages folder to repair the corrupt or missing files. Copy the expanded *.mum and *.cat files to %windir%\Temp\CheckSUR\servicing\packages:Ĭopy C:\temp\KB2685939\*.mum %windir%\Temp\CheckSUR\servicing\packages\Ĭopy C:\temp\KB2685939\*.cat %windir%\Temp\CheckSUR\servicing\packages\ĥ. Expand the package using the expand command (this assumes the package was downloaded to C:\temp and that we’re expanding to C:\temp\KB2685939):Įxpand C:\temp\Windows6.1-KB2685939-圆4.msu /f:* C:\temp\KB2685939ģ. Download the appropriate update package for KB2685939 for the target system from the Microsoft Download Center.Ģ. To repair, you can follow these instructions.ġ. You will find the KB article number of files that cannot be repaired in the CheckSUR log file: For any corruption which cannot be automatically repaired, we can still use this utility to manually fix these items. If CheckSUR is able to automatically repair files, it will do so and report this in the log file.
Once installed, a log is generated under %windir%\Logs\CBS\CheckSUR.log. This utility is often referred to as CheckSUR – short for Check System Update Readiness. The utility installs as a MSU package on older platforms, and is baked in for Windows 8 and Server 2012 with the DISM utility.
The tool is available for all editions of Windows since Vista/Server 2008 and is published under KB947821. Microsoft has developed a System Update Readiness tool which can identify and repair Windows system file corruption that could prevent other updates from being installed.
0 kommentar(er)
