[SOLVED] Win 7 Pro SP1 x64 (but Czech) - install Windows Updates Error 0x80073712 problem

A

alpak

Member
Joined
Mar 4, 2018
Posts
8
Hi,

after some problems with the sleep mode then the HDD reports some troubles and during the checkdisk process it leads to destroy some files that is important to update.

I've learned some infos about the command sfc /scannow and discover the stuff in the directories c:\Windows\Logs\CBS\, c:\Windows\servicing\Packages\ and c:\Windows\winsxs\

Bellow I attached the Logs CheckSUR.log, CheckSUR.persist.log, CBS.log and the log from the SFCFix program.

View attachment CBS_SFCFix_log.zip

Here is the log from CheckSUR.log. In the report are only 44 errors now

Code: 
=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2018-03-06 17:58

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs
(f)    CBS Catalog Corrupt    0x800B0100    servicing\Packages\Package_for_KB3142024~31bf3856ad364e35~amd64~~6.1.1.1.cat        
(f)    CBS MUM Corrupt    0x800F0900    servicing\Packages\Package_for_KB3161561~31bf3856ad364e35~amd64~~6.1.1.1.mum        Line 1: xÏ^€úÿÿ

Checking Package Watchlist

Checking Component Watchlist
(f)    CBS Watchlist Component Missing    0x80070002    amd64_microsoft-windows-i..osticstap.resources_31bf3856ad364e35_0.0.0.0_cs-cz_c79c802cfe5f7d70    Package_4_for_KB3124275~31bf3856ad364e35~amd64~~11.2.1.0    Package registry presence failed, possibly an orphaned package on package watchlist
(f)    CBS Watchlist Component Missing    0x80070002    amd64_microsoft-windows-i..resources.resources_31bf3856ad364e35_0.0.0.0_cs-cz_780f763a31263780    Package_4_for_KB3124275~31bf3856ad364e35~amd64~~11.2.1.0    Package registry presence failed, possibly an orphaned package on package watchlist
(f)    CBS Watchlist Component Missing    0x80070002    amd64_microsoft-windows-ie-f12.resources_31bf3856ad364e35_0.0.0.0_cs-cz_ace55c0c731c0f53    Package_4_for_KB3124275~31bf3856ad364e35~amd64~~11.2.1.0    Package registry presence failed, possibly an orphaned package on package watchlist
(f)    CBS Watchlist Component Missing    0x80070002    amd64_microsoft-windows-inetres-adm.resources_31bf3856ad364e35_0.0.0.0_cs-cz_ac402851970959ae    Package_4_for_KB3124275~31bf3856ad364e35~amd64~~11.2.1.0    Package registry presence failed, possibly an orphaned package on package watchlist
(f)    CBS Watchlist Component Missing    0x80070002    wow64_microsoft-windows-inetres-adm.resources_31bf3856ad364e35_0.0.0.0_cs-cz_b694d2a3cb6a1ba9    Package_4_for_KB3124275~31bf3856ad364e35~amd64~~11.2.1.0    Package registry presence failed, possibly an orphaned package on package watchlist
(f)    CBS Watchlist Component Missing    0x80070002    x86_microsoft-windows-i..osticstap.resources_31bf3856ad364e35_0.0.0.0_cs-cz_6b7de4a946020c3a    Package_4_for_KB3124275~31bf3856ad364e35~amd64~~11.2.1.0    Package registry presence failed, possibly an orphaned package on package watchlist

Checking Packages
(f)    CBS Registry Error    0x80070002    Package_109_for_KB4034664~31bf3856ad364e35~amd64~~6.1.1.4        failed to get Visibility
(f)    CBS Registry Error    0x80070002    Package_146_for_KB3126587~31bf3856ad364e35~amd64~~6.1.1.1        failed to get CurrentState
(f)    CBS Registry Error    0x80070002    Package_146_for_KB3126587~31bf3856ad364e35~amd64~~6.1.1.1        failed to get Visibility
(f)    CBS Registry Error    0x80070002    Package_190_for_KB4025341~31bf3856ad364e35~amd64~~6.1.1.6        failed to get CurrentState
(f)    CBS Registry Error    0x80070103    Package_2_for_KB3123479~31bf3856ad364e35~amd64~~6.1.1.0        failed to get owner for package.
(f)    CBS Registry Error    0x80070002    Package_for_KB3123479~31bf3856ad364e35~amd64~~6.1.1.0        failed to get CurrentState
(f)    CBS Registry Error    0x80070002    Package_for_KB3123479~31bf3856ad364e35~amd64~~6.1.1.0        failed to get Visibility
(f)    CBS Registry Error    0x80070103    Package_for_KB3146706_SP1~31bf3856ad364e35~amd64~~6.1.1.2        failed to get owner for package.

