Hello,
I deal with Windows Update and CBS(SFC Corruptions) on a daily basis over at Sysnative forums.
This issue that is occuring is due to the following registry keys in the COMPONENTS hive:
HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_avast.vc110.crt_2036b14a11e83e4a_11.0.60610.1_none_d58a6d64ab65b396.
HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_avast.vc110.crt_2036b14a11e83e4a_11.0.60610.1_none_1d37a43bbfe1dc9c.
There are two issues (from what I have seen) one is that SFC is saying the manifest is missing the other is saying it is damaged. The missing error appears to come from after uninstalling avast, the damaged is due to a mistmatch of the two hashes.
A little background first: When SFC runs to check the integrity of the WinSxS files and folders(The component store) it will first verify that the manifest is not corrupt or missing. The way that SFC will check to see if the manifest is corrupt is by looking at a value within the COMPONENTS hive that is associated with the WinSxS folder. If the hash does not match it will return that the manifest is damaged, if the registry key in the COMPONENTS hive exists but it cant find the key it will show as missing.
This is a deeper analysis on the manifest is damaged issue:
Lets take the two manifest files that are causing this issue, along with the current SHA256(Hex) values:
x86_avast.vc110.crt_2036b14a11e83e4a_11.0.60610.1_none_1d37a43bbfe1dc9c.manifest
--> SHA256 Hex: 63A7687EFFCA7BE2C7B057DFF48BF13919DE614957851D8D9270A2B017B09A75
2016-07-03 14:22:46, Info CSI 000058d2 Manifest hash for component [l:73 ml:140]"[B]amd64_avast.vc110.crt_2036b14a11e83e4a_11.0.60610.1_none_d58a6d64ab65b396[/B]" does not match expected value.
Expected:{l:32 b:[COLOR=blue]e29526d5e7a9622ae55d4b1fa9001d5ca922450833b0e71fe760ed78089c573a[/COLOR]}
Found:{l:32 b:[COLOR=red]7b77f2780d21c3a7cf3c6ae32d31a7c46c217eae321e897c22d5c4f29f34675d[/COLOR]}.
2016-07-03 14:22:46, Info CSI 000058d3 Unable to load manifest for component [l:73 ml:140]"amd64_avast.vc110.crt_2036b14a11e83e4a_11.0.60610.1_none_d58a6d64ab65b396"
2016-07-03 14:22:46, Info CSI 000058d4 [SR] Cannot verify component files for Avast.VC110.CRT, version 11.0.60610.1, arch amd64, versionScope neutral, pkt {l:8 b:2036b14a11e83e4a}, type [l:5]"win32", manifest is damaged (TRUE)
2016-07-03 14:22:46, Info CSI 000058d5 Manifest hash for component [l:71 ml:140]"
amd64_avast.vc110.crt_2036b14a11e83e4a_11.0.60610.1_none_d58a6d64ab65b396.manifest
--> SHA256 Hex: 7B77F2780D21C3A7CF3C6AE32D31A7C46C217EAE321E897C22D5C4F29F34675D
[B]x86_avast.vc110.crt_2036b14a11e83e4a_11.0.60610.1_none_1d37a43bbfe1dc9c[/B]" does not match expected value.
Expected:{l:[COLOR=blue]32 b:3aa52bd279cf7742e92b8cc464155b15bb4abe60d65463958aad243a2634f538[/COLOR]}
Found:{l:32 b:[COLOR=red]63a7687effca7be2c7b057dff48bf13919de614957851d8d9270a2b017b09a75[/COLOR]}.
2016-07-03 14:22:46, Info CSI 000058d6 Unable to load manifest for component [l:71 ml:140]"x86_avast.vc110.crt_2036b14a11e83e4a_11.0.60610.1_none_1d37a43bbfe1dc9c"
2016-07-03 14:22:46, Info CSI 000058d7 [SR] Cannot verify component files for Avast.VC110.CRT, version 11.0.60610.1, arch x86, versionScope neutral, pkt {l:8 b:2036b14a11e83e4a}, type [l:5]"win32", manifest is damaged (TRUE)
2016-07-03 14:22:46, Info CSI 000058d8 [SR] Repair complete
The part in red, is the hash it found on the manifest files.
The way that SFC verify the integrity of a manifest file is through the COMPONENTS registry hive
[HKEY_LOCAL_MACHINE\COMP\DerivedData\Components\amd64_avast.vc110.crt_2036b14a11e83e4a_11.0.60610.1_none_d58a6d64ab65b396]
"S256H"=hex:[COLOR=blue]e2,95,26,d5,e7,a9,62,2a,e5,5d,4b,1f,a9,00,1d,5c,a9,22,45,08,33,b0,e7,1f,e7,60,ed,78,08,9c,57,3a[/COLOR]
[HKEY_LOCAL_MACHINE\COMP\DerivedData\Components\x86_avast.vc110.crt_2036b14a11e83e4a_11.0.60610.1_none_1d37a43bbfe1dc9c]
"S256H"=hex:[COLOR=blue]3a,a5,2b,d2,79,cf,77,42,e9,2b,8c,c4,64,15,5b,15,bb,4a,be,60,d6,54,63,95,8a,ad,24,3a,26,34,f5,38[/COLOR]
The part in blue is what SFC was expecting for the manifest file, which matches the value in the registry.
If you change the hash inside the registry to the one on the actual file, the error will go away. What I would like from avast is confirmation that these manifest files are actually correct and the registry value is incorrect, or vis versa.
Deleting any registry keys found within the SOFTWARE hive will not stop the manifest is missing error, the way to fix this one is to remove the following COMPONENTS keys:
HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_avast.vc110.crt_2036b14a11e83e4a_11.0.60610.1_none_d58a6d64ab65b396.
HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_avast.vc110.crt_2036b14a11e83e4a_11.0.60610.1_none_1d37a43bbfe1dc9c.
Does the avast removal tool clean up the COMPONENTS hive?
I have successfully fix the manifest is damaged issue, but changing the hash in the components hive.
Let me know if you need any more information.