Author Topic: Avast, Windows 10 pro 64-bit and System File Checker  (Read 49702 times)

0 Members and 1 Guest are viewing this topic.

Offline Asyn

  • Avast √úberevangelist
  • Certainly Bot
  • *****
  • Posts: 72174
    • >>>  Avast Forum - Deutschsprachiger Bereich  <<<
Re: Avast, Windows 10 pro 64-bit and System File Checker
« Reply #30 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...
« Last Edit: June 13, 2016, 03:06:04 PM by Asyn »
Win 8.1 [x64] - Avast PremSec 21.9.6660.IBC [UI.670] - EEK - Firefox ESR 78.15 [NS/uBO/PB] - TB 91.2
Avast-Tools: Secure Browser 94.0 - Cleanup 21.3 - SecureLine 5.13 - Driver Updater 21.3 - CCleaner 5.85
Avast Wissenswertes (Downloads, Anleitungen & Infos): https://forum.avast.com/index.php?topic=60523.0

Offline drake127

  • Avast team
  • Sr. Member
  • *
  • Posts: 324
Re: Avast, Windows 10 pro 64-bit and System File Checker
« Reply #31 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.

Offline Asyn

  • Avast √úberevangelist
  • Certainly Bot
  • *****
  • Posts: 72174
    • >>>  Avast Forum - Deutschsprachiger Bereich  <<<
Re: Avast, Windows 10 pro 64-bit and System File Checker
« Reply #32 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...
Win 8.1 [x64] - Avast PremSec 21.9.6660.IBC [UI.670] - EEK - Firefox ESR 78.15 [NS/uBO/PB] - TB 91.2
Avast-Tools: Secure Browser 94.0 - Cleanup 21.3 - SecureLine 5.13 - Driver Updater 21.3 - CCleaner 5.85
Avast Wissenswertes (Downloads, Anleitungen & Infos): https://forum.avast.com/index.php?topic=60523.0

Offline cookiebear66

  • Newbie
  • *
  • Posts: 5
Re: Avast, Windows 10 pro 64-bit and System File Checker
« Reply #33 on: June 23, 2016, 04:44:47 AM »
I have installed version 12.1.2272 and still getting the same error message.

Offline StuBerg

  • Newbie
  • *
  • Posts: 10
Re: Avast, Windows 10 pro 64-bit and System File Checker
« Reply #34 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
« Last Edit: June 24, 2016, 12:25:25 AM by ad337998 »

Offline drake127

  • Avast team
  • Sr. Member
  • *
  • Posts: 324
Re: Avast, Windows 10 pro 64-bit and System File Checker
« Reply #35 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

Offline StuBerg

  • Newbie
  • *
  • Posts: 10
Re: Avast, Windows 10 pro 64-bit and System File Checker
« Reply #36 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
« Last Edit: June 24, 2016, 02:47:30 PM by StuBerg »

Offline avant-guvnor

  • Full Member
  • ***
  • Posts: 107
Re: Avast, Windows 10 pro 64-bit and System File Checker
« Reply #37 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.
« Last Edit: June 26, 2016, 02:44:37 AM by mville »

Offline cookiebear66

  • Newbie
  • *
  • Posts: 5
Re: Avast, Windows 10 pro 64-bit and System File Checker
« Reply #38 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)

Offline StuBerg

  • Newbie
  • *
  • Posts: 10
Re: Avast, Windows 10 pro 64-bit and System File Checker
« Reply #39 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
« Last Edit: June 25, 2016, 05:25:07 AM by StuBerg »

Offline cookiebear66

  • Newbie
  • *
  • Posts: 5
Re: Avast, Windows 10 pro 64-bit and System File Checker
« Reply #40 on: June 25, 2016, 06:17:19 AM »
@Stuberg ya weird. And this is a fresh install. Uninstalled and re-installed.

Offline StuBerg

  • Newbie
  • *
  • Posts: 10
Re: Avast, Windows 10 pro 64-bit and System File Checker
« Reply #41 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/) 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.

Offline drake127

  • Avast team
  • Sr. Member
  • *
  • Posts: 324
Re: Avast, Windows 10 pro 64-bit and System File Checker
« Reply #42 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?

Offline StuBerg

  • Newbie
  • *
  • Posts: 10
Re: Avast, Windows 10 pro 64-bit and System File Checker
« Reply #43 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

Offline drake127

  • Avast team
  • Sr. Member
  • *
  • Posts: 324
Re: Avast, Windows 10 pro 64-bit and System File Checker
« Reply #44 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?
« Last Edit: June 25, 2016, 11:51:12 PM by drake127 »