Checking Component Store
(f)    CSI Manifest Failed Catalog Check    0x00000000    winsxs\Manifests\x86_microsoft-windows-cryptbase_31bf3856ad364e35_6.1.7601.23796_none_67a231b92598f2a9.manifest    x86_microsoft-windows-cryptbase_31bf3856ad364e35_6.1.7601.23796_none_67a231b92598f2a9    
(f)    CSI Manifest Failed Catalog Check    0x00000000    winsxs\Manifests\amd64_microsoft-windows-i..rolviewer.resources_31bf3856ad364e35_11.2.9600.18738_cs-cz_415574e8eac936fc.manifest    amd64_microsoft-windows-i..rolviewer.resources_31bf3856ad364e35_11.2.9600.18738_cs-cz_415574e8eac936fc    
(f)    CSI Manifest Failed Catalog Check    0x00000000    winsxs\Manifests\x86_microsoft-windows-i..timezones.resources_31bf3856ad364e35_6.1.7601.23452_cs-cz_42829bc5124e5821.manifest    x86_microsoft-windows-i..timezones.resources_31bf3856ad364e35_6.1.7601.23452_cs-cz_42829bc5124e5821    
(f)    CSI Manifest Failed Catalog Check    0x00000000    winsxs\Manifests\x86_microsoft-windows-cryptbase_31bf3856ad364e35_6.1.7601.23642_none_67d43e4725740471.manifest    x86_microsoft-windows-cryptbase_31bf3856ad364e35_6.1.7601.23642_none_67d43e4725740471    
(f)    CSI Manifest Failed Catalog Check    0x00000000    winsxs\Manifests\amd64_78fb46c8e56bf0f43ffb5d3ba0fd14f7_31bf3856ad364e35_6.1.7601.23739_none_2cd8a08941041850.manifest    amd64_78fb46c8e56bf0f43ffb5d3ba0fd14f7_31bf3856ad364e35_6.1.7601.23739_none_2cd8a08941041850    
(f)    CSI Manifest Failed Catalog Check    0x00000000    winsxs\Manifests\x86_wpf-windowsbase_31bf3856ad364e35_6.1.7601.23744_none_59dd782cbf3e5c90.manifest    x86_wpf-windowsbase_31bf3856ad364e35_6.1.7601.23744_none_59dd782cbf3e5c90    
(f)    CSI Manifest Failed Catalog Check    0x00000000    winsxs\Manifests\amd64_3512821798256a2184eb49f1af00ffba_31bf3856ad364e35_11.2.9600.18349_none_11ac7de8b6cbe353.manifest    amd64_3512821798256a2184eb49f1af00ffba_31bf3856ad364e35_11.2.9600.18349_none_11ac7de8b6cbe353    
(f)    CSI Manifest Failed Catalog Check    0x00000000    winsxs\Manifests\wow64_microsoft-windows-wow64_31bf3856ad364e35_6.1.7601.23040_none_d1056ab63b89509e.manifest    wow64_microsoft-windows-wow64_31bf3856ad364e35_6.1.7601.23040_none_d1056ab63b89509e    
(f)    CSI Manifest Failed Catalog Check    0x00000000    winsxs\Manifests\wow64_microsoft-windows-security-digest_31bf3856ad364e35_6.1.7601.23040_none_a3acedc3e0ef329e.manifest    wow64_microsoft-windows-security-digest_31bf3856ad364e35_6.1.7601.23040_none_a3acedc3e0ef329e    
(f)    CSI Manifest Failed Catalog Check    0x00000000    winsxs\Manifests\amd64_microsoft-windows-ie-lowreg_31bf3856ad364e35_11.2.9600.17239_none_8ab9d04ff8de0c86.manifest    amd64_microsoft-windows-ie-lowreg_31bf3856ad364e35_11.2.9600.17239_none_8ab9d04ff8de0c86    
(f)    CSI Manifest All Zeros    0x00000000    winsxs\Manifests\amd64_microsoft-windows-sechost_31bf3856ad364e35_6.1.7601.23040_none_e64dd537fccf9399.manifest    amd64_microsoft-windows-sechost_31bf3856ad364e35_6.1.7601.23040_none_e64dd537fccf9399    
(f)    CSI Manifest Failed Catalog Check    0x00000000    winsxs\Manifests\amd64_dcd2cfdae88cd53864cea441eb6f5970_31bf3856ad364e35_11.2.9600.18349_none_40017b3789d2ca48.manifest    amd64_dcd2cfdae88cd53864cea441eb6f5970_31bf3856ad364e35_11.2.9600.18349_none_40017b3789d2ca48    
(f)    CSI Manifest Failed Catalog Check    0x00000000    winsxs\Manifests\amd64_microsoft-windows-c..tionauthorityclient_31bf3856ad364e35_6.1.7601.22923_none_3621766a6c6dc5e1.manifest    amd64_microsoft-windows-c..tionauthorityclient_31bf3856ad364e35_6.1.7601.22923_none_3621766a6c6dc5e1    
(f)    CSI Manifest Failed Catalog Check    0x00000000    winsxs\Manifests\wow64_microsoft-windows-systemrestore-main_31bf3856ad364e35_6.1.7601.23040_none_afbf729417791cfe.manifest    wow64_microsoft-windows-systemrestore-main_31bf3856ad364e35_6.1.7601.23040_none_afbf729417791cfe    
(f)    CSI Manifest Failed Catalog Check    0x00000000    winsxs\Manifests\wow64_microsoft-windows-i..rnational-timezones_31bf3856ad364e35_6.1.7601.23452_none_7e1e31626dd272f3.manifest    wow64_microsoft-windows-i..rnational-timezones_31bf3856ad364e35_6.1.7601.23452_none_7e1e31626dd272f3    
(f)    CSI Manifest Failed Catalog Check    0x00000000    winsxs\Manifests\amd64_079d22e65563eba632b22cfb3e1199f5_31bf3856ad364e35_6.1.7601.23717_none_13888216793a3e2b.manifest    amd64_079d22e65563eba632b22cfb3e1199f5_31bf3856ad364e35_6.1.7601.23717_none_13888216793a3e2b    
(f)    CSI Manifest Failed Catalog Check    0x00000000    winsxs\Manifests\x86_microsoft-windows-i..tocolimplementation_31bf3856ad364e35_11.2.9600.18762_none_880588e7fe97ec0d.manifest    x86_microsoft-windows-i..tocolimplementation_31bf3856ad364e35_11.2.9600.18762_none_880588e7fe97ec0d    
(f)    CSI Manifest Failed Catalog Check    0x00000000    winsxs\Manifests\x86_microsoft-windows-c..tionauthorityclient_31bf3856ad364e35_6.1.7601.23418_none_da128bfeb403df4b.manifest    x86_microsoft-windows-c..tionauthorityclient_31bf3856ad364e35_6.1.7601.23418_none_da128bfeb403df4b    
(f)    CSI Manifest Failed Catalog Check    0x00000000    winsxs\Manifests\amd64_microsoft-windows-ie-versioninfo_31bf3856ad364e35_11.2.9600.18762_none_e16110174a1c6a2c.manifest    amd64_microsoft-windows-ie-versioninfo_31bf3856ad364e35_11.2.9600.18762_none_e16110174a1c6a2c    
(f)    CSI Manifest Failed Catalog Check    0x00000000    winsxs\Manifests\x86_microsoft-windows-rpc-http_31bf3856ad364e35_6.1.7601.23154_none_a25e7ce8b6d453c6.manifest    x86_microsoft-windows-rpc-http_31bf3856ad364e35_6.1.7601.23154_none_a25e7ce8b6d453c6    
(f)    CSI Manifest Failed Catalog Check    0x00000000    winsxs\Manifests\wow64_microsoft-windows-security-ntlm_31bf3856ad364e35_6.1.7601.23154_none_e58bc2a1c6c96061.manifest    wow64_microsoft-windows-security-ntlm_31bf3856ad364e35_6.1.7601.23154_none_e58bc2a1c6c96061    
(f)    CSI Manifest Failed Catalog Check    0x00000000    winsxs\Manifests\wow64_microsoft-windows-wow64_31bf3856ad364e35_6.1.7601.18839_none_d08fc84f225b45b0.manifest    wow64_microsoft-windows-wow64_31bf3856ad364e35_6.1.7601.18839_none_d08fc84f225b45b0    
(f)    CSI Manifest Failed Catalog Check    0x00000000    winsxs\Manifests\wow64_microsoft-windows-winsrv_31bf3856ad364e35_6.1.7601.18839_none_1ee896e7e7614992.manifest    wow64_microsoft-windows-winsrv_31bf3856ad364e35_6.1.7601.18839_none_1ee896e7e7614992    
(f)    CSI Manifest Failed Catalog Check    0x00000000    winsxs\Manifests\amd64_e8479767d28f487c65027556b0d110be_31bf3856ad364e35_6.1.7601.23713_none_bb37f0d493d8e9ea.manifest    amd64_e8479767d28f487c65027556b0d110be_31bf3856ad364e35_6.1.7601.23713_none_bb37f0d493d8e9ea    
(f)    CSI Manifest Failed Catalog Check    0x00000000    winsxs\Manifests\amd64_a4c66b93bb605ede299d2eed2d814ed7_31bf3856ad364e35_6.1.7601.23715_none_8e5be6aae0f183e6.manifest    amd64_a4c66b93bb605ede299d2eed2d814ed7_31bf3856ad364e35_6.1.7601.23715_none_8e5be6aae0f183e6    
(f)    CSI Manifest Failed Catalog Check    0x00000000    winsxs\Manifests\amd64_ec259f7595ac2c32d845238e7d55378e_31bf3856ad364e35_11.2.9600.18349_none_d93fda2261d2fefe.manifest    amd64_ec259f7595ac2c32d845238e7d55378e_31bf3856ad364e35_11.2.9600.18349_none_d93fda2261d2fefe    
(f)    CSI Manifest Failed Catalog Check    0x00000000    winsxs\Manifests\wow64_microsoft-windows-lsa_31bf3856ad364e35_6.1.7601.23864_none_0f189deec111dd81.manifest    wow64_microsoft-windows-lsa_31bf3856ad364e35_6.1.7601.23864_none_0f189deec111dd81    
(f)    CSI Manifest Failed Catalog Check    0x00000000    winsxs\Manifests\amd64_microsoft-windows-t..s-clientactivexcore_31bf3856ad364e35_7.2.7601.23137_none_482a1d791f2527de.manifest    amd64_microsoft-windows-t..s-clientactivexcore_31bf3856ad364e35_7.2.7601.23137_none_482a1d791f2527de    

