system
February 22, 2009, 7:42pm
1
The mistake warns daily record as follows: why?Why, what cause
2009-02-16 20:23:43 SYSTEM 1704 AAVM - scanning warning: x_AavmCheckFileDirectEx: (C:\Windows\TEMP_avast4_\unp150390561.tmp) returning error, 80004004.
DavidR
February 22, 2009, 8:21pm
2
Personally I don’t look inside the log viewer or log files unless I’m experiencing a problem. For example if there is an avast error displayed continually to the screen, as this is more serious.
Where these I would say aren’t displayed to the screen just reporting for whatever reason it couldn’t scan a file that it had unpacked. The C:\Windows\TEMP_avast4_\ folder is where avast unpacks archive file to scan the contents.
Like David said, I won’t worry with this avast temporary file. It’s ok, just verbose of the logs.
system
February 24, 2009, 7:32am
4
I have noticed a similar verbosity from my logs which started after installing the most recent update on 2/20/09. Mine is different, though.
My log is displaying the warnings with the “80004004 ” code like that seen by pajro, but it alternates with error entries under this code: 7C3A497A .
These two events alternate several hundred times a day in my log. Again, this just started after I updated Avast on the 20th.
Event Type: Warning80004004 .
Event Type: Error7C3A497A .
What should I do?
DavidR
February 24, 2009, 1:46pm
5
Nothing, for the reasons I mentioned before.
I only go chasing something that is a problem and that has to be displaying errors to the screen regularly. The avast logs aren’t particularly user friendly (nor is the windows event viewer) and are really more use to one of the Alwil team in the case of any investigation of a problem.
Scanning errors, really are a very minor issue, but they are logged, now if scanning was to regularly stop/hang or crash then that is truly something worthy of investigation.
system
March 4, 2009, 8:25am
6
Personally I don’t look inside the log viewer or log files unless I’m experiencing a problem. For example if there is an avast error displayed continually to the screen, as this is more serious.
Where these I would say aren’t displayed to the screen just reporting for whatever reason it couldn’t scan a file that it had unpacked. The C:\Windows\TEMP_avast4_\ folder is where avast unpacks archive file to scan the contents.
So, thank you for your answer, I am a Chinese user, because no Chinese technical forums, is very difficult to communicate, this is not conducive to such a good software avast at Chinese markets
Vlk
March 4, 2009, 10:32am
7
Please zip the \data\log directory and send it to my email address for further analysis.
Thanks