I wrote done the name of the following file as Avast was doing a bootup scan:
file:///C:/Documents%20and%20Settings/All%20Users/Application%20Data/AVAST%20Software/Avast/report/aswBoot.txt
Long name, isn't it? This file seems to contain all possible problems and errors found by the scheduled Avast bootup scan.
The Avast bootup scan came up with the following error on 3 files on my hard drive:
Error 42127 {CAB archive is corrupted
The Avast website has this to say about this particular error:
Boot-Time Scan Error 42127 {CAB archive is corrupted}
Sounds like it is no big deal. Since all 3 instances of error 42127 are Google Earth files, I'll assume that the problem is that Avast cannot interpret the files. This could be a common problem.
I suppose the way to fine out for sure is to install and uninstall Google Earth. Don't think I'll do this quite yet. I'm not that worried.
Here's another site that suggests that the only thing this is is a file format that Avast cannot read:
Avast boot time scan showing corrupt files
Maybe I should be more worried than I am. If Avast cannot interpret the file format, this could be an excellent place for malware to hide. At least, that's my theory. However, maybe I'm wrong. After all, the malware cannot really hide unless it itself understands the file format. How does malware hide its own signature unless it encrypts its own signature in some way? So, maybe its not such an ideal place to hide after all.
Update: June 19, 2014
I ran a boot-time scan overnight. Came up with errors 42125 and 42127. Here's what the Avast Forum says:
Sounds like both these errors are zero big deal. I'm not going to worry about it.
Update: October 22, 2014
Wow! Computers get more complicated every year. It appears that now you have to explicitly request a log file:
No aswBoot.txt File Nor Folder Created to Store It
That's one reason why I have this blog. So many things to keep track of!
Ed Abbott