Summary:
Seconds executed: 1443
 Found 44 errors
  CSI Manifest All Zeros Total count: 1
  CSI Manifest Failed Catalog Check Total count: 27
  CBS MUM Corrupt Total count: 1
  CBS Catalog Corrupt Total count: 1
  CBS Registry Error Total count: 8
  CBS Watchlist Component Missing Total count: 6

Unavailable repair files:
    winsxs\manifests\x86_microsoft-windows-cryptbase_31bf3856ad364e35_6.1.7601.23796_none_67a231b92598f2a9.manifest
    winsxs\manifests\amd64_microsoft-windows-i..rolviewer.resources_31bf3856ad364e35_11.2.9600.18738_cs-cz_415574e8eac936fc.manifest
    winsxs\manifests\x86_microsoft-windows-i..timezones.resources_31bf3856ad364e35_6.1.7601.23452_cs-cz_42829bc5124e5821.manifest
    winsxs\manifests\x86_microsoft-windows-cryptbase_31bf3856ad364e35_6.1.7601.23642_none_67d43e4725740471.manifest
    winsxs\manifests\amd64_78fb46c8e56bf0f43ffb5d3ba0fd14f7_31bf3856ad364e35_6.1.7601.23739_none_2cd8a08941041850.manifest
    winsxs\manifests\x86_wpf-windowsbase_31bf3856ad364e35_6.1.7601.23744_none_59dd782cbf3e5c90.manifest
    winsxs\manifests\amd64_3512821798256a2184eb49f1af00ffba_31bf3856ad364e35_11.2.9600.18349_none_11ac7de8b6cbe353.manifest
    winsxs\manifests\wow64_microsoft-windows-wow64_31bf3856ad364e35_6.1.7601.23040_none_d1056ab63b89509e.manifest
    winsxs\manifests\wow64_microsoft-windows-security-digest_31bf3856ad364e35_6.1.7601.23040_none_a3acedc3e0ef329e.manifest
    winsxs\manifests\amd64_microsoft-windows-ie-lowreg_31bf3856ad364e35_11.2.9600.17239_none_8ab9d04ff8de0c86.manifest
    winsxs\manifests\amd64_microsoft-windows-sechost_31bf3856ad364e35_6.1.7601.23040_none_e64dd537fccf9399.manifest
    winsxs\manifests\amd64_dcd2cfdae88cd53864cea441eb6f5970_31bf3856ad364e35_11.2.9600.18349_none_40017b3789d2ca48.manifest
    winsxs\manifests\amd64_microsoft-windows-c..tionauthorityclient_31bf3856ad364e35_6.1.7601.22923_none_3621766a6c6dc5e1.manifest
    winsxs\manifests\wow64_microsoft-windows-systemrestore-main_31bf3856ad364e35_6.1.7601.23040_none_afbf729417791cfe.manifest
    winsxs\manifests\wow64_microsoft-windows-i..rnational-timezones_31bf3856ad364e35_6.1.7601.23452_none_7e1e31626dd272f3.manifest
    winsxs\manifests\amd64_079d22e65563eba632b22cfb3e1199f5_31bf3856ad364e35_6.1.7601.23717_none_13888216793a3e2b.manifest
    winsxs\manifests\x86_microsoft-windows-i..tocolimplementation_31bf3856ad364e35_11.2.9600.18762_none_880588e7fe97ec0d.manifest
    winsxs\manifests\x86_microsoft-windows-c..tionauthorityclient_31bf3856ad364e35_6.1.7601.23418_none_da128bfeb403df4b.manifest
    winsxs\manifests\amd64_microsoft-windows-ie-versioninfo_31bf3856ad364e35_11.2.9600.18762_none_e16110174a1c6a2c.manifest
    winsxs\manifests\x86_microsoft-windows-rpc-http_31bf3856ad364e35_6.1.7601.23154_none_a25e7ce8b6d453c6.manifest
    winsxs\manifests\wow64_microsoft-windows-security-ntlm_31bf3856ad364e35_6.1.7601.23154_none_e58bc2a1c6c96061.manifest
    winsxs\manifests\wow64_microsoft-windows-wow64_31bf3856ad364e35_6.1.7601.18839_none_d08fc84f225b45b0.manifest
    winsxs\manifests\wow64_microsoft-windows-winsrv_31bf3856ad364e35_6.1.7601.18839_none_1ee896e7e7614992.manifest
    winsxs\manifests\amd64_e8479767d28f487c65027556b0d110be_31bf3856ad364e35_6.1.7601.23713_none_bb37f0d493d8e9ea.manifest
    winsxs\manifests\amd64_a4c66b93bb605ede299d2eed2d814ed7_31bf3856ad364e35_6.1.7601.23715_none_8e5be6aae0f183e6.manifest
    winsxs\manifests\amd64_ec259f7595ac2c32d845238e7d55378e_31bf3856ad364e35_11.2.9600.18349_none_d93fda2261d2fefe.manifest
    winsxs\manifests\wow64_microsoft-windows-lsa_31bf3856ad364e35_6.1.7601.23864_none_0f189deec111dd81.manifest
    winsxs\manifests\amd64_microsoft-windows-t..s-clientactivexcore_31bf3856ad364e35_7.2.7601.23137_none_482a1d791f2527de.manifest
    servicing\packages\Package_for_KB3142024~31bf3856ad364e35~amd64~~6.1.1.1.mum
    servicing\packages\Package_for_KB3161561~31bf3856ad364e35~amd64~~6.1.1.1.mum
    servicing\packages\Package_for_KB3142024~31bf3856ad364e35~amd64~~6.1.1.1.cat
    servicing\packages\Package_for_KB3161561~31bf3856ad364e35~amd64~~6.1.1.1.cat

