2 errors repeat in warning log

Avast 4.6 Pro and Sygate Pro firewall.

2 errors are repeating many times a day in the warning log:

AAVM-scanning warning:x_AavmCheckFileDirectEx [UnI]: C\Windows$NTUninstall/#######$ and then the names of many different programs - each with it’s own entry as above.

The other repeating warning is:
Function setifaceUpdatePackages() has failed. Return code is 0xC0000142, dwRes is C0000142.
An error has occurred while attempting to update. Please check the logs.

The fact is, I receive automatic updates almost every day according to the notification log.

Both of the above errors occur under both my name (I am the Admin and the only user), and under System.

Help? Are these significant?

Louise

Check this thread out

http://forum.avast.com/index.php?topic=13809.0

They appear to be warnings of a failed update which is a normal occurence if you are offline whan avast tries to update. They are not a problem

I won’t worry that much… Just verbose of the logs.
But if you’re permanently connected to the Internet, check if the error occurs just after the boot.
If you change (or add) AlwaysConnectedWaitSeconds value into the [InetWD] section of avast4.ini file, you could set the number of seconds to wait before attempting to update. The default is 30 but it may not be enough in some DSL systems. In this case, you can try increasing this e.g. to 60 (1 minute). That should be enough. More details here: http://forum.avast.com/index.php?board=2;action=display;threadid=1647

Thanks for your responses.
The line is my avast4.ini file reads:

assumealwaysconnected=0
[Quick]

Should I just change that to, say, 20 - so it will wait 20 seconds?

Or should I add the line suggested (AlwaysConnectedWaitSeconds[b] value into the [b][InetWD]

Any ideas why so many of the $NTinstall etc. etc. files can’t be scanned? This happens during a regular scan but also happened during an at boot scan.

Thanks again.

Louise

I did run a boot time scan and didn’t receive any errors. Can it scan those files

You should add the line suggested:
AlwaysConnectedWaitSeconds=60
or =30 into the [InetWD] section.

OK - all done. I’ll check the logs and see if that took care of it.

Thanks.

Louise