Avast WEBforum

Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: avant-guvnor on May 29, 2016, 07:54:03 PM

Title: Avast, Windows 10 pro 64-bit and System File Checker
Post by: avant-guvnor on May 29, 2016, 07:54:03 PM
I have uninstalled Avast free edition 2016.11.2.2262 from a Windows 10 Pro 64-bit PC using avastclear.exe v.11.2.2738.0.

I have run the System File Checker on this PC, which reports the following:
Windows Resource Protection found corrupt files but was unable to fix some
 of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
 example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not
 supported in offline servicing scenarios.

I have checked the CBS.log and see the following lines:
2016-05-29 18:27:52, Info                  CSI    00004d66 [SR] Repairing 2 components
2016-05-29 18:27:52, Info                  CSI    00004d67 [SR] Beginning Verify and Repair transaction
2016-05-29 18:27:52, Info                  CSI    00004d68 Manifest hash for component [l:73 ml:140]"amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.23918.0_none_53c8344321b452ba" does not match expected value.
 Expected:{l:32 b:714cddc73198abfd1a1a7dccbbca0808eda040d50b048b7e421d7afb8e2ac6b8}
 Found:{l:32 b:b77d27df43c464ca24067666962175bd050201195a9a3e9f4021c89abb2c29c0}.
2016-05-29 18:27:52, Info                  CSI    00004d69 Unable to load manifest for component [l:73 ml:140]"amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.23918.0_none_53c8344321b452ba"
2016-05-29 18:27:52, Info                  CSI    00004d6a [SR] Cannot verify component files for Avast.VC140.CRT, version 14.0.23918.0, arch amd64, versionScope neutral, pkt {l:8 b:fcc99ee6193ebbca}, type [l:5]"win32", manifest is damaged (TRUE)
2016-05-29 18:27:52, Info                  CSI    00004d6b Manifest hash for component [l:71 ml:140]"x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.23918.0_none_9b756b1a36307bc0" does not match expected value.
 Expected:{l:32 b:4379430502b6887d62d4283c0bfcb6aaf7b65e2d559321ca9b05a5c80c3f4357}
 Found:{l:32 b:d6b86bd6da85aef647b9c45e336c2ca37eda2e509c81bcf41b9bf06ca7c4f148}.
2016-05-29 18:27:52, Info                  CSI    00004d6c Unable to load manifest for component [l:71 ml:140]"x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.23918.0_none_9b756b1a36307bc0"
2016-05-29 18:27:52, Info                  CSI    00004d6d [SR] Cannot verify component files for Avast.VC140.CRT, version 14.0.23918.0, arch x86, versionScope neutral, pkt {l:8 b:fcc99ee6193ebbca}, type [l:5]"win32", manifest is damaged (TRUE)

These refer to Avast C runtime libraries.

Please advise on how I completely remove Avast (files and registry keys/values) from my system and so, eliminate the sfc corruption messages.

PLEASE NOTE: This is consistent for 2 other Windows 10 Pro 64-bit PCs I administer, both of which were running Avast free edition 2016.11.2.2262, but does NOT occur on a fourth Windows 8.1 Pro 64-bit PC, which was also running Avast free edition 2016.11.2.2262.
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: Eddy on May 29, 2016, 08:01:26 PM
Only way to remove avast completely is doing it manually.
Remove all folders, files and registry entries.
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: avant-guvnor on May 29, 2016, 10:28:20 PM
Only way to remove avast completely is doing it manually.
Remove all folders, files and registry entries.

I would like to remove the offending folders and files but as you are probably aware, even as an administrator I do not have permission to delete from the C:\Windows\WinSxS and C:\Windows\WinSxS\manifests folders as I am not Trusted Installer.

Any other ideas?
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: Eddy on May 29, 2016, 11:17:46 PM
You need to login to Windows as the real administrator, not as a user with admin rights.
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: bob3160 on May 29, 2016, 11:21:29 PM
This may help you:
http://www.ghacks.net/2014/11/12/how-to-enable-the-hidden-windows-10-administrator-account/
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: avant-guvnor on May 30, 2016, 01:08:07 AM
I enabled the built-in windows 10 administrator account, but I am still unable to delete Avast related folders from C:\Windows\WinSxS due to not being Trusted Installer.

This really is absurd, that an end-user should be required to manually remove troublesome Avast files from system folders in the first place.

Any other ideas?
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: esc on May 30, 2016, 03:03:13 AM
You have to take Ownership of these files first, then delete them. As you can see, the security works ....
See: http://www.askvg.com/guide-how-to-take-ownership-permission-of-a-file-or-folder-manually-in-windows/ (http://www.askvg.com/guide-how-to-take-ownership-permission-of-a-file-or-folder-manually-in-windows/)
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: avant-guvnor on May 30, 2016, 08:20:53 PM
So, I have finally taken ownership of the offending Avast files and deleted them. Avast support have suggested I follow the advice given in this thread.

However, I have run the System File Checker again, but sadly it reports the same:
Windows Resource Protection found corrupt files but was unable to fix some
 of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
 example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not
 supported in offline servicing scenarios.