I reduced it from 139 to 44 by myself through downloading KBs from Microsoft web and updating the files on HDD but still I have the problems in registry, especially with the 4 Packages and with manifests from winsxs directory. For me it seems to be a big problem find the Package_for_KB3142024 and Package_for_KB3161561 before SP1. In the KBs right now are only Packages for SP1. Where to download these packages from?

So can you please help me to fix the last errors? But as I mentioned it in the Subject I have the Czech version and I think that it can complicate the situation:huh:

big thx
 
Hi,

so I've reduced by myself some another errors
  • Checking Windows Servicing Packages
  • Checking Package Manifests and Catalogs
  • Checking Package Watchlist
  • Checking Component Watchlist
  • Checking Packages

and only I've found that still persist errors with
  • Checking Component Store

Code: 
=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2018-03-12 09:20

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store
(f)    CSI Manifest Failed Catalog Check    0x00000000    winsxs\Manifests\x86_microsoft-windows-i..timezones.resources_31bf3856ad364e35_6.1.7601.23452_cs-cz_42829bc5124e5821.manifest    x86_microsoft-windows-i..timezones.resources_31bf3856ad364e35_6.1.7601.23452_cs-cz_42829bc5124e5821    
(f)    CSI Manifest Failed Catalog Check    0x00000000    winsxs\Manifests\amd64_3512821798256a2184eb49f1af00ffba_31bf3856ad364e35_11.2.9600.18349_none_11ac7de8b6cbe353.manifest    amd64_3512821798256a2184eb49f1af00ffba_31bf3856ad364e35_11.2.9600.18349_none_11ac7de8b6cbe353    
(f)    CSI Manifest Failed Catalog Check    0x00000000    winsxs\Manifests\wow64_microsoft-windows-wow64_31bf3856ad364e35_6.1.7601.23040_none_d1056ab63b89509e.manifest    wow64_microsoft-windows-wow64_31bf3856ad364e35_6.1.7601.23040_none_d1056ab63b89509e    
(f)    CSI Manifest Failed Catalog Check    0x00000000    winsxs\Manifests\wow64_microsoft-windows-security-digest_31bf3856ad364e35_6.1.7601.23040_none_a3acedc3e0ef329e.manifest    wow64_microsoft-windows-security-digest_31bf3856ad364e35_6.1.7601.23040_none_a3acedc3e0ef329e    
(f)    CSI Manifest Failed Catalog Check    0x00000000    winsxs\Manifests\amd64_microsoft-windows-ie-lowreg_31bf3856ad364e35_11.2.9600.17239_none_8ab9d04ff8de0c86.manifest    amd64_microsoft-windows-ie-lowreg_31bf3856ad364e35_11.2.9600.17239_none_8ab9d04ff8de0c86    
(f)    CSI Manifest All Zeros    0x00000000    winsxs\Manifests\amd64_microsoft-windows-sechost_31bf3856ad364e35_6.1.7601.23040_none_e64dd537fccf9399.manifest    amd64_microsoft-windows-sechost_31bf3856ad364e35_6.1.7601.23040_none_e64dd537fccf9399    
(f)    CSI Manifest Failed Catalog Check    0x00000000    winsxs\Manifests\amd64_dcd2cfdae88cd53864cea441eb6f5970_31bf3856ad364e35_11.2.9600.18349_none_40017b3789d2ca48.manifest    amd64_dcd2cfdae88cd53864cea441eb6f5970_31bf3856ad364e35_11.2.9600.18349_none_40017b3789d2ca48    
(f)    CSI Manifest Failed Catalog Check    0x00000000    winsxs\Manifests\wow64_microsoft-windows-systemrestore-main_31bf3856ad364e35_6.1.7601.23040_none_afbf729417791cfe.manifest    wow64_microsoft-windows-systemrestore-main_31bf3856ad364e35_6.1.7601.23040_none_afbf729417791cfe    
(f)    CSI Manifest Failed Catalog Check    0x00000000    winsxs\Manifests\wow64_microsoft-windows-i..rnational-timezones_31bf3856ad364e35_6.1.7601.23452_none_7e1e31626dd272f3.manifest    wow64_microsoft-windows-i..rnational-timezones_31bf3856ad364e35_6.1.7601.23452_none_7e1e31626dd272f3    
(f)    CSI Manifest Failed Catalog Check    0x00000000    winsxs\Manifests\x86_microsoft-windows-c..tionauthorityclient_31bf3856ad364e35_6.1.7601.23418_none_da128bfeb403df4b.manifest    x86_microsoft-windows-c..tionauthorityclient_31bf3856ad364e35_6.1.7601.23418_none_da128bfeb403df4b    
(f)    CSI Manifest Failed Catalog Check    0x00000000    winsxs\Manifests\x86_microsoft-windows-rpc-http_31bf3856ad364e35_6.1.7601.23154_none_a25e7ce8b6d453c6.manifest    x86_microsoft-windows-rpc-http_31bf3856ad364e35_6.1.7601.23154_none_a25e7ce8b6d453c6    
(f)    CSI Manifest Failed Catalog Check    0x00000000    winsxs\Manifests\wow64_microsoft-windows-security-ntlm_31bf3856ad364e35_6.1.7601.23154_none_e58bc2a1c6c96061.manifest    wow64_microsoft-windows-security-ntlm_31bf3856ad364e35_6.1.7601.23154_none_e58bc2a1c6c96061    
(f)    CSI Manifest Failed Catalog Check    0x00000000    winsxs\Manifests\wow64_microsoft-windows-wow64_31bf3856ad364e35_6.1.7601.18839_none_d08fc84f225b45b0.manifest    wow64_microsoft-windows-wow64_31bf3856ad364e35_6.1.7601.18839_none_d08fc84f225b45b0    
(f)    CSI Manifest Failed Catalog Check    0x00000000    winsxs\Manifests\wow64_microsoft-windows-winsrv_31bf3856ad364e35_6.1.7601.18839_none_1ee896e7e7614992.manifest    wow64_microsoft-windows-winsrv_31bf3856ad364e35_6.1.7601.18839_none_1ee896e7e7614992    
(f)    CSI Manifest Failed Catalog Check    0x00000000    winsxs\Manifests\amd64_ec259f7595ac2c32d845238e7d55378e_31bf3856ad364e35_11.2.9600.18349_none_d93fda2261d2fefe.manifest    amd64_ec259f7595ac2c32d845238e7d55378e_31bf3856ad364e35_11.2.9600.18349_none_d93fda2261d2fefe    
(f)    CSI Manifest Failed Catalog Check    0x00000000    winsxs\Manifests\amd64_microsoft-windows-t..s-clientactivexcore_31bf3856ad364e35_7.2.7601.23137_none_482a1d791f2527de.manifest    amd64_microsoft-windows-t..s-clientactivexcore_31bf3856ad364e35_7.2.7601.23137_none_482a1d791f2527de    

