Avast, Windows 10 pro 64-bit and System File Checker

[REDACTED]

Hi again,
we released emergency update #358 fixing VC110 runtime on build 2272 (and its business equivalent). It should be delivered to computers within 12 hours. Please, let me know if everything is ok.

Hi Drake,
I'm sorry to say I still have the same problem when running SFC on my Windows10 pc 64bit.

I have been following this thread with interest hoping the updates from Avast would have fixed it, but it hasn't.

Program version is now 12.2.2276  (build 12.2.3126.0)

Any suggestions would be very much appreciated,

[REDACTED]

Using latest version (12.3.2280) and still having the same issue with both my computers: win 10 home 32bits and win10 pro 64bits.
[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-08-19 20:10:56, Info                  CSI   
[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-08-19 20:10:56, Info                  CSI   

[bob3160]

Using latest version (12.3.2280) and still having the same issue with both my computers: win 10 home 32bits and win10 pro 64bits.
[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-08-19 20:10:56, Info                  CSI   
[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-08-19 20:10:56, Info                  CSI   

Repair Avast:
Control Panel> Program and Features (Add/remove program)>Select Avast> Select Repair. Reboot when completed
https://www.avast.com/faq.php?article=AVKB204
If Repair doesn't fix the problem, try the following:
Clean Install of Avast:
https://goo.gl/4Ptzkf

[drake127]

Hi, this specific issue will disappear when you upgrade your Windows 10 (e.g. to Anniversary Update). This is purely cosmetic issue and has no negative impact on your system. The component actually works just fine and is not used in current Avast version anyway. Unfortunately, repairing or uninstalling Avast does not help.

[REDACTED]

drake127. You have verified that no more SFC problems with Windows 10 Anniversary update installed right? I am ready to try Avast Free again and I just want to make double sure everything is OK. Thanks.

[REDACTED]

So problem clears up after Anniversary Update right?

[drake127]

Yes, but I must stress out that this was always cosmetic issue. It had no effect on functionality of Avast or Windows.

[REDACTED]

I understand drake 127. Thanks. I just didn't want anything like what I've read here to be present after installing Avast, or if I decide to uninstall for some reason. From what I read in this thread. I believe an uninstall did not make SFC problem go away. 

[mchain]

To reiterate, running sfc /scannow in safe mode shows no errors, so any errors reported in normal mode are just that, superficial.

[REDACTED]

Thanks for your input mchain. I understand errors are superficial. I'm just fussy when it comes to installing an AV and it causes something that takes time to fix, especially when it shouldn't. The people who have this problem must be like me from what I read here. I've had Norton from Comcast installed this year, and later I used AVG Pro, both with no problems or issues after uninstall. Windows Defender is going fine, but the urge to try Avast again started after hearing about the Nitro update. I, of course, waited for a bit like I always do with a new release, and I'm glad I did. I have the Anniversary update installed and all the new cumulative updates as well, so I'm hoping there are no SFC problems now like drake127 states, superficial or not.