CheckSur log corrupt manifest

Page 1 of 3 123 LastLast

  1. Posts : 33
    Windows 7 X64
       #1

    CheckSur log corrupt manifest


    Hi

    I have a corrupt manifest. I see that people come here with the same problem and a helpful poster gives out the needed files to fix it.


    Summary:
    Seconds executed: 2355
    Found 901 errors
    CSI Manifest Failed Catalog Check Total count: 5
    CSI Missing Deployment Key Total count: 15
    CSI Missing Identity Total count: 6
    CSI Mismatched Identity Total count: 2
    CSI C Mark Deployment Not Marked Total count: 862
    CSI C Mark Deployment Missing Total count: 9
    CBS MUM Corrupt Total count: 1
    CSI Missing Winning Component Key Total count: 1

    Unavailable repair files:
    winsxs\manifests\amd64_microsoft-windows-msauditevtlog_31bf3856ad364e35_6.1.7601.23040_none_25cd72a8a846d196.manifest
    winsxs\manifests\wow64_microsoft-windows-ie-htmlrendering_31bf3856ad364e35_11.2.9600.17633_none_ffdaa43c6ba73cf8.manifest
    winsxs\manifests\wow64_microsoft-windows-ie-internetexplorer_31bf3856ad364e35_11.2.9600.17420_none_1c0e758f636ca489.manifest
    winsxs\manifests\x86_netfx-sbscmp10_dll_31bf3856ad364e35_6.1.7601.18514_none_770d53c5633e1fe1.manifest
    winsxs\manifests\amd64_netfx-sbscmp10_dll_31bf3856ad364e35_6.1.7601.22724_none_d3aabe0e34c149f9.manifest
    servicing\packages\Package_for_KB3004394_SP1~31bf3856ad364e35~amd64~~6.1.2.0.mum
    servicing\packages\Package_for_KB3004394_SP1~31bf3856ad364e35~amd64~~6.1.2.0.cat
    CheckSur log corrupt manifest Attached Files
      My Computer


  2. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #2

    With that bunch of errors there is not going to be any sensible way to repair things short of a repair install.
    I suggest that you back up your data to external storage, and do the repair...
    Repair Install
      My Computer


  3. Posts : 33
    Windows 7 X64
    Thread Starter
       #3

    Wow. Given that you are the boss of checksur repair,!that is devastating news.
      My Computer


  4. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #4

    The big problem is this ...
    CSI C Mark Deployment Not Marked Total count: 862
      My Computer


  5. Posts : 33
    Windows 7 X64
    Thread Starter
       #5

    Hi

    I managed to fix the manifest following this guide.
    Need to manually fix problems in checksur
    But get error codes 80070246 and 80070308 while doing updates
    I'm attaching the new checksur
    CheckSur log corrupt manifest Attached Files
      My Computer


  6. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #6

    Those I can try and fix -

    Code:
    (f)	CSI Missing Identity	0x00000000	appid	1cec18ef69c..af568b18952_31bf3856ad364e35_8.0.7600.20861_f6ca0f8e95ece5ae	
    (f)	CSI Missing Identity	0x00000000	appid	79a8da50923..72460ba3cfb_31bf3856ad364e35_6.1.7600.20740_071f1beb767921ef	
    (f)	CSI Mismatched Identity	0x00000000	appid	2fd8d5bf1e7..2390dc6fe4f_31bf3856ad364e35_6.1.7601.22012_148a42887bc79a12	appid and keyform do not match; appid is wrong.
    (f)	CSI Missing Identity	0x00000000	appid	8abd15d21a9..e4560b10e08_31bf3856ad364e35_6.1.7601.22530_2e103e3e0c1fa6b5	
    (f)	CSI Mismatched Identity	0x00000000	appid	119ec807287..855b0c9bbf3_6595b64144ccf1df_6.0.7601.23039_dd84a4767f17ea34	appid and keyform do not match; appid is wrong.
    (f)	CSI Missing Identity	0x00000000	appid	d80d1f4b9f8..6325edf114b_31bf3856ad364e35_6.1.7601.22530_f5437a0bb919147a	
    (f)	CSI Missing Identity	0x00000000	appid	d6fd5b7e6d1..dca159acfd0_31bf3856ad364e35_6.1.7601.21861_2c1abf7889730a43	
    (f)	CSI Missing Identity	0x00000000	appid	2c2c046d9c6..bed51b7d6a4_31bf3856ad364e35_6.1.7601.22530_a2a6c009fa0db073	
    (f)	CSI Missing Deployment Key	0x00000000	9acf6cc54e3..ea4cc168145_31bf3856ad364e35_11.2.9600.17843_41417932c032ada9	HKLM\Components\CanonicalData\Deployments	
    (f)	CSI Missing Deployment Key	0x00000000	41ed3b74800..5e0a215fd08_31bf3856ad364e35_8.0.7600.16766_bebb2178f1a778e0	HKLM\Components\CanonicalData\Deployments	
    (f)	CSI Missing Deployment Key	0x00000000	c6b6edbf458..fcdbf8dae34_b03f5f7f11d50a3a_6.1.7601.18523_077ede4fc527ff09	HKLM\Components\CanonicalData\Deployments	
    (f)	CSI Missing Deployment Key	0x00000000	f41713b60dd..49589459bcd_b03f5f7f11d50a3a_6.1.7601.18523_cfcb6af0676c62f7	HKLM\Components\CanonicalData\Deployments	
    (f)	CSI Missing Deployment Key	0x00000000	policy.8.0...ft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.4053_4ddfc6cd11929a02	HKLM\Components\CanonicalData\Deployments	
    (f)	CSI Missing Deployment Key	0x00000000	723dcb1eacb..1c8391aaf31_31bf3856ad364e35_6.1.7601.17857_6377f3323823d5d4	HKLM\Components\CanonicalData\Deployments	
    (f)	CSI Missing Deployment Key	0x00000000	104fe3480a5..04cd456f311_b03f5f7f11d50a3a_6.1.7601.22733_708f226f3504dc39	HKLM\Components\CanonicalData\Deployments	
    (f)	CSI Missing Deployment Key	0x00000000	cd366cd055d..b2ae2d6c64b_b77a5c561934e089_6.1.7601.22110_97c6da735c0e7d5d	HKLM\Components\CanonicalData\Deployments	
    (f)	CSI Missing Deployment Key	0x00000000	b59c32f608f..4303f51d707_b77a5c561934e089_6.1.7601.17952_670c2ced0ddcf5b0	HKLM\Components\CanonicalData\Deployments	
    (f)	CSI Missing Deployment Key	0x00000000	89bc3a3186d..38a9947b066_31bf3856ad364e35_8.0.7600.16766_bc77a1c38977ecdf	HKLM\Components\CanonicalData\Deployments	
    (f)	CSI Missing Deployment Key	0x00000000	60cf7d85c39..5e7b75133c2_6595b64144ccf1df_6.0.7601.23039_2ca8b50ca275e600	HKLM\Components\CanonicalData\Deployments	
    (f)	CSI Missing Deployment Key	0x00000000	9eee84c6ac3..2538ead2473_31bf3856ad364e35_8.0.7600.20908_b8b8766185731dd4	HKLM\Components\CanonicalData\Deployments	
    (f)	CSI Missing Deployment Key	0x00000000	b612f4a3cb1..b2add3491f5_b77a5c561934e089_6.1.7601.17952_8f3dd633b9b86f0e	HKLM\Components\CanonicalData\Deployments	
    (f)	CSI Missing Deployment Key	0x00000000	202c00b5cd2..e8f8d3d7582_31bf3856ad364e35_6.1.7600.16444_b4028544b0890ec2	HKLM\Components\CanonicalData\Deployments	
    (f)	CSI Missing Deployment Key	0x00000000	1769f48b5ed..f36c5fd5230_b03f5f7f11d50a3a_6.1.7601.22733_aba759d0a226d804	HKLM\Components\CanonicalData\Deployments	
    (f)	CSI C Mark Deployment Missing	0x00000000	c!windowsfoundation_31bf3856ad364e35_6.1.7601.17514_615fdfe2a739	amd64_microsoft-windows-component-opcom_31bf3856ad364e35_6.1.7601.17514_none_015d0742c9308ce9	
    (f)	CSI C Mark Deployment Missing	0x00000000	c!50851c14f4b..9208f5b57ac_31bf3856ad364e35_6.1.7600.20910_5f3fb1e9d67e75ae	amd64_microsoft-windows-explorer_31bf3856ad364e35_6.1.7600.20910_none_ae79ed04ac56c4a9	
    (f)	CSI C Mark Deployment Missing	0x00000000	c!390a3fce470..a08b86c8bc1_31bf3856ad364e35_6.1.7600.16768_d4674e8383922077	amd64_microsoft-windows-explorer_31bf3856ad364e35_6.1.7600.16768_none_adc24107935a7e25	
    (f)	CSI Missing Winning Component Key	0x00000000	x86_policy.9.0.microsoft.vc90.openmp_1fc8b3b9a1e18e3b_9.0.30729.5570_none_0e94c157b72a923c		
    (f)	CSI C Mark Deployment Missing	0x00000000	c!50851c14f4b..9208f5b57ac_31bf3856ad364e35_6.1.7600.20910_5f3fb1e9d67e75ae	wow64_microsoft-windows-explorer_31bf3856ad364e35_6.1.7600.20910_none_b8ce9756e0b786a4	
    (f)	CSI Missing Winning Component Key	0x00000000	amd64_netfx-mscorwks_dll_b03f5f7f11d50a3a_6.1.7601.17587_none_bf133713d70404bb		
    (f)	CSI C Mark Deployment Missing	0x00000000	c!ae677085b95..1a49ee8c5a5_31bf3856ad364e35_6.1.7601.17567_0594635cf349c2fc	amd64_microsoft-windows-explorer_31bf3856ad364e35_6.1.7601.17567_none_afa79dc39081d0ba	
    (f)	CSI C Mark Deployment Missing	0x00000000	c!390a3fce470..a08b86c8bc1_31bf3856ad364e35_6.1.7600.16768_d4674e8383922077	wow64_microsoft-windows-explorer_31bf3856ad364e35_6.1.7600.16768_none_b816eb59c7bb4020	
    (f)	CSI C Mark Deployment Missing	0x00000000	c!microsoft-w..anguagepack_31bf3856ad364	amd64_networking-mpssvc-svc.resources_31bf3856ad364e35_6.1.7601.17514_en-us_e58eb9a1a517b5e1	
    (f)	CSI C Mark Deployment Missing	0x00000000	c!2d779ff79c5..a8323e2f1c4_31bf3856ad364	amd64_microsoft-windows-s..or-native-serverbox_31bf3856ad364e35_6.1.7601.18332_none_cdcd09fd7ac37e52	
    (f)	CSI C Mark Deployment Missing	0x00000000	c!ae677085b95..1a49ee8c5a5_31bf3856ad364e35_6.1.7601.17567_0594635cf349c2fc	wow64_microsoft-windows-explorer_31bf3856ad364e35_6.1.7601.17567_none_b9fc4815c4e292b5
    I need to have a look at your COMPONENTS registry hive

    Please copy the C:\Windows\System32\config\COMPONENTS file (no extension) to your desktop and then compress it - upload the compressed file to your favoured fileshare site (preferably Dropbox or OneDrive) and post a link.
      My Computer


  7. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #7

    Hmmm - thinking about it, I don't really see how that fixed the number of errors that were present.
    Please post the CheckSUR.Persist.log file
      My Computer


  8. Posts : 33
    Windows 7 X64
    Thread Starter
       #8

    ok

    here you go, the checksur.persist is attached below and the components is on google drive
    https://drive.google.com/file/d/0B1l...ew?usp=sharing
    CheckSur log corrupt manifest Attached Files
      My Computer


  9. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #9

    The previous CheckSUR run did a lot of work!
    However, there is registry corruption present.

    I've managed to fix the problems I found (to my surprise) - but others will now appear to replace them Let's see how much work there really is to do...

    I've uploaded a file - ggnaa.zip - to my OneDrive at Noel's OneDrive
    Please download and save it to your desktop.
    Right-click on the file and select Extract All, and save to the default destination (which should be a folder on the desktop)

    Create a new System Restore point

    Open an Elevated Command Prompt, and run the following commands.

    Code:
    IF EXIST C:\Windows\System32\config\COMPONENTS.OLD1 DEL C:\Windows\System32\config\COMPONENTS.OLD1
    REN C:\Windows\System32\config\COMPONENTS COMPONENTS.OLD1
    COPY "%userprofile%\desktop\ggnaa\COMPONENTS" C:\Windows\System32\config
     
    .
    If you get an error with any command, STOP THERE - do not reboot! - post for instructions.

    Assuming all commands go OK, reboot, and run another CheckSUR scan - post the new CheckSUR.log file.
      My Computer


  10. Posts : 33
    Windows 7 X64
    Thread Starter
       #10

    ok.

    here is the new checksur.log
    CheckSur log corrupt manifest Attached Files
      My Computer


 
Page 1 of 3 123 LastLast

  Related Discussions
Our Sites
Site Links
About 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 14:04.
Find Us