Summary:
Seconds executed: 560
 Found 16 errors
  CSI Manifest All Zeros Total count: 1
  CSI Manifest Failed Catalog Check Total count: 15

Unavailable repair files:
    winsxs\manifests\x86_microsoft-windows-i..timezones.resources_31bf3856ad364e35_6.1.7601.23452_cs-cz_42829bc5124e5821.manifest
    winsxs\manifests\amd64_3512821798256a2184eb49f1af00ffba_31bf3856ad364e35_11.2.9600.18349_none_11ac7de8b6cbe353.manifest
    winsxs\manifests\wow64_microsoft-windows-wow64_31bf3856ad364e35_6.1.7601.23040_none_d1056ab63b89509e.manifest
    winsxs\manifests\wow64_microsoft-windows-security-digest_31bf3856ad364e35_6.1.7601.23040_none_a3acedc3e0ef329e.manifest
    winsxs\manifests\amd64_microsoft-windows-ie-lowreg_31bf3856ad364e35_11.2.9600.17239_none_8ab9d04ff8de0c86.manifest
    winsxs\manifests\amd64_microsoft-windows-sechost_31bf3856ad364e35_6.1.7601.23040_none_e64dd537fccf9399.manifest
    winsxs\manifests\amd64_dcd2cfdae88cd53864cea441eb6f5970_31bf3856ad364e35_11.2.9600.18349_none_40017b3789d2ca48.manifest
    winsxs\manifests\wow64_microsoft-windows-systemrestore-main_31bf3856ad364e35_6.1.7601.23040_none_afbf729417791cfe.manifest
    winsxs\manifests\wow64_microsoft-windows-i..rnational-timezones_31bf3856ad364e35_6.1.7601.23452_none_7e1e31626dd272f3.manifest
    winsxs\manifests\x86_microsoft-windows-c..tionauthorityclient_31bf3856ad364e35_6.1.7601.23418_none_da128bfeb403df4b.manifest
    winsxs\manifests\x86_microsoft-windows-rpc-http_31bf3856ad364e35_6.1.7601.23154_none_a25e7ce8b6d453c6.manifest
    winsxs\manifests\wow64_microsoft-windows-security-ntlm_31bf3856ad364e35_6.1.7601.23154_none_e58bc2a1c6c96061.manifest
    winsxs\manifests\wow64_microsoft-windows-wow64_31bf3856ad364e35_6.1.7601.18839_none_d08fc84f225b45b0.manifest
    winsxs\manifests\wow64_microsoft-windows-winsrv_31bf3856ad364e35_6.1.7601.18839_none_1ee896e7e7614992.manifest
    winsxs\manifests\amd64_ec259f7595ac2c32d845238e7d55378e_31bf3856ad364e35_11.2.9600.18349_none_d93fda2261d2fefe.manifest
    winsxs\manifests\amd64_microsoft-windows-t..s-clientactivexcore_31bf3856ad364e35_7.2.7601.23137_none_482a1d791f2527de.manifest

