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/)?
Edit: Link corrected, thanks.
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/)?
Edit: Link corrected, thanks.
I may correct your FTP-link Drake: ftp://ftp.avast.com/incoming/
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
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).
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
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.
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?
Yes, I believe it does.
I have the same issue. Did all the steps, delete files, regedit, uninstalled, reinstalled…same thing.
[s]You could try the latest beta: https://forum.avast.com/index.php?board=15[/s]
Edit: See below…
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.
Oops…
I have installed version 12.1.2272 and still getting the same error message.
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
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
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
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.
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)
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