Avast Warning log

[windward]

I have Avast 4.8 Home edition. I received the following in the warning log. Is this a problem I can fix?
Thanks,
Jim
***
Here is the Avast warning log...
8/31/2009 2:52:08 PM   SYSTEM   432   Function setifaceUpdatePackages() has failed. Return code is 0x2000001A, dwRes is 2000001A. 
8/31/2009 8:12:30 PM   SYSTEM   432   Function setifaceUpdatePackages() has failed. Return code is 0x2000001A, dwRes is 2000001A. 
9/1/2009 8:42:17 AM   SYSTEM   1988   Function setifaceUpdatePackages() has failed. Return code is 0x2000001A, dwRes is 2000001A. 
9/1/2009 1:03:38 PM   SYSTEM   1988   Function setifaceUpdatePackages() has failed. Return code is 0x2000001A, dwRes is 2000001A. 
9/1/2009 2:58:31 PM   SYSTEM   1972   Function setifaceUpdatePackages() has failed. Return code is 0x2000001A, dwRes is 2000001A. 
9/1/2009 7:02:52 PM   SYSTEM   1972   Function setifaceUpdatePackages() has failed. Return code is 0x2000001A, dwRes is 2000001A. 
9/1/2009 11:03:22 PM   SYSTEM   1972   Function setifaceUpdatePackages() has failed. Return code is 0x2000001A, dwRes is 2000001A. 
9/2/2009 7:36:52 AM   SYSTEM   1984   Function setifaceUpdatePackages() has failed. Return code is 0x2000001A, dwRes is 2000001A. 
9/2/2009 8:26:58 AM   HP_Owner   4044   Function setifaceUpdatePackages() has failed. Return code is 0x2000001A, dwRes is 2000001A. 
9/2/2009 2:21:06 PM   SYSTEM   1500   AAVM - scanning warning: x_AavmCheckFileDirectEx [UNI]: C:\Documents and Settings\HP_Owner\Desktop\WindowsXP-KB958644-x86-ENU.exe (C:\Documents and Settings\HP_Owner\Desktop\WindowsXP-KB958644-x86-ENU.exe) returning error, 00000026.

[mkis]

This is a symptom of a problem. If there is a problem. Update packages did not download.

May possibly be just an error - that is, for example, your internet connect may not have been ready, or may have been busy elsewhere. Common examples.

If problem, then error will persist.

[windward]

How does one go about fixing it if it is a problem?

[mkis]

One of the functions they attributed to conficker virus was capability to prevent updates from going through. I would say most that type malware will carry this function, so possibly error (or warning) due to infection. But more details are needed.

Was there initially no problem before error / warning msg began?
If so, what changes have been made since then?

Assume HP_Owner indicates you use HP system. Do or did you have HP printer or scanner connected to your system as well. There is a fix for automatic updates for these kinds of setups. But really need more details.

What service pack do have with your XP? Is it SP3?

[DavidR]

First windows file system error 26 = The specified disk or diskette cannot be accessed, which seems strange though I don't think suspicious. Files that can't be scanned are just that not an indication they are infected, etc. just can't be scanned.

The other (Function setifaceUpdatePackages() has failed. Return code is 0x2000001A, dwRes is 2000001A.) this happens from time to time and there is no one thing it can be pinned down to slow or dropped connection is common. I doubt they are conficker related at all/

I get them regularly and they are just update hiccups, they aren't even hard errors, e.g. displayed to the screen (Red error pop-up about the update failed), so I basically ignore it as avast will try again until it can update.

- Personally I keep my nose out of the logs as for the most part the content is verbose and not to helpful to a user, more so for a developer. Only if I experience a problem with avast or hard errors are displayed to the screen do I look in the logs.
 
So are you getting any errors displayed to the screen or other avast problems ?
 
If not I wouldn't worry about this.

[windward]

Thanks.
My original problem was I deleted a program through add/remove programs and instead of just that program getting deleted, several others got deleted also. I figured I might have a virus. After doing a Hijack this, Malwarebytes, and running Panda ActiveScan 2.0 I am hoping that is no longer a problem.

I do have an HP system and did have an HP scanner a while back. I now have a Epson CX7400 printer/scanner.

I have XP service pack 3.

Thanks again,
Aloha,
Jim

[mkis]

An automatic updates issue seems that Microsoft has only partially fixed. In particular where HP printer / scanner has been connected.

http://ask-leo.com/how_do_i_fix_this_high_cpu_usage_svchost_virus_or_whatever_it_is.html


I used the fix outlined under Another Temporary Solution -- toward the bottom of the page. The fix is 'in the wild' - not certified - so be careful but should be okay. If you try out and this does solve your problem, there will still be entries 4 scanner scattered through Registry, but unless you have very good Registry experience, I would leave them there. There are lot of like-minded entries that can be mistaken 4  scanner device entries.

[DavidR]

Thanks.
My original problem was I deleted a program through add/remove programs and instead of just that program getting deleted, several others got deleted also. I figured I might have a virus. After doing a Hijack this, Malwarebytes, and running Panda ActiveScan 2.0 I am hoping that is no longer a problem.
<snip>

I don't believe you have anything to do other than normal monitoring what is going on with your system if you aren't getting any hard errors displayed.

The PandaActiveScan had in the past the nasty habit of a) dumping files and folders in your system32 folder and b) failing to encrypt its virus signatures so avast can detect them during on-demand scans. There are plenty of other on-line scanners that don't do this - On-line Virus Scanners and other useful Links Security-Ops.eu.tt

[paramedic35]

I do not have the warning log problem, however, I think I may have a trojan. I hope someone can help.
I have not been paying attention but just reakized that I have not been receiving any warnings about programs wanting to access my computer. I thought that everything was working very well. My PC started running slower and running out of virtual memory.
I checked loaded modules and found  "xt1922 by codejock software".
Not recognizing it I Binged it and found info from symantec stating that it is Level 1 trojan known as Lodav.C

I did what they recommended (disable system restore, update virus definitions, scan) Avast had been updated earlier in the day so it stated that it was current. After 2 complete scans no viruses were found but the xt1922 is still present.

Do I have a problem???

[Lisandro]

Difficult to know only by the file name...
Maybe you could upload the file to www.virustotal.com and check if it is really infected.

[paramedic35]

That said that it was OK. So my question is...Why am I not getting any warning messages while I am on the web asking for permission to let a programm access the computer?

[Lisandro]

That said that it was OK. So my question is...Why am I not getting any warning messages while I am on the web asking for permission to let a programm access the computer?

Which is your firewall?

[paramedic35]

windows defender

[Lisandro]

windows defender

It's not a firewall... it's an antispyware tool only.

[mkis]

How does one go about fixing it if it is a problem?

@windward

I'm sorry windward, but in my second post to this thread I was getting your avast log mixed up with automatic updates in general. I think DavidR is probably right, although your error does seem persistent. You could check Windows Eventviewer under Application and System for more information concerning the issue - use the dates and times from your avast log to find the correct events. (EventViewer is found in Adminstrative Tools in the Control Panel).

By conficker type malware I mean most malware from late last year early this year that were attributed and grouped a common character as conficker. One common attribute of the malware was to prevent computers from updating, particularly to security sites and agencies. I still come across this issue, and attempting to manually update from Windows Security Center is often my first test for possibility of infection.

Sorry but I just sorted a computer that had an issue with Windows auto updates and I overlooked that your errors were returned to an avast log. At times I have myself had these messages. Its really a matter of whether the issue goes further than avast updates not completing successfully.