and using sfc /scannow I've found some corrupt files
CORRUPT: C:\Windows\winsxs\amd64_microsoft-windows-p..ooler-networkclient_31bf3856ad364e35_6.1.7601.23889_none_97dc052da0db9dd7\win32spl.dll
CORRUPT: C:\Windows\winsxs\wow64_microsoft-windows-w..mediadeliveryengine_31bf3856ad364e35_6.1.7601.19091_none_8591194da8d7f843\wmpmde.dll

but now I think due to the all registry fixes I'm able to update my Win7 x64 Pro from Microsoft Update with all critical updates :smile9: (even if the the update KB4075211 from February 22 2018 destroy something on my HDD and windows don't boot up, but this is only recommended update so I don't install it)

but still I need to fix this 18 errors ...

So can you please help me? I don't know how to find where are these files in the KB's packages??? Is some procedure how to find it? Or is there some list?
 
So another small update because I still have company notebook from my last cutomer at home. I've checked the Windows directory there and I've fixed
  • 2 CORRUPT files win32spl.dll and wmpmde.dll
  • another 13 manifest files
Code: 
=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2018-03-13 11:21

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store
(f)    CSI Manifest Failed Catalog Check    0x00000000    winsxs\Manifests\x86_microsoft-windows-i..timezones.resources_31bf3856ad364e35_6.1.7601.23452_cs-cz_42829bc5124e5821.manifest    x86_microsoft-windows-i..timezones.resources_31bf3856ad364e35_6.1.7601.23452_cs-cz_42829bc5124e5821    
(f)    CSI Manifest Failed Catalog Check    0x00000000    winsxs\Manifests\amd64_microsoft-windows-ie-lowreg_31bf3856ad364e35_11.2.9600.17239_none_8ab9d04ff8de0c86.manifest    amd64_microsoft-windows-ie-lowreg_31bf3856ad364e35_11.2.9600.17239_none_8ab9d04ff8de0c86    
(f)    CSI Manifest Failed Catalog Check    0x00000000    winsxs\Manifests\wow64_microsoft-windows-i..rnational-timezones_31bf3856ad364e35_6.1.7601.23452_none_7e1e31626dd272f3.manifest    wow64_microsoft-windows-i..rnational-timezones_31bf3856ad364e35_6.1.7601.23452_none_7e1e31626dd272f3    

