Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.



Windows 7: System Update Readiness Tool - CheckSur.log File Analyzis


System Update Readiness Tool - CheckSur.log File Analyzis

How to Analyze the System Update Readiness Tool CheckSur.log File
Published by Flavius
03 Sep 2010
Published by

How to Analyze the System Update Readiness Tool CheckSur.log File


warning   Warning

This article is intended only for advanced users


information   Information

This tutorial help you to fix many various Windows Update Errors e.g

0x80070001,0x80070002,0x80070003,0x80070005,0x8007000D,0x80070026,0x80070057, 0x80070246,
0x800703EE,0x80070490,0x800705B9,0x8007065E,0x800706BE,0x800736B3,0x800736CC, 0x80073701,0x8007370A,
0x8007370B,0x8007370D,0x80073712,0x8007371B,0x80080005,0x80092003,0x80092004, 0x800B0100,0x800B0101,
0x800F080D,0x800F0818,0x800F081F,0x800F0900,0x800F0A05


and many others

This tutorial can help you also with many issues with Turn Windows Features On or Off
This article applies to Vista/Windows Server 2008/Windows 7/Windows Server 2008 R2 (all versions



Many errors concerning the problem with Windows Update or with the enabling something in "Turn Windows features on or off" is caused by damages in the WinSxS, Packages folders, or in CBS,COMPONENTS keys.To diagnose and repair such damage, MS created tool Readiness Tool KB947821.When you run it, the tool tries to detect errors and fix them automatically.Unfortunately in practice in most cases the tool does not solve the problem automatically and user intervention is needed here.After completion of it's work the tool create CheckSur.log report in C:\Windows\Logs\CBS folder.Logs can look very different and different is the scale of difficulty of their analysis

Examples:

Code:
 
=================================
Checking System Update Readiness.
Binary Version 6.1.7600.20667
Package Version 8.0
2010-08-13 13:26
 
Checking Windows Servicing Packages
 
Checking Package Manifests and Catalogs
(f)    CBS MUM Corrupt    0x800F0900    servicing\Packages\Package_2_for_KB2079403~31bf3856ad364e35~amd64~~6.1.1.0.mum        Line 1: 
(f)    CBS Catalog Corrupt    0x800B0100    servicing\Packages\Package_2_for_KB2079403~31bf3856ad364e35~amd64~~6.1.1.0.cat        
(f)    CBS MUM Corrupt    0x800F0900    servicing\Packages\Package_for_KB2079403_RTM~31bf3856ad364e35~amd64~~6.1.1.0.mum        Line 1: 
(f)    CBS Catalog Corrupt    0x800B0100    servicing\Packages\Package_for_KB2079403_RTM~31bf3856ad364e35~amd64~~6.1.1.0.cat        
(f)    CBS MUM Corrupt    0x800F0900    servicing\Packages\Package_for_KB2079403~31bf3856ad364e35~amd64~~6.1.1.0.mum        Line 1: 
(f)    CBS Catalog Corrupt    0x800B0100    servicing\Packages\Package_for_KB2079403~31bf3856ad364e35~amd64~~6.1.1.0.cat        
 
Checking Package Watchlist
 
Checking Component Watchlist
 
Checking Packages
 
Checking Component Store
 
Summary:
Seconds executed: 355
 Found 6 errors
  CBS MUM Corrupt Total count: 3
  CBS Catalog Corrupt Total count: 3
 
Unavailable repair files:
    servicing\packages\Package_2_for_KB2079403~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_2_for_KB2079403~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_for_KB2079403_RTM~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_for_KB2079403_RTM~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_for_KB2079403~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_for_KB2079403~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_2_for_KB2079403~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_2_for_KB2079403~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_for_KB2079403_RTM~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_for_KB2079403_RTM~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_for_KB2079403~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_for_KB2079403~31bf3856ad364e35~amd64~~6.1.1.0.cat
Example 1.One of the easiest logs by the WU error 0x800B0100

Code:
 
=================================
Checking System Update Readiness.
Binary Version 6.1.7600.20667
Package Version 8.0
2010-08-17 00:14
 
Checking Windows Servicing Packages
 
Checking Package Manifests and Catalogs
(f)    CBS MUM Corrupt    0x800F0900    servicing\Packages\Package_1_for_KB982214~31bf3856ad364e35~amd64~~6.1.1.3.mum        Line 1: 
(f)    CBS Catalog Corrupt    0x800B0100    servicing\Packages\Package_1_for_KB982214~31bf3856ad364e35~amd64~~6.1.1.3.cat        
(f)    CBS MUM Corrupt    0x800F0900    servicing\Packages\Package_2_for_KB978886~31bf3856ad364e35~amd64~~6.1.1.0.mum        Line 1: 
(f)    CBS Catalog Corrupt    0x800B0100    servicing\Packages\Package_2_for_KB978886~31bf3856ad364e35~amd64~~6.1.1.0.cat        
(f)    CBS MUM Corrupt    0x800F0900    servicing\Packages\Package_2_for_KB980436~31bf3856ad364e35~amd64~~6.1.1.2.mum        Line 1: 
(f)    CBS Catalog Corrupt    0x800B0100    servicing\Packages\Package_2_for_KB980436~31bf3856ad364e35~amd64~~6.1.1.2.cat        
(f)    CBS MUM Corrupt    0x800F0900    servicing\Packages\Package_2_for_KB982799~31bf3856ad364e35~amd64~~6.1.1.0.mum        Line 1: 
(f)    CBS Catalog Corrupt    0x800B0100    servicing\Packages\Package_2_for_KB982799~31bf3856ad364e35~amd64~~6.1.1.0.cat        
(f)    CBS MUM Corrupt    0x800F0900    servicing\Packages\Package_3_for_KB980436~31bf3856ad364e35~amd64~~6.1.1.2.mum        Line 1: 
(f)    CBS Catalog Corrupt    0x800B0100    servicing\Packages\Package_3_for_KB980436~31bf3856ad364e35~amd64~~6.1.1.2.cat        
(f)    CBS MUM Corrupt    0x800F0900    servicing\Packages\Package_3_for_KB982799~31bf3856ad364e35~amd64~~6.1.1.0.mum        Line 1: 
(f)    CBS Catalog Corrupt    0x800B0100    servicing\Packages\Package_3_for_KB982799~31bf3856ad364e35~amd64~~6.1.1.0.cat        
(f)    CBS MUM Corrupt    0x800F0900    servicing\Packages\Package_for_KB978886_RTM~31bf3856ad364e35~amd64~~6.1.1.0.mum        Line 1: 
(f)    CBS Catalog Corrupt    0x800B0100    servicing\Packages\Package_for_KB978886_RTM~31bf3856ad364e35~amd64~~6.1.1.0.cat        
(f)    CBS MUM Corrupt    0x800F0900    servicing\Packages\Package_for_KB978886~31bf3856ad364e35~amd64~~6.1.1.0.mum        Line 1: 
(f)    CBS Catalog Corrupt    0x800B0100    servicing\Packages\Package_for_KB978886~31bf3856ad364e35~amd64~~6.1.1.0.cat        
(f)    CBS MUM Corrupt    0x800F0900    servicing\Packages\Package_for_KB980436_RTM~31bf3856ad364e35~amd64~~6.1.1.2.mum        Line 1: 
(f)    CBS Catalog Corrupt    0x800B0100    servicing\Packages\Package_for_KB980436_RTM~31bf3856ad364e35~amd64~~6.1.1.2.cat        
(f)    CBS MUM Corrupt    0x800F0900    servicing\Packages\Package_for_KB980436~31bf3856ad364e35~amd64~~6.1.1.2.mum        Line 1: 
(f)    CBS Catalog Corrupt    0x800B0100    servicing\Packages\Package_for_KB980436~31bf3856ad364e35~amd64~~6.1.1.2.cat        
(f)    CBS MUM Corrupt    0x800F0900    servicing\Packages\Package_for_KB982214_RTM~31bf3856ad364e35~amd64~~6.1.1.3.mum        Line 1: 
(f)    CBS Catalog Corrupt    0x800B0100    servicing\Packages\Package_for_KB982214_RTM~31bf3856ad364e35~amd64~~6.1.1.3.cat        
(f)    CBS MUM Corrupt    0x800F0900    servicing\Packages\Package_for_KB982214~31bf3856ad364e35~amd64~~6.1.1.3.mum        Line 1: 
(f)    CBS Catalog Corrupt    0x800B0100    servicing\Packages\Package_for_KB982214~31bf3856ad364e35~amd64~~6.1.1.3.cat        
(f)    CBS MUM Corrupt    0x800F0900    servicing\Packages\Package_for_KB982799_RTM~31bf3856ad364e35~amd64~~6.1.1.0.mum        Line 1: 
(f)    CBS Catalog Corrupt    0x800B0100    servicing\Packages\Package_for_KB982799_RTM~31bf3856ad364e35~amd64~~6.1.1.0.cat        
(f)    CBS MUM Corrupt    0x800F0900    servicing\Packages\Package_for_KB982799~31bf3856ad364e35~amd64~~6.1.1.0.mum        Line 1: 
(f)    CBS Catalog Corrupt    0x800B0100    servicing\Packages\Package_for_KB982799~31bf3856ad364e35~amd64~~6.1.1.0.cat        
(f)    CBS MUM Corrupt    0x800F0900    servicing\Packages\Package_for_KB983590_RTM~31bf3856ad364e35~amd64~~6.1.1.0.mum        Line 1: 
(f)    CBS Catalog Corrupt    0x800B0100    servicing\Packages\Package_for_KB983590_RTM~31bf3856ad364e35~amd64~~6.1.1.0.cat        
(f)    CBS MUM Corrupt    0x800F0900    servicing\Packages\Package_for_KB983590~31bf3856ad364e35~amd64~~6.1.1.0.mum        Line 1: 
(f)    CBS Catalog Corrupt    0x800B0100    servicing\Packages\Package_for_KB983590~31bf3856ad364e35~amd64~~6.1.1.0.cat        
 
Checking Package Watchlist
 
Checking Component Watchlist
 
Checking Packages
 
Checking Component Store
(f)    CSI Manifest All Zeros    0x00000000    winsxs\Manifests\amd64_microsoft-windows-rasrtutils_31bf3856ad364e35_6.1.7600.20738_none_69cd38af1d1dedd3.manifest    amd64_microsoft-windows-rasrtutils_31bf3856ad364e35_6.1.7600.20738_none_69cd38af1d1dedd3    
(f)    CSI Manifest and S256H Do Not Match    0x00000000    winsxs\Manifests\amd64_b2db70fde4bba871099a6486474b10fe_31bf3856ad364e35_6.1.7600.16612_none_3fa3f1dc518b21de.manifest    amd64_b2db70fde4bba871099a6486474b10fe_31bf3856ad364e35_6.1.7600.16612_none_3fa3f1dc518b21de    
(f)    CSI Manifest All Zeros    0x00000000    winsxs\Manifests\amd64_microsoft-windows-smbserver-common_31bf3856ad364e35_6.1.7600.20740_none_607b009642d9c626.manifest    amd64_microsoft-windows-smbserver-common_31bf3856ad364e35_6.1.7600.20740_none_607b009642d9c626    
(f)    CSI Manifest All Zeros    0x00000000    winsxs\Manifests\amd64_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.1.7600.20733_none_0fd0b57e990e2079.manifest    amd64_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.1.7600.20733_none_0fd0b57e990e2079    
(f)    CSI Manifest and S256H Do Not Match    0x00000000    winsxs\Manifests\amd64_c7bd203987149def1c2c18717d81d5e6_31bf3856ad364e35_6.1.7600.16612_none_e9da73e72f0f803d.manifest    amd64_c7bd203987149def1c2c18717d81d5e6_31bf3856ad364e35_6.1.7600.16612_none_e9da73e72f0f803d    
(f)    CSI Manifest All Zeros    0x00000000    winsxs\Manifests\x86_microsoft-windows-rasrtutils_31bf3856ad364e35_6.1.7600.20738_none_0dae9d2b64c07c9d.manifest    x86_microsoft-windows-rasrtutils_31bf3856ad364e35_6.1.7600.20738_none_0dae9d2b64c07c9d    
(f)    CSI Manifest Failed Catalog Check    0x00000000    winsxs\Manifests\x86_netfx-sos_dll_b03f5f7f11d50a3a_6.1.7600.16597_none_e877dfd2b7241dea.manifest    x86_netfx-sos_dll_b03f5f7f11d50a3a_6.1.7600.16597_none_e877dfd2b7241dea    
(f)    CSI Manifest All Zeros    0x00000000    winsxs\Manifests\amd64_netfx-mscordacwks_b03f5f7f11d50a3a_6.1.7600.20717_none_a126b806c861ae6e.manifest    amd64_netfx-mscordacwks_b03f5f7f11d50a3a_6.1.7600.20717_none_a126b806c861ae6e    
(f)    CSI Manifest All Zeros    0x00000000    winsxs\Manifests\x86_microsoft-windows-rasrtutils_31bf3856ad364e35_6.1.7600.16617_none_0d399fee4b938b9a.manifest    x86_microsoft-windows-rasrtutils_31bf3856ad364e35_6.1.7600.16617_none_0d399fee4b938b9a    
(f)    CSI Manifest All Zeros    0x00000000    winsxs\Manifests\amd64_microsoft-windows-smbserver-v1_31bf3856ad364e35_6.1.7600.16619_none_363c11500fe837b6.manifest    amd64_microsoft-windows-smbserver-v1_31bf3856ad364e35_6.1.7600.16619_none_363c11500fe837b6    
(f)    CSI Manifest All Zeros    0x00000000    winsxs\Manifests\amd64_netfx-sos_dll_b03f5f7f11d50a3a_6.1.7600.20717_none_89f4ffc7bc568a83.manifest    amd64_netfx-sos_dll_b03f5f7f11d50a3a_6.1.7600.20717_none_89f4ffc7bc568a83    
(f)    CSI Manifest All Zeros    0x00000000    winsxs\Manifests\amd64_microsoft-windows-rasrtutils_31bf3856ad364e35_6.1.7600.16617_none_69583b7203f0fcd0.manifest    amd64_microsoft-windows-rasrtutils_31bf3856ad364e35_6.1.7600.16617_none_69583b7203f0fcd0    
(f)    CSI Manifest All Zeros    0x00000000    winsxs\Manifests\amd64_netfx-sos_dll_b03f5f7f11d50a3a_6.1.7600.16597_none_a0caa8fba2a7f4e4.manifest    amd64_netfx-sos_dll_b03f5f7f11d50a3a_6.1.7600.16597_none_a0caa8fba2a7f4e4    
(f)    CSI Manifest All Zeros    0x00000000    winsxs\Manifests\amd64_microsoft-windows-smbserver-common_31bf3856ad364e35_6.1.7600.16619_none_601ad629299bb698.manifest    amd64_microsoft-windows-smbserver-common_31bf3856ad364e35_6.1.7600.16619_none_601ad629299bb698    
(f)    CSI Manifest All Zeros    0x00000000    winsxs\Manifests\amd64_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.1.7600.16610_none_0f59b7ad7fe2fcc8.manifest    amd64_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.1.7600.16610_none_0f59b7ad7fe2fcc8    
(f)    CSI Manifest All Zeros    0x00000000    winsxs\Manifests\wow64_microsoft-windows-security-schannel_31bf3856ad364e35_6.1.7600.20735_none_891f9920bc49aaed.manifest    wow64_microsoft-windows-security-schannel_31bf3856ad364e35_6.1.7600.20735_none_891f9920bc49aaed    
(f)    CSI Manifest All Zeros    0x00000000    winsxs\Manifests\amd64_netfx-mscorwks_dll_b03f5f7f11d50a3a_6.1.7600.16597_none_bf383e53d6b20cfc.manifest    amd64_netfx-mscorwks_dll_b03f5f7f11d50a3a_6.1.7600.16597_none_bf383e53d6b20cfc    
(f)    CSI Manifest and S256H Do Not Match    0x00000000    winsxs\Manifests\amd64_3b21d80f6ec46f3f54e45b47c5decd14_31bf3856ad364e35_6.1.7600.20735_none_311ba0baba7f06d6.manifest    amd64_3b21d80f6ec46f3f54e45b47c5decd14_31bf3856ad364e35_6.1.7600.20735_none_311ba0baba7f06d6    
(f)    CSI Manifest All Zeros    0x00000000    winsxs\Manifests\amd64_microsoft-windows-smbserver-v1_31bf3856ad364e35_6.1.7600.20740_none_369c3bbd29264744.manifest    amd64_microsoft-windows-smbserver-v1_31bf3856ad364e35_6.1.7600.20740_none_369c3bbd29264744    
(f)    CSI Manifest All Zeros    0x00000000    winsxs\Manifests\amd64_microsoft-windows-smbserver-v2_31bf3856ad364e35_6.1.7600.20740_none_36916bd1292e6335.manifest    amd64_microsoft-windows-smbserver-v2_31bf3856ad364e35_6.1.7600.20740_none_36916bd1292e6335    
(f)    CSI Manifest All Zeros    0x00000000    winsxs\Manifests\amd64_microsoft-windows-smbserver-v2_31bf3856ad364e35_6.1.7600.16619_none_363141640ff053a7.manifest    amd64_microsoft-windows-smbserver-v2_31bf3856ad364e35_6.1.7600.16619_none_363141640ff053a7    
(f)    CSI Manifest All Zeros    0x00000000    winsxs\Manifests\amd64_netfx-mscorwks_dll_b03f5f7f11d50a3a_6.1.7600.20717_none_a862951ff060a29b.manifest    amd64_netfx-mscorwks_dll_b03f5f7f11d50a3a_6.1.7600.20717_none_a862951ff060a29b    
(f)    CSI Manifest All Zeros    0x00000000    winsxs\Manifests\amd64_netfx-mscordacwks_b03f5f7f11d50a3a_6.1.7600.16597_none_b7fc613aaeb318cf.manifest    amd64_netfx-mscordacwks_b03f5f7f11d50a3a_6.1.7600.16597_none_b7fc613aaeb318cf    
(f)    CSI Manifest All Zeros    0x00000000    winsxs\Manifests\amd64_microsoft-windows-security-schannel_31bf3856ad364e35_6.1.7600.16612_none_7e53f0fd6ebdc541.manifest    amd64_microsoft-windows-security-schannel_31bf3856ad364e35_6.1.7600.16612_none_7e53f0fd6ebdc541    
(f)    CSI Manifest All Zeros    0x00000000    winsxs\Manifests\wow64_microsoft-windows-security-schannel_31bf3856ad364e35_6.1.7600.16612_none_88a89b4fa31e873c.manifest    wow64_microsoft-windows-security-schannel_31bf3856ad364e35_6.1.7600.16612_none_88a89b4fa31e873c    
(f)    CSI Manifest All Zeros    0x00000000    winsxs\Manifests\amd64_microsoft-windows-security-schannel_31bf3856ad364e35_6.1.7600.20735_none_7ecaeece87e8e8f2.manifest    amd64_microsoft-windows-security-schannel_31bf3856ad364e35_6.1.7600.20735_none_7ecaeece87e8e8f2    
 
Summary:
Seconds executed: 419
 Found 58 errors
  CSI Manifest All Zeros Total count: 22
  CSI Manifest and S256H Do Not Match Total count: 3
  CSI Manifest Failed Catalog Check Total count: 1
  CBS MUM Corrupt Total count: 16
  CBS Catalog Corrupt Total count: 16
 
Unavailable repair files:
    winsxs\manifests\amd64_microsoft-windows-rasrtutils_31bf3856ad364e35_6.1.7600.20738_none_69cd38af1d1dedd3.manifest
    winsxs\manifests\amd64_b2db70fde4bba871099a6486474b10fe_31bf3856ad364e35_6.1.7600.16612_none_3fa3f1dc518b21de.manifest
    winsxs\manifests\amd64_microsoft-windows-smbserver-common_31bf3856ad364e35_6.1.7600.20740_none_607b009642d9c626.manifest
    winsxs\manifests\amd64_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.1.7600.20733_none_0fd0b57e990e2079.manifest
    winsxs\manifests\amd64_c7bd203987149def1c2c18717d81d5e6_31bf3856ad364e35_6.1.7600.16612_none_e9da73e72f0f803d.manifest
    winsxs\manifests\x86_microsoft-windows-rasrtutils_31bf3856ad364e35_6.1.7600.20738_none_0dae9d2b64c07c9d.manifest
    winsxs\manifests\x86_netfx-sos_dll_b03f5f7f11d50a3a_6.1.7600.16597_none_e877dfd2b7241dea.manifest
    winsxs\manifests\amd64_netfx-mscordacwks_b03f5f7f11d50a3a_6.1.7600.20717_none_a126b806c861ae6e.manifest
    winsxs\manifests\x86_microsoft-windows-rasrtutils_31bf3856ad364e35_6.1.7600.16617_none_0d399fee4b938b9a.manifest
    winsxs\manifests\amd64_microsoft-windows-smbserver-v1_31bf3856ad364e35_6.1.7600.16619_none_363c11500fe837b6.manifest
    winsxs\manifests\amd64_netfx-sos_dll_b03f5f7f11d50a3a_6.1.7600.20717_none_89f4ffc7bc568a83.manifest
    winsxs\manifests\amd64_microsoft-windows-rasrtutils_31bf3856ad364e35_6.1.7600.16617_none_69583b7203f0fcd0.manifest
    winsxs\manifests\amd64_netfx-sos_dll_b03f5f7f11d50a3a_6.1.7600.16597_none_a0caa8fba2a7f4e4.manifest
    winsxs\manifests\amd64_microsoft-windows-smbserver-common_31bf3856ad364e35_6.1.7600.16619_none_601ad629299bb698.manifest
    winsxs\manifests\amd64_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.1.7600.16610_none_0f59b7ad7fe2fcc8.manifest
    winsxs\manifests\wow64_microsoft-windows-security-schannel_31bf3856ad364e35_6.1.7600.20735_none_891f9920bc49aaed.manifest
    winsxs\manifests\amd64_netfx-mscorwks_dll_b03f5f7f11d50a3a_6.1.7600.16597_none_bf383e53d6b20cfc.manifest
    winsxs\manifests\amd64_3b21d80f6ec46f3f54e45b47c5decd14_31bf3856ad364e35_6.1.7600.20735_none_311ba0baba7f06d6.manifest
    winsxs\manifests\amd64_microsoft-windows-smbserver-v1_31bf3856ad364e35_6.1.7600.20740_none_369c3bbd29264744.manifest
    winsxs\manifests\amd64_microsoft-windows-smbserver-v2_31bf3856ad364e35_6.1.7600.20740_none_36916bd1292e6335.manifest
    winsxs\manifests\amd64_microsoft-windows-smbserver-v2_31bf3856ad364e35_6.1.7600.16619_none_363141640ff053a7.manifest
    winsxs\manifests\amd64_netfx-mscorwks_dll_b03f5f7f11d50a3a_6.1.7600.20717_none_a862951ff060a29b.manifest
    winsxs\manifests\amd64_netfx-mscordacwks_b03f5f7f11d50a3a_6.1.7600.16597_none_b7fc613aaeb318cf.manifest
    winsxs\manifests\amd64_microsoft-windows-security-schannel_31bf3856ad364e35_6.1.7600.16612_none_7e53f0fd6ebdc541.manifest
    winsxs\manifests\wow64_microsoft-windows-security-schannel_31bf3856ad364e35_6.1.7600.16612_none_88a89b4fa31e873c.manifest
    winsxs\manifests\amd64_microsoft-windows-security-schannel_31bf3856ad364e35_6.1.7600.20735_none_7ecaeece87e8e8f2.manifest
    servicing\packages\Package_1_for_KB982214~31bf3856ad364e35~amd64~~6.1.1.3.mum
    servicing\packages\Package_1_for_KB982214~31bf3856ad364e35~amd64~~6.1.1.3.mum
    servicing\packages\Package_2_for_KB978886~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_2_for_KB978886~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_2_for_KB980436~31bf3856ad364e35~amd64~~6.1.1.2.mum
    servicing\packages\Package_2_for_KB980436~31bf3856ad364e35~amd64~~6.1.1.2.mum
    servicing\packages\Package_2_for_KB982799~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_2_for_KB982799~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_3_for_KB980436~31bf3856ad364e35~amd64~~6.1.1.2.mum
    servicing\packages\Package_3_for_KB980436~31bf3856ad364e35~amd64~~6.1.1.2.mum
    servicing\packages\Package_3_for_KB982799~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_3_for_KB982799~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_for_KB978886_RTM~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_for_KB978886_RTM~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_for_KB978886~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_for_KB978886~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_for_KB980436_RTM~31bf3856ad364e35~amd64~~6.1.1.2.mum
    servicing\packages\Package_for_KB980436_RTM~31bf3856ad364e35~amd64~~6.1.1.2.mum
    servicing\packages\Package_for_KB980436~31bf3856ad364e35~amd64~~6.1.1.2.mum
    servicing\packages\Package_for_KB980436~31bf3856ad364e35~amd64~~6.1.1.2.mum
    servicing\packages\Package_for_KB982214_RTM~31bf3856ad364e35~amd64~~6.1.1.3.mum
    servicing\packages\Package_for_KB982214_RTM~31bf3856ad364e35~amd64~~6.1.1.3.mum
    servicing\packages\Package_for_KB982214~31bf3856ad364e35~amd64~~6.1.1.3.mum
    servicing\packages\Package_for_KB982214~31bf3856ad364e35~amd64~~6.1.1.3.mum
    servicing\packages\Package_for_KB982799_RTM~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_for_KB982799_RTM~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_for_KB982799~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_for_KB982799~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_for_KB983590_RTM~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_for_KB983590_RTM~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_for_KB983590~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_for_KB983590~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_1_for_KB982214~31bf3856ad364e35~amd64~~6.1.1.3.cat
    servicing\packages\Package_1_for_KB982214~31bf3856ad364e35~amd64~~6.1.1.3.cat
    servicing\packages\Package_2_for_KB978886~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_2_for_KB978886~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_2_for_KB980436~31bf3856ad364e35~amd64~~6.1.1.2.cat
    servicing\packages\Package_2_for_KB980436~31bf3856ad364e35~amd64~~6.1.1.2.cat
    servicing\packages\Package_2_for_KB982799~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_2_for_KB982799~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_3_for_KB980436~31bf3856ad364e35~amd64~~6.1.1.2.cat
    servicing\packages\Package_3_for_KB980436~31bf3856ad364e35~amd64~~6.1.1.2.cat
    servicing\packages\Package_3_for_KB982799~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_3_for_KB982799~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_for_KB978886_RTM~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_for_KB978886_RTM~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_for_KB978886~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_for_KB978886~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_for_KB980436_RTM~31bf3856ad364e35~amd64~~6.1.1.2.cat
    servicing\packages\Package_for_KB980436_RTM~31bf3856ad364e35~amd64~~6.1.1.2.cat
    servicing\packages\Package_for_KB980436~31bf3856ad364e35~amd64~~6.1.1.2.cat
    servicing\packages\Package_for_KB980436~31bf3856ad364e35~amd64~~6.1.1.2.cat
    servicing\packages\Package_for_KB982214_RTM~31bf3856ad364e35~amd64~~6.1.1.3.cat
    servicing\packages\Package_for_KB982214_RTM~31bf3856ad364e35~amd64~~6.1.1.3.cat
    servicing\packages\Package_for_KB982214~31bf3856ad364e35~amd64~~6.1.1.3.cat
    servicing\packages\Package_for_KB982214~31bf3856ad364e35~amd64~~6.1.1.3.cat
    servicing\packages\Package_for_KB982799_RTM~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_for_KB982799_RTM~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_for_KB982799~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_for_KB982799~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_for_KB983590_RTM~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_for_KB983590_RTM~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_for_KB983590~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_for_KB983590~31bf3856ad364e35~amd64~~6.1.1.0.cat
Example 2.Harder log with WU Error 0x800B0100."Unavailable repair files" section indicate all damaged components.

Code:
(f)    CSI Missing Deployment Key    0x00000000    microsoft-w..anguagepack_31bf3856ad364e35_6.1.7600.16385_d4c01c6932a42ec3    HKLM\Components\CanonicalData\Deployments    
(f)    CSI Missing Deployment Key    0x00000000    microsoft-w..anguagepack_31bf3856ad364e35_6.1.7600.16385_99fe045407bd44b1    HKLM\Components\CanonicalData\Deployments    
(f)    CSI Missing Deployment Key    0x00000000    microsoft-w..anguagepack_31bf3856ad364e35_6.1.7600.16385_fa5e4dffe1e88db4    HKLM\Components\CanonicalData\Deployments    
(f)    CSI Missing Identity    0x00000000    identity    amd64_microsoft-windows-i..iccontent.resources_31bf3856ad364e35_6.1.7600.16385_en-us_06458c544252951f    
(fix)    CSI Missing Identity    CSI Registry Item Repaired    amd64_microsoft-windows-i..iccontent.resources_31bf3856ad364e35_6.1.7600.16385_en-us_06458c544252951f
(f)    CSI Missing Deployment Key    0x00000000    microsoft-w..anguagepack_31bf3856ad364e35_6.1.7600.16385_8a9c86005f761e26    HKLM\Components\CanonicalData\Deployments    
(f)    CSI Missing Deployment Key    0x00000000    microsoft-w..anguagepack_31bf3856ad364e35_6.1.7600.16385_506389b6220fd1c7    HKLM\Components\CanonicalData\Deployments    
(f)    CSI Missing Deployment Key    0x00000000    microsoft-w..anguagepack_31bf3856ad364e35_6.1.7600.16385_b7dc3d9314539d96    HKLM\Components\CanonicalData\Deployments    
(f)    CSI Missing Deployment Key    0x00000000    microsoft-w..anguagepack_31bf3856ad364e35_6.1.7600.16385_924ea401e9dabd40    HKLM\Components\CanonicalData\Deployments    
(f)    CSI Missing Deployment Key    0x00000000    microsoft-w..anguagepack_31bf3856ad364e35_6.1.7600.16385_d08b17d43b43dd40    HKLM\Components\CanonicalData\Deployments    
(f)    CSI Missing Deployment Key    0x00000000    microsoft-w..anguagepack_31bf3856ad364e35_6.1.7600.16385_d11d45ff9c5b8d99    HKLM\Components\CanonicalData\Deployments    
(f)    CSI Missing Deployment Key    0x00000000    microsoft-w..anguagepack_31bf3856ad364e35_6.1.7600.16385_2bee90910a243965    HKLM\Components\CanonicalData\Deployments    
(f)    CSI Missing Deployment Key    0x00000000    microsoft-w..anguagepack_31bf3856ad364e35_6.1.7600.16385_c69d3d11fe62fca4    HKLM\Components\CanonicalData\Deployments    
(f)    CSI Missing Identity    0x00000000    identity    amd64_microsoft-windows-i..orybrowse.resources_31bf3856ad364e35_6.1.7600.16385_en-us_bcfe3adf37b82f21    
(fix)    CSI Missing Identity    CSI Registry Item Repaired    amd64_microsoft-windows-i..orybrowse.resources_31bf3856ad364e35_6.1.7600.16385_en-us_bcfe3adf37b82f21
(f)    CSI Missing Deployment Key    0x00000000    wcf-nonhttp..anguagepack_31bf3856ad364e35_6.1.7600.16385_ad7e47bf75b19e45    HKLM\Components\CanonicalData\Deployments    
(f)    CSI Missing Deployment Key    0x00000000    microsoft-w..anguagepack_31bf3856ad364e35_6.1.7600.16385_6f32e6840ceb657b    HKLM\Components\CanonicalData\Deployments    
(f)    CSI Missing Deployment Key    0x00000000    microsoft-w..anguagepack_31bf3856ad364e35_6.1.7600.16385_13c68ed0db89a233    HKLM\Components\CanonicalData\Deployments    
(f)    CSI Missing Deployment Key    0x00000000    microsoft-w..anguagepack_31bf3856ad364e35_6.1.7600.16385_362b9f1a38b9376f    HKLM\Components\CanonicalData\Deployments
Example 3.Unable to open "Turn Windows features On or off" (part of log).Components assigned as (Fix) means that the tool repaired the problem automatically in these places.

Code:
=================================
Checking System Update Readiness.
Binary Version 6.0.6002.22285
Package Version 7.0
2010-04-07 10:30
 
Checking Windows Servicing Packages
 
Checking Package Manifests and Catalogs
 
Checking Package Watchlist
 
Checking Component Watchlist
(f)    CBS Watchlist Component Missing    0x80070002    amd64_bthmtpenum.inf_31bf3856ad364e35_0.0.0.0_none_7ff053f99479855b    Microsoft-Windows-WPD7IP-SKU-Package~31bf3856ad364e35~amd64~~7.0.6002.18112.bthmtpenum    Package registry presence failed, possibly an orphaned package on package watchlist
(f)    CBS Watchlist Component Missing    0x80070002    amd64_wpdfs.inf_31bf3856ad364e35_0.0.0.0_none_a5e566b2d3236f6d    Microsoft-Windows-WPD7IP-SKU-Package~31bf3856ad364e35~amd64~~7.0.6002.18112.wpdfs    Package registry presence failed, possibly an orphaned package on package watchlist
(f)    CBS Watchlist Component Missing    0x80070002    amd64_wpdmtp.inf_31bf3856ad364e35_0.0.0.0_none_9f92d6d487384aad    Microsoft-Windows-WPD7IP-SKU-Package~31bf3856ad364e35~amd64~~7.0.6002.18112.wpdmtp    Package registry presence failed, possibly an orphaned package on package watchlist
(f)    CBS Watchlist Component Missing    0x80070002    amd64_wpdmtphw.inf_31bf3856ad364e35_0.0.0.0_none_78371ba92ff2a242    Microsoft-Windows-WPD7IP-SKU-Package~31bf3856ad364e35~amd64~~7.0.6002.18112.wpdmtphw    Package registry presence failed, possibly an orphaned package on package watchlist
 
Checking Packages
 
Checking Component Store
 
Summary:
Seconds executed: 2230
 Found 4 errors
  CBS Watchlist Component Missing Total count: 4
+
System Update Readiness Tool - CheckSur.log File Analyzis-cs6.jpg
Example 4.Here you can see orphaned keys from any incorrectly uninstalled packages.Messages "CBS Watchlist Component Missing 0x80070002"+
"Package registry presence failed, possibly an orphaned package on package watchlist" means these strings are orphaned and you have to remove them.Strings are in third column,in second column are listed subkeys where you can find corrupted strings.In above example you have to only delete strings -don't touch keys.Above image shows one of problematic key in registry

Code:
=================================
Checking System Update Readiness.
Binary Version 6.1.7600.20667
Package Version 8.0
2010-07-20 05:20
 
Checking Windows Servicing Packages
 
Checking Package Manifests and Catalogs
 
Checking Package Watchlist
(f)    CBS Watchlist Package Missing    0x80070005    Microsoft-Windows-Client-Features-Package~31bf3856ad364e35~x86~~0.0.0.0    Package_2_for_KB978542~31bf3856ad364e35~x86~~6.1.1.1    Package registry presence failed, possibly an orphaned package on package watchlist
 
Checking Component Watchlist
(f)    CBS Watchlist Component Missing    0x80070005    x86_microsoft-windows-mail-core-dll_31bf3856ad364e35_0.0.0.0_none_7c58b7336d745ee2    Package_2_for_KB978542~31bf3856ad364e35~x86~~6.1.1.1    Package registry presence failed, possibly an orphaned package on package watchlist
(f)    CBS Watchlist Component Missing    0x80070005    x86_microsoft-windows-mail-core-dll_31bf3856ad364e35_0.0.0.0_none_7c58b7336d745ee2    Package_2_for_KB978542~31bf3856ad364e35~x86~~6.1.1.1    Package registry presence failed, possibly an orphaned package on package watchlist
 
Checking Packages
(f)    CBS Registry Error    0x00000005    Package_2_for_KB978542~31bf3856ad364e35~x86~~6.1.1.1    Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\    Failed to open store sub key
 
Checking Component Store
(f)    CSI Corrupt Keyform: Permission Denied    0x00000005    116e2eed80d..b378328db7c_31bf3856ad364e35_6.1.7600.16543_c700b2077690d8b3    HKLM\Components\CanonicalData\Deployments    
(f)    CSI Corrupt Keyform: Permission Denied    0x00000005    116e2eed80d..b378328db7c_31bf3856ad364e35_6.1.7600.16543_c700b2077690d8b3    HKLM\Components\CanonicalData\Deployments    
 
Summary:
Seconds executed: 156
 Found 6 errors
  CSI Corrupt Keyform: Permission Denied Total count: 2
  CBS Registry Error Total count: 1
  CBS Watchlist Package Missing Total count: 1
  CBS Watchlist Component Missing Total count: 2
Example 5.Readiness Tool can detect issues with permissions too.Messages "CBS Watchlist Component Missing 0x80070005"+ "Package registry presence failed, possibly an orphaned package on package watchlist" means incorrectly permissions
in this key.You need to restore original permissions.


Identification damages componets

I.Damages in C:\Windows\Servicing\Packages

This folder contains a pairs of files with *.cat and *.mum extensions

It's very easy to identify corrupted components from this folder.As you can see from above examples mostly components have the following form

Package_x_for_{update ID}~31bf3856ad364e35~x86~~6.x.x.x.cat /mum (for 32bit system)
Package_x_for_{update ID}~31bf3856ad364e35~amd64~~6.x.x.x.cat /mum (for 64bit system)

and here is very easy to read source of component and it doesn't require more comments.If you cannot identify any file from this folder that means it's native component and you have to look for it on your installation disk.


II.Damages in C:\Windows\WinSxS

Here it's worse to identify.

METHOD I
-Check components in your installation disk

//see also point ACCESS FILES ON YOUR INSTALL DISK//

METHOD II
-If you have also damages in Packages folder,first download & unpack updates which are corrupted in Packages,next
try to find remains damaged files in unpacked updates.

//see also point UNPACKING UPDATES//

METHOD III
-Compare with another computer

Popular method,I'm using it many times too,however, this method has the following disadvantages:

-there are different states of updates in different systems
-the same update may in many various ways modify WinSxS structure -it depends in example from language version
-Some updates are designed specifically for hardware configuration

METHOD IV
-Analyze COMPONENTS hive (hard method)

warning   Warning

In Windows 7 COMPONENTS hive is not defaultly loaded to registry.OS load this hive only when you use Windows Updates or
"Turn Windows Features on or off" .If you don't have this hive in registry you have to load COMPONENTS hive to registry
manualy


Informations about WinSxS subfolders and *. manifest files you can find in subkey of HKLM\Components\DerivedData\Components,which have exactly the same name as the name of folder or file (without *. manifest extension) when you find a proper key you have to find in there any string containing in the name 31bf3856ad364e35 sequence,then look for the subkey in the HKLM\Components\CanonicalData\Catalogs contains also this string, take note of it's name and now navigate to the HKLM\Components\CanonicalData\Deployments and locate the string with the same name as mentioned before subkey in Catalogs key and now you can identify a hotfix for a particular component. If no such information that means it's native component and we have to look for it on the installation disk, but there is a possibility that you have been unlucky and it belongs to any 3p MS application .

information   Information

31bf3856ad364e35 sequence here is so called Public Key Token.For interested additional lecture CLICK


EXAMPLE

We want to identify the origin of the component
C:\Windows\WinSxS\manifests\amd64_microsoft-windows-wow64_31bf3856ad364e35_6.1.7600.20602_none_c4f7d8ca09dfa6fb.manifest

1.Find key
HKLM\Components\DerivedData\Components\amd64_microsoft-windows-wow64_31bf3856ad364e35_6.1.7600.20602_none_c4f7d8ca09dfa6fb

System Update Readiness Tool - CheckSur.log File Analyzis-cs1.png


There you can see a string containing in the name 31bf3856ad364e35 sequence,the full string name is c! 15ad33c7794 8bc2ac288b3_31bf3856ad364e35_6.1.7600.20602_a019e7b42992cde3 ..- Remember the name.

2.Next find the same string in HKLM\Components\CanonicalData\Catalogs.You can figure it contain the subkey

System Update Readiness Tool - CheckSur.log File Analyzis-cs2.png

HKLM\Components\CanonicalData\Catalogs\83c9a24d60423e6d7d62e9fe7532d616cd9230c418a5e2bc280d577037eb1 39a

3.And finally you have to find subkey in HKLM\Components\CanonicalData\Deployments which contain string with the same name as mentioned in point 2 subkey in Catalogs.

System Update Readiness Tool - CheckSur.log File Analyzis-cs3.png


As you can see from this figure this component belongs to KB978637.

ACCESS FILES ON YOUR INSTALL DISK

Two ways -classic method by using imagex tool

Access Vista Install DVD Files - Vista Forums
WIM File - Extract and Modify

or better and more confortable way in my opinion by using 7-zip or WinRAR

Extract Files from Vista Installation DVD - Vista Forums
Extract Files from Windows 7 Installation DVD

UNPACKING UPDATES

1.Download update from Microsoft Download Center and place it in any folder
2.Run console and type following commands

expand -f:*{update name}.msu {destination folder}
expand -f:*{update name}.cab {destination folder}

to unpack Windows6.1-KB980302-x86.msu which already is in C:\Temp you have to type these commands

expand -f:* C:\TEMP\Windows6.1-KB980302-x86.msu C:\TEMP
expand -f:* C:\TEMP\Windows6.1-KB980302-x86.cab C:\TEMP

warning   Warning

Don't use any 3p archiver tools like 7-zip or WinRAR on *.cab files from updates,because these tools incompletely unpack such kind of archives.Strange,but there is no this problem on *.cab files from service packs.


Files update.cat,update.mum,update-bf.cat,update-bf.mum

Almost all the extracted components have the same name as those contained in subfolders of C:\Windows except for those
files that are listed in this section,however, giving them the correct name is not difficult.Extracted *.cat,*.mum files have the following form:

Package_{number}_for_{update ID}~31bf3856ad364e35~x86~~6.x.x.x.cat (for system 32bit)

Package_{number}_for_{update ID}~31bf3856ad364e35~amd64~~6.x.x.x.cat (for system 64bit)

so then correct name for update.cat will be

Package_for_{update ID}~31bf3856ad364e35~x86~~6.x.x.x.cat (for system 32bit)

Package_for_{update ID}~31bf3856ad364e35~amd64~~6.x.x.x.cat (for system 64bit)

and of course correct name of update.mum

Package_for_{update ID}~31bf3856ad364e35~x86~~6.x.x.x.mum (for system 32bit)

Package_for_{update ID}~31bf3856ad364e35~amd64~~6.x.x.x.mum (for system 64bit)

The file update-bf.cat we need to compare with the files with that names

Package_{number}_for_{update ID}_bf~31bf3856ad364e35~x86~~6.x.x.x.cat (for system 32bit)

Package_{number}_for_{update ID}_bf~31bf3856ad364e35~amd64~~6.x.x.x.cat (for system 64bit)

so proper name for update-bf.cat,update-bf.mum will be:

Package_for_{update ID}_bf~31bf3856ad364e35~x86~~6.x.x.x.cat /mum (for system 32bit)

Package_for_{update ID}_bf~31bf3856ad364e35~amd64~~6.x.x.x.cat /mum (for system 64bit)

EXAMPLE

unpacked KB980302 for Windows 7 32bit


for this update update.cat/mum will be

package_for_kb980302~31bf3856ad364e35~x86~~6.1.1.0.cat /mum

and update-bf.cat

package_for_kb980302_bf~31bf3856ad364e35~x86~~6.1.1.0.cat /mum

Note   Note

The 4th and 3th char from the right in package name indicate kernel version of system
6.0 -Vista/Windows Server 2008,6.1 -Windows 7/Windows Server 2008 R2


Unpacking service pack

to unpack any service pack you have to type following commands

{service pack name} /x:{destination folder}
expand -f:* {service pack name} {destination folder}

i.e for SP2 for Vista 32bit which is stored in C:\Temp the commands are following


C:\Temp\Windows6.0-KB948465-X86.exe /x:C:\Temp
expand -f:* C:\Temp\Windows6.0-KB948465-X86.exe C:\Temp


Files update.cat,update.mum in unpacked service packs:

For service packs you have to also rename update.cat,update.mum files.The proper names are following

for Vista SP1 32bit:

VistaSP1-KB936330~31bf3856ad364e35~x86~~6.0.0.18000.cat
VistaSP1-KB936330~31bf3856ad364e35~x86~~6.0.0.18000.mum

for vista SP1 64bit

VistaSP1-KB936330~31bf3856ad364e35~amd64~~6.0.0.18000.cat
VistaSP1-KB936330~31bf3856ad364e35~amd64~~6.0.0.18000.mum

for Vista SP2 32bit

VistaSP2-KB948465~31bf3856ad364e35~x86~~6.0.0.18005.cat
VistaSP2-KB948465~31bf3856ad364e35~x86~~6.0.0.18005.mum

for Vista SP2 64bit

VistaSP2-KB948465~31bf3856ad364e35~amd64~~6.0.0.18005.cat
VistaSP2-KB948465~31bf3856ad364e35~amd64~~6.0.0.18005.mum

REPLACING CORRUPTED FILES

When you have already prepared all required files from different sources you can now replace corrupted files
by using any below method.

METHOD I

warning   Warning

This method affects only on C:\Windows\Servicing\Packages and C:\Windows\WinSxS\Manifests folders.This method will not work if you have damages in other locations.


1.copy all *.cat,*.mum files to C:\Windows\Temp\CheckSur\Servicing\Packages folder,and all *.manifest files to C:\Windows\Temp\CheckSur\WinSxS\Manifests
2.Run Readiness Tool again

METHOD II

1.Navigate to folders where you have corrupted files,takeownership of these folders and add your account to have
full control
2.Replace corrupted files
3.Restore original permissions

Tip   Tip

I do not recommend using this method on WinSxS folder,practically there are many obstacles with changing permissions for it,i.e files using by any process.My suggestion:if you have damages in WinSxS I recommend to use METHOD III or IV
to replace files.Personally I'm using METHOD II if there are damages only in C:\Windows\Servicing\Packages


METHOD III


1.Create folder and give the name whatever you want i.e Packs.In this folder create Windows folder and it's subfolders according with folders structure in original Windows folder -of course you need only to create empty folders only for required files (not all)

EXAMPLE

Suppose now you have damaged files only in C:\Windows\WinSxS\Manifests and C:\Windows\Servicing\Packages
folders,so you have to create only folders Packs\Windows\WinSxS\Manifests and Packs\Windows\Servicing\Packages
and place there files and this is all.


2.When your Packs folder is ready,place it on directly on root C:

3.Boot your installation disk (or if you don't have it use special recovery disk)
go to command prompt and type:

robocopy {boot partition}:\Packs {boot partition}:\ /E /IS

where boot partition -the partition where is installed your OS

In mostly cases boot partition is the first partition,so in this case the command will be:

robocopy C:\Packs C:\ /E /IS

warning   Warning

If in your computer boot partition is not the first partition you have to change drive letter in my commands.
Check your partitions status in diskmgmt.msc before you boot installation disk.


As you can see above command merge original Windows folder with Windows subfolder from Packs folder

METHOD IV

Use any live CD or any linux i.e Ubuntu or second system if you have,to replace corrupted files.

Tip   Tip

When finished repair I suggest to install problematic updates from Microsoft Download Center,sometimes there are
strange problems with updates from Windows Updates,I don't know why -these ones from Microsoft Download Center will always pass.





warning   Warning
  • Sometimes Readiness Tool may not detect all issues at once.Sometimes you have to run it many times to diagnose & repair all errors.
  • If tool returns repeatedly the same errors in log although you did correctly requested operations then in this case you have to uninstall update which relate to damaged component.If unable to do that in "Programs and Features" try command prompt -details:CLICK
  • If there are too many damages or unable to fix something the only solution is to make repair install Repair Install






.

Comment

 System Update Readiness Tool - CheckSur.log File Analyzis





Tutorial Tools



Similar help and support threads for2: System Update Readiness Tool - CheckSur.log File Analyzis
Windows 7 Tutorial Category
System Update Readiness Tool is Not Working Windows Updates & Activation
System Update Readiness Tool problem... Windows Updates & Activation
System Update Readiness Tool Windows Updates & Activation
System Update Readiness Tool and other questions. Windows Updates & Activation

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 03:26 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33