SFC found corrupt Avast files

[REDACTED]

I have Avast Premier. SFC /scannow found these corrupt files and I think they belong to Avast. What can I do?

Found:{l:32 b:b77d27df43c464ca24067666962175bd050201195a9a3e9f4021c89abb2c29c0}.
2016-06-23 07:40:07, Info                  CSI    0000000f Looking for manifest in Backup Dir...
2016-06-23 07:40:07, Error                 CSI    00000010 (F) Unable to load manifest for component [l:73 ml:140]"amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.23918.0_none_53c8344321b452ba"[gle=0x80004005]
2016-06-23 07:40:07, Error                 CSI    00000011@2016/6/23:11:40:07.657 (F) base\wcp\componentstore\storelayout.cpp(2671): Store corruption detected in function ComponentStore::CRawStoreLayout::FetchManifestContent expression: 0
  FileHashMismatch on resource [100]"\winsxs\manifests\amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.23918.0_none_53c8344321b452ba.manifest"[gle=0x80004005]

[merckxist]

I use Avast Free, but I assume Premier has a repair option, so try repairing the installation. Open Control Panel > Programs > highlight Avast > click Change, select Repair option from menu. After repair, see if SFC produces the same error.

[Eddy]

All avast versions have the repair option.

It looks to me sfc just can't handle the files.
If everything is working without a problem, I would not worry about it and just ignore the messages.

[REDACTED]

I already tried the repair option but it did not fix the scannow error. Maybe you're right -the SFC can't really make sense of the hash.??

[merckxist]

Not knowing how critical that file is for avast, it might not be an issue to your configuration. But. . . I have those same files on win7 and win10 in C:\windows\winsxs and got no error running sfc. The error seems to indicate sfc can't find the manifest file it wants (maybe to correct the problem?) Perhaps one of the Evangelist experts can shed some more light. You would think that a repair would replace them if they were significant or deemed corrupt by avast. Maybe a clean install could make sfc happy.

edit: have you looked at similar issue https://forum.avast.com/index.php?topic=186903.0

[DavidR]

@    denautn
What was the reason for running the SFC /scannow ?

If it wasn't for a specific problem and avast is running as it should, then as Eddy said you shouldn't have anything to worry about.

[REDACTED]

Yes everything is working fine.But last week the SFC reported no problems. I guess I'm a perfectionist.However an expert should be able to decipher a CBS log and tell me the solution.But you're right that nothings perfect and I should be content.

[Eddy]

Why looking for a solution if there is no problem ?
That doesn't make sense.

[drake127]

There is another topic for this issue: https://forum.avast.com/index.php?topic=186903.0