Summary:
Seconds executed: 1075
 Found 3 errors
  CSI Manifest Failed Catalog Check Total count: 3

Unavailable repair files:
    winsxs\manifests\x86_microsoft-windows-i..timezones.resources_31bf3856ad364e35_6.1.7601.23452_cs-cz_42829bc5124e5821.manifest
    winsxs\manifests\amd64_microsoft-windows-ie-lowreg_31bf3856ad364e35_11.2.9600.17239_none_8ab9d04ff8de0c86.manifest
    winsxs\manifests\wow64_microsoft-windows-i..rnational-timezones_31bf3856ad364e35_6.1.7601.23452_none_7e1e31626dd272f3.manifest

So right now there are only 3 manifests files left :-)

But I think that there is still problem with the update KB4075211 that leads to incosistency in Volume of Drive and goes to NO BOOT :-(

Can you somebody analyze this stuff for me? And can help me with fix the last errors in manifests file?

THX
 
Hi,

of course. The assistance will be fine. All of the changes I've made on the 1:1 copy of the old SDD to the new SDD (500GB to 1TB). But still I have some questions


  • from the last log you can see 3 corrupted manifests files. I want to know where to find them? Is there some possibilities to recognize the KBxxxx update files that can I download directly from Micro$oft?
Code: 
Unavailable repair files:
    winsxs\manifests\x86_microsoft-windows-i..timezones.resources_31bf3856ad364e35_6.1.7601.23452_cs-cz_42829bc5124e5821.manifest
    winsxs\manifests\amd64_microsoft-windows-ie-lowreg_31bf3856ad364e35_11.2.9600.17239_none_8ab9d04ff8de0c86.manifest
    winsxs\manifests\wow64_microsoft-windows-i..rnational-timezones_31bf3856ad364e35_6.1.7601.23452_none_7e1e31626dd272f3.manifest


  • in my first post are registry errors I've tried to fix them by myself manually but I'm not sure if it's OK even if they dissappeard in the other logs. It seems to be OK. Bellow is my repair script

View attachment SFCFix.txt

Everything leads that Windows Update is again OK. I've installed many of the Recommended and Critical updates but with one update I had the problems
February 22, 2018—KB4075211 (Preview of Monthly Rollup)
this leads to no boot problems (error 0xc000000e and 0xc0000135) :huh: Fine is that it's not criticall update.

So I don't know if this errors is due to the problems with manifests, packages and registry fix? And is there some chance to fix even this?

THX
 
I don't recommend installing Previews. They are basically beta's of the actual update. They can cause more problems than it is worth. Try the following KBs for what you are looking for.
kb3162835
kb2976627
 
Hi,

Thanks

KB3162835 is fine. I've download it and solve the problems with 2 files
Code: 
=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2018-03-16 14:32

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store
(f)    CSI Manifest Failed Catalog Check    0x00000000    winsxs\Manifests\amd64_microsoft-windows-ie-lowreg_31bf3856ad364e35_11.2.9600.17239_none_8ab9d04ff8de0c86.manifest    amd64_microsoft-windows-ie-lowreg_31bf3856ad364e35_11.2.9600.17239_none_8ab9d04ff8de0c86    

Summary:
Seconds executed: 1201
 Found 1 errors
  CSI Manifest Failed Catalog Check Total count: 1

Unavailable repair files:
    winsxs\manifests\amd64_microsoft-windows-ie-lowreg_31bf3856ad364e35_11.2.9600.17239_none_8ab9d04ff8de0c86.manifest

But I'm not able to download KB2976627 and I suppose that there is the last final manifest file amd64_microsoft-windows-ie-lowreg_31bf3856ad364e35_11.2.9600.17239_none_8ab9d04ff8de0c86.manifest

hmmm so where to find this KB... file and how do you recognize what KB... is for what manifest file? :-)
 
It's not really something I can explain in a post. We have an acadamy here were we train interested students on the entire Windows/Update servicing process.

Is there anything else I can assist with?
 
Thanks

the log seems to be fine right now

Code: 
=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2018-03-16 15:22

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store

Summary:
Seconds executed: 1346
 No errors detected

maybe I have 2 off topic questions

clean2.png



  • is Win10 better due effective maintenance of this update files? And due to this directory WINSXS contain much much less files then in Win7 system?

On my Win7Pro x64 is WINSXS directory about cca 23,5 GB .... :huh:
 
is it possible to delete unwanted files like on the picture bellow? I've found this Disk Cleanup Wizard addon lets users delete outdated Windows updates on Windows 7 SP1 or Windows Server 2008 R2 SP1 ? Is it good to use it and delete unwanted update files on Win7 Pro?
Click to expand...

Yes that is completely safe to do.
is Win10 better due effective maintenance of this update files? And due to this directory WINSXS contain much much less files then in Win7 system?
Click to expand...
Yes it is much better on Windows 10 because of compression. It would be about 1/3 of what you have on Windows 7.
 
You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top