The CBS.log still has references to Avast, which is causing the Windows Resource Protection corruption message. See the following lines from the CBS.log:
2016-05-30 14:44:50, Info                  CSI    00004eae [SR] Cannot verify component files for Avast.VC140.CRT, version 14.0.23918.0, arch amd64, versionScope neutral, pkt {l:8 b:fcc99ee6193ebbca}, type [l:5]"win32", manifest is damaged (FALSE)
2016-05-30 14:44:50, Info                  CSI    00004eaf [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 (FALSE)
2016-05-30 14:44:50, Info                  CSI    00004eb0 [SR] Cannot verify component files for Avast.VC140.CRT, version 14.0.23918.0, arch x86, versionScope neutral, pkt {l:8 b:fcc99ee6193ebbca}, type [l:5]"win32", manifest is damaged (FALSE)
2016-05-30 14:44:50, Info                  CSI    00004eb1 [SR] Cannot verify component files for Avast.VC140.MFC, version 14.0.23918.0, arch x86, versionScope neutral, pkt {l:8 b:fcc99ee6193ebbca}, type [l:5]"win32", manifest is damaged (FALSE)
2016-05-30 14:44:50, Info                  CSI    00004eb2 [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 (FALSE)
2016-05-30 14:44:50, Info                  CSI    00004eb3 [SR] Cannot verify component files for policy.11.0.Avast.VC110.CRT, version 11.0.60610.1, arch x86, versionScope neutral, pkt {l:8 b:2036b14a11e83e4a}, type [l:12]"win32-policy", manifest is damaged (FALSE)

I do not know how to fix this now. I have also asked Avast support, who have offered nothing in fixing this issue. This is just not acceptable.

Any other ideas would be much appreciated.
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: bob3160 on May 30, 2016, 08:47:15 PM
If you've contacted support, post the Support # here and we'll try to expedite it.
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: avant-guvnor on May 30, 2016, 09:11:01 PM
If you've contacted support, post the Support # here and we'll try to expedite it.

#346999

Thank you.
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: bob3160 on May 30, 2016, 10:02:58 PM
If you've contacted support, post the Support # here and we'll try to expedite it.

#346999

Thank you.
Reported and help requested. Let's see if that helps. :)
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: drake127 on May 30, 2016, 11:00:55 PM
We currently don't support removal of these CRT files as they are shared among most of our products. However, if you are determined to eradicate them, you can take ownership of them (only them!) and delete them:
C:\Windows\WinSxs\Manifest\*_avast.*
C:\Windows\WinSxs\*_avast.*


Also, you need to delete the following registry keys:
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\*_avast.*

Don't forget to reboot your system afterwards.
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: avant-guvnor on May 31, 2016, 03:12:46 AM
We currently don't support removal of these CRT files as they are shared among most of our products. However, if you are determined to eradicate them, you can take ownership of them (only them!) and delete them:
C:\Windows\WinSxs\Manifest\*_avast.*
C:\Windows\WinSxs\*_avast.*


Also, you need to delete the following registry keys:
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\*_avast.*

Don't forget to reboot your system afterwards.

Firstly, I am not determined to eradicate anything except system corruption. I am getting System File Checker corruption, which refers to Avast files (and is occurring on more than 1 Windows 10 Pro 64-bit PC). See the original post for the related problematic files/manifests.

The logical approach to fixing the corruption issue, which is caused by Avast free edition and Avast C runtime libraries, and recommended by Microsoft Support, was to remove Avast.

Secondly, I have already performed the removal you suggest here, which still does not fix the corruption issue. See my later post.

What I really want to know is how this corruption issue has occurred and how I can fix it. It is a recent problem, only appearing in the last 2 or 3 weeks, affects all my Windows 10 Pro 64-bit PCs and seems related to the 2016.11.2.2262 SafeZone Browser background update.
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: drake127 on May 31, 2016, 11:13:16 AM
That's interesting. Do you still have those files or did you irreversibly delete them? I cannot answer why SFC still detects our CRT if you removed all of its files. I tried to reproduce your issue on Windows 8.1 and 10 x64 but was unable to reproduce the issue. This makes me wonder if you really hadn't those manifest somehow broken.

Can you try to reinstall Avast? It might fix it by reinstalling CRT again.
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: avant-guvnor on May 31, 2016, 03:41:20 PM
That's interesting. Do you still have those files or did you irreversibly delete them? I cannot answer why SFC still detects our CRT if you removed all of its files. I tried to reproduce your issue on Windows 8.1 and 10 x64 but was unable to reproduce the issue. This makes me wonder if you really hadn't those manifest somehow broken.

Can you try to reinstall Avast? It might fix it by reinstalling CRT again.

All of the following were permanently deleted:
C:\Windows\WinSxs\Manifest\*_avast.*
C:\Windows\WinSxs\*_avast.*
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\*_avast.*

I have now reinstalled Avast 2016.11.2.2262 with my usual component selection:
(http://i751.photobucket.com/albums/xx157/mvilleuk/Avast/ce2dc156-dd64-4f3a-b010-db4530758cf3.jpg)

Next I restore my .avastconfig settings and reboot.

Then I login to my Avast account and always get this error:
Unexpected Error
An unexpected error occurred on the server, we are working on the solution.
Refresh

another reboot usually fixes this issue.

Finally I have run sfc /scannow which results in:
Windows Resource Protection found corrupt files but was unable to fix some
 of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
 example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not
 supported in offline servicing scenarios.

Here are the offending lines in the CBS.log:
2016-05-31 14:33:04, Info                  CSI    00004e9d [SR] Beginning Verify and Repair transaction
2016-05-31 14:33:04, Info                  CSI    00004e9e Manifest hash for component [l:73 ml:140]"amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.23918.0_none_53c8344321b452ba" does not match expected value.
 Expected:{l:32 b:714cddc73198abfd1a1a7dccbbca0808eda040d50b048b7e421d7afb8e2ac6b8}
 Found:{l:32 b:b77d27df43c464ca24067666962175bd050201195a9a3e9f4021c89abb2c29c0}.
2016-05-31 14:33:04, Info                  CSI    00004e9f Unable to load manifest for component [l:73 ml:140]"amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.23918.0_none_53c8344321b452ba"
2016-05-31 14:33:04, Info                  CSI    00004ea0 [SR] Cannot verify component files for Avast.VC140.CRT, version 14.0.23918.0, arch amd64, versionScope neutral, pkt {l:8 b:fcc99ee6193ebbca}, type [l:5]"win32", manifest is damaged (TRUE)
2016-05-31 14:33:04, Info                  CSI    00004ea1 Manifest hash for component [l:71 ml:140]"x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.23918.0_none_9b756b1a36307bc0" does not match expected value.
 Expected:{l:32 b:4379430502b6887d62d4283c0bfcb6aaf7b65e2d559321ca9b05a5c80c3f4357}
 Found:{l:32 b:d6b86bd6da85aef647b9c45e336c2ca37eda2e509c81bcf41b9bf06ca7c4f148}.
2016-05-31 14:33:04, Info                  CSI    00004ea2 Unable to load manifest for component [l:71 ml:140]"x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.23918.0_none_9b756b1a36307bc0"
2016-05-31 14:33:04, Info                  CSI    00004ea3 [SR] Cannot verify component files for Avast.VC140.CRT, version 14.0.23918.0, arch x86, versionScope neutral, pkt {l:8 b:fcc99ee6193ebbca}, type [l:5]"win32", manifest is damaged (TRUE)
2016-05-31 14:33:04, Info                  CSI    00004ea4 [SR] Cannot verify component files for policy.11.0.Avast.VC110.CRT, version 11.0.60610.1, arch x86, versionScope neutral, pkt {l:8 b:2036b14a11e83e4a}, type [l:12]"win32-policy", manifest is damaged (FALSE)
2016-05-31 14:33:04, Info                  CSI    00004ea5 [SR] Repair complete

This fiasco all started with my post Manage Accounts crashes GUI dated 12/04/2016 and the subsequent background fixes and the forced SafeZone browser background install, which has screwed things up for me on all my Windows 10 Pro 64-bit PCs. It does not affect any of my Windows 8.1 64-bit PCs that I administer.
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: avant-guvnor on May 31, 2016, 08:22:22 PM
By the way, I am not alone with this issue. Just seen this recent thread:
http://www.tenforums.com/performance-maintenance/50851-help-sfc-after-dvd-upgrade-10-please.html (http://www.tenforums.com/performance-maintenance/50851-help-sfc-after-dvd-upgrade-10-please.html)
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: avant-guvnor on June 01, 2016, 01:21:30 PM
I tried to reproduce your issue on Windows 8.1 and 10 x64 but was unable to reproduce the issue.

Firstly, as I have explained, the issue is not occurring on my Windows 8.1 Pro 64-bit PCs, only Windows 10 Pro 64-bit PCs.

Secondly, not reproducing this on 10 x64 is probably due to you not installing the same set of components as I do, so you are not replicating my Avast installation/setup.
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: Eddy on June 01, 2016, 01:40:02 PM
A little note :

SFC appends things to CBS.log but is not creating it.
Those entries can only be there if not everything from avast has been removed.
Unless there is somewhere a flaw in Windows that thinks not everything is removed.
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: avant-guvnor on June 01, 2016, 02:50:23 PM
SFC appends things to CBS.log but is not creating it.
Those entries can only be there if not everything from avast has been removed.
Unless there is somewhere a flaw in Windows that thinks not everything is removed.

I would gladly completely remove Avast from the affected PCs. Sadly, I am not the developer of this software and as such, I am not in a position to know whether everything Avast related has been removed.

Currently, I have been advised to re-install Avast (see reply #13), which I have done (see reply #14).
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: ralbrux on June 05, 2016, 10:38:39 AM
I too have the same problem.  I am using Avast Pro v 11.2.2262 on 2 desktop machines and 1 laptop.   The 2 desktops were upgraded from Win 7 Pro ultimate 64 to Win 10 Pro 64 about 3 weeks back and the laptop form Win 8.1 Home 64 to Win 10 Home 64.  Having run sfc /scannow 2 or 3 times on all these machines, I always get the same result indicating corrupted files which cannot be repaired.  The files in question are always AVAST.VC140.CRT files as per the original post.

Over the years I have learned that error messages are frequently long on "error" and short on "message".   At the end of the sfc scan it mentions "corrupted" files.   But in the cs log the incriminated files are not labeled as "corrupted".   Rather it says "Unable to load manifest" & "Cannot verify" for these Avast files.  Are these files really corrupted ?

Windows 10 has apparently added more stringent checking and controls for apps which have not received the latest version of Microsoft's "certification" for use with Win 10.

Could it be that this is the issue?

Could an Avast moderator make a comment as to whether or not this could be what is at issue here?

In advance thanks,
Richard
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: drake127 on June 05, 2016, 11:14:38 AM
What Windows 10 build do you have? Would you be kind enough to pack and upload incriminating files to our FTP server (ftp://ftp.avast.com/incoming/ (ftp://ftp.avast.com/incoming/))?

Edit: Link corrected, thanks.
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: Asyn on June 05, 2016, 11:44:42 AM
What Windows 10 build do you have? Would you be kind enough to pack and upload incriminating files to our FTP server (ftp://ftp.avast.com/incoming (http://ftp://ftp.avast.com/incoming))?
I may correct your FTP-link Drake: ftp://ftp.avast.com/incoming/ (ftp://ftp.avast.com/incoming/)
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: ralbrux on June 05, 2016, 06:53:12 PM
drake 127

In reply to your request for information the machine I'm on is running Windows 10 Pro v 1511 build 10586.318.

Using File Zilla I have uploaded to you ftp server a zip file (Avast.vc.140.crt.zip).  I cannot be sure that this is what you want.  When I did a search on my system drive for "AVAST.VC140.CRT" I got a whole slew of hits some of which are in the windows.old folder which still has the Win 7 setup in case I would want to revert to Win 7.   These hits include folders & files.  I was unable to copy everything in these hits to another folder, and that which I could copy weighs around 45 MB !

Given the extremely complicated naming conventions that Avast used for these files & folders it is well night impossible for me to see clearly what's what.   I used the file names that, as best as I could understand given what i saw when searching the cs log file for "AVAST.VC140.CRT., are concerned to select 4 files to transfer to you in the zip package.  Can't be sure given the plethora of files and folders and the complicated naming that this is what you want and need.

Best regards,
Richard
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: drake127 on June 06, 2016, 10:09:09 AM
I looked at files you sent me and it was exactly what I needed. It looks like you actually have broken catalogs, not manifest themselves. They aren't necessary for everyday use but they seem to be needed when upgrading OS (or consistency checks). I'll investigate further. I'll try to add fix to next beta (likely Thursday).
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: ralbrux on June 06, 2016, 11:25:38 AM
Ok drake 127.

Glad I got you what you needed.  I'll be watching things.

I can't really know, but I'm thinking the upgrade process to Win 10 is where some tricky complicated manipulations occurred.

Best regards,
Richard
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: avant-guvnor on June 06, 2016, 06:25:23 PM
What Windows 10 build do you have? Would you be kind enough to pack and upload incriminating files to our FTP server (ftp://ftp.avast.com/incoming/ (ftp://ftp.avast.com/incoming/))?

I am really not happy. Care to explain why you did not ask me for this information, rather than just ignoring me?

Not that I wish others to experience the same problem here, but thank goodness others have shared the same sfc issues, otherwise I would be @#*$ed!!

FYI, all my PCs with this issue are running Windows 10 Pro 64-bit, Version 1511, OS Build 10586.318.
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: drake127 on June 06, 2016, 06:31:44 PM
It was certainly not my intent to ignore you. I just hadn't time to address this topic until yesterday. I will be glad to hear from you if the fix works for you in next Beta.
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: avant-guvnor on June 10, 2016, 02:02:40 AM
It was certainly not my intent to ignore you. I just hadn't time to address this topic until yesterday. I will be glad to hear from you if the fix works for you in next Beta.

Does beta version 2016.12.1.2268, contain the fix?
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: drake127 on June 10, 2016, 02:20:35 AM
Yes, I believe it does.
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: cookiebear66 on June 13, 2016, 08:14:57 AM
I have the same issue. Did all the steps, delete files, regedit, uninstalled, reinstalled....same thing.
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: Asyn on June 13, 2016, 08:18:44 AM
I have the same issue. Did all the steps, delete files, regedit, uninstalled, reinstalled....same thing.
You could try the latest beta: https://forum.avast.com/index.php?board=15

Edit: See below...
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: drake127 on June 13, 2016, 02:52:16 PM
It's little bit embarrassing but I think I reintroduced this issue in 12.1.2269 by attempt to fix another issue with runtime. Hopefully, 12.1.2270 should be out soon and with both fixes.
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: Asyn on June 13, 2016, 03:04:52 PM
It's little bit embarrassing but I think I reintroduced this issue in 12.1.2269 by attempt to fix another issue with runtime.
Oops...
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: cookiebear66 on June 23, 2016, 04:44:47 AM
I have installed version 12.1.2272 and still getting the same error message.
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: StuBerg on June 24, 2016, 12:23:06 AM
I have this EXACT same problem.  I'm running Windows 10 Home 64-bit version 1511 build 10586.420 and Avast Free Antivirus 12.1.2272 build 12.1.3076.0 .

I can add one diagnostic suggestion that I didn't see anyone else suggesting.  After running SFP /Scannow, but before closing the elevated command prompt, run this command:

findstr /c:"[SR]" %windir%\logs\cbs\cbs.log >%userprofile%\Desktop\sfcdetails.txt

This will parse the SFC log file (CBS.log) creating a file called sfcdetails.txt on the Desktop in which it is MUCH easier to see the errors.
Stu
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: drake127 on June 24, 2016, 10:04:31 AM
Guys, I checked clean installation with exact same configuration as StuBerg but found no issues in CBS.log. Is it possible you have some left-overs there that may be broken?

These folders should be present in WinSxs directory (Vista+ x64):
amd64_avast.vc110.crt_2036b14a11e83e4a_11.0.60610.1_none_d58a6d64ab65b396
amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.23918.0_none_53c8344321b452ba
x86_avast.vc110.crt_2036b14a11e83e4a_11.0.60610.1_none_1d37a43bbfe1dc9c
x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.23918.0_none_9b756b1a36307bc0
x86_avast.vc140.mfc_fcc99ee6193ebbca_14.0.23918.0_none_a0556d0c3304aaf3
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: StuBerg on June 24, 2016, 02:45:57 PM
Hi Drake,
I have all the folders you listed above in the C:\Windows\WinSxS folder.  Each also has a "... .cat" and a "... .manifest" in the C:\Windows\WinSxS\Manifests folder EXCEPT these are missing the "... .cat" in that folder:

amd64_avast.vc110.crt_2036b14a11e83e4a_11.0.60610.1_none_d58a6d64ab65b396
x86_avast.vc110.crt_2036b14a11e83e4a_11.0.60610.1_none_1d37a43bbfe1dc9c

I don't know if the missing "... .cat" for the above two folders in the Manifests folder is an issue.

Above you said "I checked clean installation ... but found no issues in CBS.log".  Since CBS.log is so big, is it possible that you missed the errors?  Did you try running this command in an elevated command prompt to give you a much shorter listing of CBS.log:
findstr /c:"[SR]" %windir%\logs\cbs\cbs.log >%userprofile%\Desktop\sfcdetails.txt
When you run "SFC /Scannow", does it end normally and show no errors?
What is a "clean installation"?  Do I need to completely uninstall Avast (i.e. using Revo Uninstaller Pro) and reinstall to get a "clean installation"?
Stu
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: avant-guvnor on June 25, 2016, 03:10:55 AM
Guys, I checked clean installation with exact same configuration as StuBerg but found no issues in CBS.log. Is it possible you have some left-overs there that may be broken?

These folders should be present in WinSxs directory (Vista+ x64):
amd64_avast.vc110.crt_2036b14a11e83e4a_11.0.60610.1_none_d58a6d64ab65b396
amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.23918.0_none_53c8344321b452ba
x86_avast.vc110.crt_2036b14a11e83e4a_11.0.60610.1_none_1d37a43bbfe1dc9c
x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.23918.0_none_9b756b1a36307bc0
x86_avast.vc140.mfc_fcc99ee6193ebbca_14.0.23918.0_none_a0556d0c3304aaf3

The problem was introduced by earlier Avast software installs and now, it may well be ok to install 12.1.2272 on a clean machine. However, for PCs with the problem, the new version 12.1.2272 does not fix the issue.

Please advise, with step-by-step instructions, how users with the problem, are to supposed to eradicate the problem. It is now 4 weeks that I have struggled with this and still no resolution.

... in addition, here is the [SR] text extracted from the CBS.log after installing Avast Free Edition 12.1.2272, using Stuberg's findstr cmd:
2016-06-25 17:13:03, Info                  CSI    00004f2d [SR] Cannot verify component files for Avast.VC140.CRT, version 14.0.23918.0, arch amd64, versionScope neutral, pkt {l:8 b:fcc99ee6193ebbca}, type [l:5]"win32", manifest is damaged (TRUE)
2016-06-25 17:13:03, Info                  CSI    00004f30 [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-06-25 17:13:03, Info                  CSI    00004f33 [SR] Cannot verify component files for Avast.VC140.CRT, version 14.0.23918.0, arch x86, versionScope neutral, pkt {l:8 b:fcc99ee6193ebbca}, type [l:5]"win32", manifest is damaged (TRUE)
2016-06-25 17:13:03, Info                  CSI    00004f36 [SR] Cannot verify component files for Avast.VC140.MFC, version 14.0.23918.0, arch x86, versionScope neutral, pkt {l:8 b:fcc99ee6193ebbca}, type [l:5]"win32", manifest is damaged (TRUE)
2016-06-25 17:13:03, Info                  CSI    00004f39 [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-06-25 17:13:03, Info                  CSI    00004f3a [SR] Cannot verify component files for policy.11.0.Avast.VC110.CRT, version 11.0.60610.1, arch x86, versionScope neutral, pkt {l:8 b:2036b14a11e83e4a}, type [l:12]"win32-policy", manifest is damaged (FALSE)

PLEAS NOTE: this log is the same as the log posted by cookiebear66 below, except I have an additional reference to policy.11.0.Avast.VC110.CRT, version 11.0.60610.1, arch x86.
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: cookiebear66 on June 25, 2016, 05:04:49 AM
Here is what the txt file extracted.
2016-06-24 22:50:25, Info                  CSI    0000543b [SR] Cannot verify component files for Avast.VC140.CRT, version 14.0.23918.0, arch amd64, versionScope neutral, pkt {l:8 b:fcc99ee6193ebbca}, type [l:5]"win32", manifest is damaged (TRUE)
2016-06-24 22:50:25, Info                  CSI    0000543e [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-06-24 22:50:25, Info                  CSI    00005441 [SR] Cannot verify component files for Avast.VC140.CRT, version 14.0.23918.0, arch x86, versionScope neutral, pkt {l:8 b:fcc99ee6193ebbca}, type [l:5]"win32", manifest is damaged (TRUE)
2016-06-24 22:50:25, Info                  CSI    00005444 [SR] Cannot verify component files for Avast.VC140.MFC, version 14.0.23918.0, arch x86, versionScope neutral, pkt {l:8 b:fcc99ee6193ebbca}, type [l:5]"win32", manifest is damaged (TRUE)
2016-06-24 22:50:25, Info                  CSI    00005447 [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)
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: StuBerg on June 25, 2016, 05:21:26 AM
Here are the CBS.log errors from my run of SFC /Scannow:

2016-06-23 12:15:45, Info                  CSI    00000426 [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-06-23 12:26:09, Info                  CSI    00004940 [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-06-23 12:28:21, Info                  CSI    000057ee [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-06-23 12:28:21, Info                  CSI    000057f1 [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-06-23 13:22:29, Info                  CSI    0000040e [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-06-23 13:30:08, Info                  CSI    0000482b [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-06-23 13:31:43, Info                  CSI    00005634 [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-06-23 13:31:43, Info                  CSI    00005637 [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)

It's interesting that cookiebear66 (above posting) had 3 different Avast file names with this problem while all of mine are the same Avast file name (Avast.VC110.CRT).
Stu
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: cookiebear66 on June 25, 2016, 06:17:19 AM
@Stuberg ya weird. And this is a fresh install. Uninstalled and re-installed.
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: StuBerg on June 25, 2016, 01:51:50 PM
@cookiebear66:  If being a meticulous, OCD, engineer in solving this problem is "weird", I'm definitely guilty.   Simply using Windows 10 to uninstall and then re-installing is one type of clean install.  Another, much more thorough, uninstall and re-install would be to use software like "Revo Uninstaller" (http://www.revouninstaller.com/ (http://www.revouninstaller.com/)) to do the uninstalling before re-installing.  Software like Revo Uninstaller removes every last "crumb" of the previously installed program.  Revo Uninstaller first runs the normal Windows uninstall and then searches for all the leftovers and allows you to pick and choose which leftovers you want to delete.  In my experience, it's very rare that Revo Uninstaller doesn't find these leftovers in every uninstall.

So it sounds like you used the normal Windows 10 uninstall before re-installing Avast and are still getting this problem.  That's very good information to know.  Did you check after the uninstall to see if all of your 3 offending files (Avast.VC140.CRT, Avast.VC110.CRT, and Avast.VC140.MFC) were deleted?  My guess is that they were, but that's only a guess.  If they were and the reinstall installed the files again, it would then be 100% sure that it's an Avast problem.
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: drake127 on June 25, 2016, 10:50:53 PM
The most probable cause of this issue is missing or mismatching catalog file. If some of you had broken manifest, Avast would likely fail to start. StuBerg's log message confirms it as he is missing VC110 catalogs. The question is why you are missing them because I just peeked through the code and tested several scenarios (basically clean install and few updated from older version) on Windows 10 and I got all catalogs present and accounted for. Even tried to delete them manually and then performed update but they were correctly recovered.

In this specific case, uninstallation does not do much good because these WinSxs files are one of the few to be left behind*. However, our installer attempts to "update" them even if they are present so this should not be a problem. Actually, there should be no need to uinstall/reinstall - repair should be just enough to fix these files.

Can you look into Avast installation directory under Setup\CRT (something like C:\Program Files\AVAST Software\Avast\Setup\CRT)? You should find there all CRT packages (with unmangled names). Do you have manifests and catalogs there? Do they match files you find in WinSxs folder?
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: StuBerg on June 25, 2016, 11:22:58 PM
@Drake127:  All I have in the C:\Program Files\AVAST Software\Avast\setup\CRT directory is a Data sub-directory and the InstallCrt.exe program.  The Data directory has 3 sub-directories; avast.vc110.crt, avast.vc140.crt, and avast.vc140.mfc .  Each of those 3 sub-directories has 2 sub-directories; amd64 and x86 EXCEPT for the avast.vc140.mfc sub-directory which only has x86 (meaning there are only 5 sub-directories at this lowest level).  Each of those 5 sub-directories has an appropriately named ".cat" and an appropriately named ".manifest" file.  So, is the problem that the avast.vc140.mfc sub-directory is missing the amd64 sub-directory?  If so, should I add it and then run a repair?

By the way, I had run the Avast Repair previously but it did not help this problem.
Stu
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: drake127 on June 25, 2016, 11:42:18 PM
We don't distribute x64 version of MFC, that's fine. It's really odd that you are missing those catalogs yet you have them in the setup folder. Are you familiar with procmon.exe? Would you be kind enough to run it, perform repair and send me the PML file?
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: StuBerg on June 26, 2016, 12:29:35 AM
@drake127:  I run Microsoft Process Monitor v3.2, but I've never used it for a repair.  If you can tell me how to do a repair using it, I'll do it.
Thanks,
Stu
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: drake127 on June 26, 2016, 12:37:23 AM
You just run procmon.exe. It might ask you to setup filters but defaults are just fine. When you see that events are being collected (there are going to be thousands of them), you can leave procmon to run in background and just start Avast repair. Procmon will log all registry and file operations. After the repair is successful, switch to procmon and save the log to PML file (again, defaults are fine). The file will be probably rather large so upload it to our FTP site (ftp://ftp.avast.com/pub/ (ftp://ftp.avast.com/pub/)) and let me know.
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: StuBerg on June 26, 2016, 03:47:56 AM
@drake127:  First, I want you to know that the Logfile.PML file is 3.95GB (yes, that's GIGABYTES).  It would be a whole lot easier if you would suggest a filter that would leave everything you need but make it much smaller.  Next, I haven't done FTPing since my XP days, so my Windows 10 PC had no FTP client installed.  I installed Filezilla but I'm having a real hard time getting it to connect to ftp://ftp.avast.com/pub/, even with using their Network Configuration Wizard.  I get a "Failed to create listen socket" error.  Do you have any other suggestions that could make this less painful?
Thanks,
Stu
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: drake127 on June 26, 2016, 03:52:19 AM
Yeah, that's little too big. Maybe setting filter to "Path contains 'avast.vc'" might be a good idea. Don't forget to also check "Drop Filtered Events". Uploading to FTP should be easy - just open it with Windows Explorer (not Internet Explorer).
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: StuBerg on June 26, 2016, 04:16:17 AM
@drake127:  I did as you suggested, but when I dragged the file to your FTP server Pub directory through Windows Explorer, I got the attached error message.
P.S. The file is only 3.2MB now!
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: drake127 on June 26, 2016, 04:22:12 AM
Yes, because I always get that URL wrong. It's ftp://ftp.avast.com/incoming
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: StuBerg on June 26, 2016, 04:30:11 AM
@drake127: That explains why I couldn't get FileZilla nor Windows Explorer to work!  You should now have the Logfile.PML .
Stu
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: StuBerg on June 27, 2016, 07:08:45 AM
@drake127: When you release the next beta with, hopefully, the resolution of this problem, please post the link to the beta download in this forum topic.
Thanks,
Stu
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: drake127 on June 27, 2016, 01:27:57 PM
Right, I fixed v110 errors but I still have no idea why some of you are experiencing issues with v140.
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: avant-guvnor on June 28, 2016, 01:05:43 PM
Can you look into Avast installation directory under Setup\CRT (something like C:\Program Files\AVAST Software\Avast\Setup\CRT)? You should find there all CRT packages (with unmangled names). Do you have manifests and catalogs there? Do they match files you find in WinSxs folder?

This is what is in the CRT directory:
(http://i751.photobucket.com/albums/xx157/mvilleuk/Avast/avastcrt.jpg)

and each (amd64 and x86) sub-directory contains a .cat and .manifest file.

These are in the WinSxS directory:
(http://i751.photobucket.com/albums/xx157/mvilleuk/Avast/avastwinsxs.jpg)

I have performed an Avast v.12.1.2272 repair and uploaded Avast_12.1.2272_Repair_Logfile.PML to the ftp server.

Just as a side note, running the repair ends with the Failed to load language dll error.
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: bob3160 on June 28, 2016, 02:36:35 PM
"Just as a side note, running the repair ends with the Failed to load language dll error."
It may be time to do a clean install of Avast:

Clean Install of Avast:
https://goo.gl/4Ptzkf
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: avant-guvnor on June 28, 2016, 02:42:25 PM
"Just as a side note, running the repair ends with the Failed to load language dll error."
It may be time to do a clean install of Avast:

Clean Install of Avast:
https://goo.gl/4Ptzkf

This was a clean install.
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: bob3160 on June 28, 2016, 02:49:56 PM
"Just as a side note, running the repair ends with the Failed to load language dll error."
It may be time to do a clean install of Avast:

Clean Install of Avast:
https://goo.gl/4Ptzkf (https://goo.gl/4Ptzkf)

This was a clean install.
You mentioned repair ???
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: avant-guvnor on June 28, 2016, 03:16:57 PM
"Just as a side note, running the repair ends with the Failed to load language dll error."
It may be time to do a clean install of Avast:

Clean Install of Avast:
https://goo.gl/4Ptzkf (https://goo.gl/4Ptzkf)

This was a clean install.
You mentioned repair ???

Correct, repair is what has been instructed by drake127 and I am reporting that the Repair produces this error.

Due to the issues outlined in this thread, I have done many clean installs in the past few weeks, followed by a Repair, which more often than not produces the Failed to load language dll error.

My faith in Avast's ability to produce a stable Windows 8.1/10 installation is dwindling rapidly. I believe (based on my experiences over the past couple of years with the Avast software) that with so many component option combinations available on install and with the forced/emergency updates, Avast have just not tested all possible scenarios on all platforms, hence the problems that have arisen that are outlined in this thread.
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: bob3160 on June 28, 2016, 03:24:48 PM
"Avast have just not tested all possible scenarios on all platforms"
You're asking for something that's virtually impossible.
I've personally installed Avast on many systems from Windows XP through Windows 10 and
have had very little problems. I do have 1 system on Windows 10 that refuses to allow me to save my Avast settings.

(Sorry, I've taken this off topic)
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: avant-guvnor on June 28, 2016, 03:35:32 PM
"Avast have just not tested all possible scenarios on all platforms"
You're asking for something that's virtually impossible.
I've personally installed Avast on many systems from Windows XP through Windows 10 and
have had very little problems. I do have 1 system on Windows 10 that refuses to allow me to save my Avast settings.

(Sorry, I've taken this off topic)

I too have installed Avast on many PCs over the years and in the main Avast was rock solid. It is only recently (in the last couple of years) that I have seen issues appearing, especially with custom component installations.
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: x30204 on July 01, 2016, 06:09:35 PM
Hello,
Every week, I run the command SFC / scannow before i make a backup of my C drive.
so far I've never had a problem but today Avast has just done an update and  the ommand SFC gave some errors on the file "Avast.VC110.CRT".

see below:

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)
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)
Repair complete
Committing transaction


I restored my system with my previous backup and disabeled the automatic update in Avast  internet security until you resolve this issue.

Many thanks.

Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: ralbrux on July 02, 2016, 03:14:34 PM
Hi.  Subsequent to my initial post on June 5 and Avast team drake 127's statement that he would try to fix the issue in an upcoming upgrade, I had been waiting for my AVAST Pro v 11.2.2262 to upgrade.  It did so just the day before yesterday to v 12.1.2272.

The problem persists.

Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: akewinther on July 02, 2016, 03:44:40 PM
Same pr0blem here running latest win10x64 v xxxxxx.240
started after latest avast program update
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: _Denny_ on July 03, 2016, 05:34:50 PM
Here's how i solved this sfc error; i won't go into details how exactly to do every step...don't ask me how to take ownership, load a registry hive, etc, google it. You should do that only if you plan to completely uninstall Avast and replace it with something else! If you reinstall it, the sfc errors will be (sadly) back...

1. Uninstall Avast with avastclear (https://www.avast.com/uninstall-utility)
2. Remove every file with "avast" in it's filename (everywhere, even in winsxs); take ownership if Windows doesn't allow it.
3. Remove every avast reference from registry
4. Boot your pc with any WinPE service disc/usb that has regedit (i recommend Sergei Strelec WinPE, Hiren's Boot CD is also ok), load the COMPONENTS registry hive (it's in C:\Windows\System32\config, backup it first; you may need to take ownership and/or unmark it as read-only)
5. Remove ALL avast references from the loaded hive, close regedit, restore COMPONENTS file ownership (if you took it) and restart
6. Run sfc /scannow and check if there are still avast-related errors; run dism /online /cleanup-image /restorehealth too just to see if everything else is ok too.

I've used Avast for 10+ years, recommended it to literally everyone and was never disappointed until Win10 came...hours of wasted time with OS reinstalls on my and customer pc's because dism kept failing at 20% (avast locked it, would never suspect that), then those false sfc errors...
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: antonakispantelis on July 10, 2016, 11:43:28 AM
Hello everyone
It is probably outdated but the problem is FINALLY solved. I just finished my second win10 64bit pc. In brief I uninstalled avast free with revo uninstaller, deleted all files containing avast from c: (including winsxs manifest temp files etc), cleaned up registry from all avast containing records with regedit and after a reboot I did a Repair Install of Windows 10 with an In-place Upgrade following this guide http://www.tenforums.com/tutorials/16397-repair-install-windows-10-place-upgrade.html. After that I ran sfc/scannow which actually DID the necessary repairs, rebooted and voila. System file checker now reports NO violations. And yes I rechecked after reinstalling the latest avast build. Everything works as it should
Cheers
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: avant-guvnor on July 10, 2016, 12:44:47 PM
It is probably outdated but the problem is FINALLY solved. I just finished my second win10 64bit pc. In brief I uninstalled avast free with revo uninstaller, deleted all files containing avast from c: (including winsxs manifest temp files etc), cleaned up registry from all avast containing records with regedit and after a reboot I did a Repair Install of Windows 10 with an In-place Upgrade following this guide http://www.tenforums.com/tutorials/16397-repair-install-windows-10-place-upgrade.html. After that I ran sfc/scannow which actually DID the necessary repairs, rebooted and voila. System file checker now reports NO violations. And yes I rechecked after reinstalling the latest avast build. Everything works as it should

Glad you fixed the issue on your PCs, but from my point of view, I don't regard an in-place upgrade of Windows 10 as a reasonable solution to the problem, especially when you consider the number of PCs I administer, that exhibit the problem.

As I understand it, Avast are to release an installer that will check for rogue WinSxS files/registry keys and perform any necessary fixes. Hopefully, this will finally resolve the underlying sfc corruption.
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: Patrick99 on July 10, 2016, 06:02:39 PM
I agree, an inplace re-install of Win10 should not be the solution to this issue. It has plagued me for two months now and I am looking forward to a fix that will solve the SFC scan error.

I may have missed it, but is there a way to take ownership of the avast files in WinSxS such that I can manually delete them:

C:\Windows\WinSxS\amd64_avast.vc110.crt_2036b14a11e83e4a_11.0.60610.1_none_d58a6d64ab65b396
C:\Windows\WinSxS\amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.23506.0_none_545784f92070b665
C:\Windows\WinSxS\amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.23918.0_none_53c8344321b452ba
C:\Windows\WinSxS\x86_avast.vc110.crt_2036b14a11e83e4a_11.0.60610.1_none_1d37a43bbfe1dc9c
C:\Windows\WinSxS\x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.23506.0_none_9c04bbd034ecdf6b
C:\Windows\WinSxS\x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.23918.0_none_9b756b1a36307bc0
C:\Windows\WinSxS\x86_avast.vc140.mfc_fcc99ee6193ebbca_14.0.23506.0_none_a0e4bdc231c10e9e
C:\Windows\WinSxS\x86_avast.vc140.mfc_fcc99ee6193ebbca_14.0.23918.0_none_a0556d0c3304aaf3

The solution suggested at AskVG for changing ownership from TrustedInstaller to my admin account fails as no dialog opens to add a new userID at the Security panel in question.

RE: Program version: 12.1.2272 (build 12.1.3076.0)
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: CraigB on July 10, 2016, 06:30:55 PM
I agree, an inplace re-install of Win10 should not be the solution to this issue. It has plagued me for two months now and I am looking forward to a fix that will solve the SFC scan error.

I may have missed it, but is there a way to take ownership of the avast files in WinSxS such that I can manually delete them:

amd64_avast.vc110.crt_2036b14a11 e83e4a_11.0.60610.1_none_d58a6d64ab65b396 amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.23506.0_none_545784f92070b665 amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.23918.0_none_53c8344321b452ba x86_avast.vc110.crt_2036b14a11 e83e4a_11.0.60610.1_none_1 d37a43bbfe1 dc9c x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.23506.0_none_9c04bbd034ecdf6b x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.23918.0_none_9b756b1 a36307bc0 x86_avast.vc140.mfc_fcc99ee6193ebbca_14.0.23506.0_none_a0e4bdc231c10e9e
x86 avast.vc140.mfc fcc99ee6193ebbca 14.0.23918.0 none a0556d0c3304aaf3

The solution suggested at AskVG for changing ownership from TrustedInstaller to my admin account fails as no dialog opens to add a new userID at the Security panel in question.
The Take Ownership script provided on ASKVG has always worked for me on Vista to Win10 http://www.askvg.com/add-take-ownership-option-in-file-folder-context-menu-in-windows-vista/
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: Patrick99 on July 10, 2016, 10:18:11 PM
As noted:

"The solution suggested at AskVG for changing ownership from TrustedInstaller to my admin account fails as no dialog opens to add a new userID at the Security panel in question."

Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: antonakispantelis on July 10, 2016, 11:53:55 PM
I agree, an inplace re-install of Win10 should not be the solution to this issue. It has plagued me for two months now and I am looking forward to a fix that will solve the SFC scan error.

I may have missed it, but is there a way to take ownership of the avast files in WinSxS such that I can manually delete them:

C:\Windows\WinSxS\amd64_avast.vc110.crt_2036b14a11e83e4a_11.0.60610.1_none_d58a6d64ab65b396
C:\Windows\WinSxS\amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.23506.0_none_545784f92070b665
C:\Windows\WinSxS\amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.23918.0_none_53c8344321b452ba
C:\Windows\WinSxS\x86_avast.vc110.crt_2036b14a11e83e4a_11.0.60610.1_none_1d37a43bbfe1dc9c
C:\Windows\WinSxS\x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.23506.0_none_9c04bbd034ecdf6b
C:\Windows\WinSxS\x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.23918.0_none_9b756b1a36307bc0
C:\Windows\WinSxS\x86_avast.vc140.mfc_fcc99ee6193ebbca_14.0.23506.0_none_a0e4bdc231c10e9e
C:\Windows\WinSxS\x86_avast.vc140.mfc_fcc99ee6193ebbca_14.0.23918.0_none_a0556d0c3304aaf3

The solution suggested at AskVG for changing ownership from TrustedInstaller to my admin account fails as no dialog opens to add a new userID at the Security panel in question.

RE: Program version: 12.1.2272 (build 12.1.3076.0)

To tell you the truth I did it manually from properties>security etc
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: antonakispantelis on July 11, 2016, 12:34:34 AM
For a large number of PCs where you would want a quick automated and reproducible solution I think that AVAST developers need to provide us with .... something.
For one or three PCs (like in my case) I found rather handy an inplace reinstall. Above all it solved for me the problem after a month or so of fruitless efforts. In general I totally agree that this should not be the solution but nevertheless it is one effective solution. Before this I simply could not solve it no matter what. It took me at least one hour to uninstall avast, clean the registry and all files (including WinSxS) especially because I had to take ownership for each file/folder, before deleting them. Even after having deleted everything the sfc errors were there. That is why I resorted to the inplace reinstall. That took less than half an hour and now I am a happy puppy again.
Cheers
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: CraigB on July 11, 2016, 08:26:08 AM
As noted:

"The solution suggested at AskVG for changing ownership from TrustedInstaller to my admin account fails as no dialog opens to add a new userID at the Security panel in question."
So you have installed the registry script and have "Take ownership" added to your context menu?
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: Patrick99 on July 11, 2016, 08:35:16 AM
As noted:

"The solution suggested at AskVG for changing ownership from TrustedInstaller to my admin account fails as no dialog opens to add a new userID at the Security panel in question."
So you have installed the registry script and have "Take ownership" added to your context menu?
Yes, and when used "permission denied" is the error message.
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: CraigB on July 11, 2016, 08:46:08 AM
Sounds like you might need to run some logs so one of the specialists can have a look at what might be wrong with your system.
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: N@URINE on July 13, 2016, 12:48:35 AM
I have exactly the same problem, I uninstalled Avast and run SFC, but in vain.


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)
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)
Repair complete
Committing transaction


I restored my system with my previous backup and disabeled the automatic update in Avast  internet security until you resolve this issue.

Many thanks.
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: N@URINE on July 13, 2016, 12:56:55 AM
I have windows 8.1

I tried to reproduce your issue on Windows 8.1 and 10 x64 but was unable to reproduce the issue.

Firstly, as I have explained, the issue is not occurring on my Windows 8.1 Pro 64-bit PCs, only Windows 10 Pro 64-bit PCs.

Secondly, not reproducing this on 10 x64 is probably due to you not installing the same set of components as I do, so you are not replicating my Avast installation/setup.
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: N@URINE on July 13, 2016, 01:31:59 AM
I'll give it a shot


We currently don't support removal of these CRT files as they are shared among most of our products. However, if you are determined to eradicate them, you can take ownership of them (only them!) and delete them:
C:\Windows\WinSxs\Manifest\*_avast.*
C:\Windows\WinSxs\*_avast.*


Also, you need to delete the following registry keys:
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\*_avast.*

Don't forget to reboot your system afterwards.
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: Go The Power on July 15, 2016, 09:51:41 AM
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

Code: [Select]
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

Code: [Select]
[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
Code: [Select]
[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.
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: Patrick99 on July 15, 2016, 08:18:28 PM
What Windows OS are you using that contains the COMPONENTS registry hive? I am not seeing that in the Windows 10 registry

EDIT: Ran a registry cleanup and now see COMPONENTS hive in regedit
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: N@URINE on July 16, 2016, 12:22:32 AM
What Windows OS are you using that contains the COMPONENTS registry hive? I am not seeing that in the Windows 10 registry

neither do I! on Windows 8.1
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: N@URINE on July 16, 2016, 12:25:19 AM
I searched for this in the registry 'amd64_avast.vc110.crt_2036b14a11e83e4a_11.0.60610.1_none_d58a6d64ab65b396', but I didn't find it, either.
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: N@URINE on July 16, 2016, 12:39:35 AM
for me this is where my problem is:

2016-07-13 17:37:11, Info                  CSI    0000090a [SR] Cannot verify component files for Avast.VC110.CRT, Version = 11.0.60610.1, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:2036b14a11e83e4a}, Type = [l:10{5}]"win32", TypeName neutral, PublicKey neutral, manifest is damaged (TRUE)
2016-07-13 17:37:11, Info                  CSI    0000090d [SR] Cannot verify component files for Avast.VC110.CRT, Version = 11.0.60610.1, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:2036b14a11e83e4a}, Type = [l:10{5}]"win32", TypeName neutral, PublicKey neutral, manifest is damaged (TRUE)
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: Go The Power on July 16, 2016, 01:08:31 AM
The COMPONETS Hive gets loaded when its needed, for example when Windows Updates runs it will load the hive, when SFC runs it loads the hive etc.

The hive is located inside of C:\Windows\System32\config

The easiest way to load the hive is is to type into the search box(next to the start menu) windows features, select "turn windows features on and off", leave this window open.

I created a tutorial yesterday that will resolve this issue:
https://www.sysnative.com/forums/windows-update/20590-windows-10-avast-causing-corrupt-manifest-files-fix.html
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: N@URINE on July 16, 2016, 01:50:32 PM
many many thanks Go The Power
it really worked like magic.  ;)
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: drake127 on July 16, 2016, 03:02:11 PM
To answer Go The Power's question, all manifests are correct. The reason why Windows complains about them is the fact that we added additional signatures to them. Unfortunately, in case of VC110, we used old catalog files. In case of VC140, we ommited to clean COMPONENTS cache.

The reason I didn't comment about a fix is that MS released new version of the runtime. New Avast versions will distribute only VC140 runtime (14.0.24210.0) with overriding policy making both VC110 and VC140 (14.0.23506.0 and 14.0.23918.0) obsolete. This makes it tricky to fix VC110 error as I would like to avoid having to distribute this runtime in following versions. As for VC140, I intend to completely remove it which should solve the issue.
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: Patrick99 on July 24, 2016, 09:57:09 PM
Removed the manifests in question. Later had to do a repair install of Windows 10 for other reasons. Now Avast SecureLine refuses my license file and will not work. Submitted a ticket but I suspect it is because the Avast110 manifests have been removed.
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: drake127 on July 24, 2016, 10:16:05 PM
That sounds likely. We plan to release emergency update for build 2272 but for now you have two options:
1) Repair your installation, this should reinstall VC110 runtime.
2) Update to latest beta (2275+) where SecureLine does not use VC110 runtime anymore.
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: Patrick99 on July 24, 2016, 10:23:34 PM
Yes, I installed the beta version before reading your latest post and the problem has solved itself. A repair install would have just re-started the whole SCF scannow debacle. Whew!

I also updated my submitted ticket with relevant information and pointers to this discussion asking that the ticket now be considered closed.
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: drake127 on July 25, 2016, 06:24:10 PM
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.
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: Starship1 on July 29, 2016, 09:33:28 PM
Quote
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,
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: moses_x on August 20, 2016, 01:17:29 AM
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   
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: bob3160 on August 20, 2016, 03:20:28 PM
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
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: drake127 on August 22, 2016, 01:21:56 AM
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.
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: avscott2015 on September 09, 2016, 03:38:21 AM
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.
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: avscott2015 on September 14, 2016, 04:36:35 AM
So problem clears up after Anniversary Update right?
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: drake127 on September 14, 2016, 08:41:13 AM
Yes, but I must stress out that this was always cosmetic issue. It had no effect on functionality of Avast or Windows.
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: avscott2015 on September 14, 2016, 03:48:04 PM
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. 
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: mchain on September 14, 2016, 09:42:57 PM
To reiterate, running sfc /scannow in safe mode shows no errors, so any errors reported in normal mode are just that, superficial.
Title: Re: Avast, Windows 10 pro 64-bit and System File Checker
Post by: avscott2015 on September 14, 2016, 10:34:25 PM
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.