Should there be instances where avast can’t update, corrupt setup, etc. it is possible to download the emergency updater to resolve the issue. But for the most part this check will find no emergency update present, so should be an exception rather than the rule, that is why it shouldn’t be there long.

If I’m very quick I can open the task manager and see it there, for me it is usually only there for a few seconds and you can see my XP system spec in my signature. As I said I don’t know if the act of having blocked it may well keep it hanging around trying to check.

To me it sounds like your system could do with delaying the auto update check and leave the emergency update check alone.

Delay Auto Update - In avast8 you need to edit (using notepad) avast5.ini the [InetWD] section of the, C:\Documents and Settings\All Users\Application Data\AVAST Software\Avast\avast5.ini (XP file location)

  • Broadband connections, add this line:
    AlwaysConnectedWaitSeconds=300 and
    AssumeAlwaysConnected=1 if not present (or edit AssumeAlwaysConnected=0 to AssumeAlwaysConnected=1)
[InetWD] AssumeAlwaysConnected=1 AlwaysConnectedWaitSeconds=300
When complete save the changes, avast's self-defence module will ask for confirmation, etc. answer Yes. You can extend this duration if required.

@@@@
This would save resources close to boot and the emergency update check shouldn’t be such an additional issue.

####
Whilst the disabling of the avast self-defence modules allows you to stop the process, it doesn’t resolve the problem as it is likely to be back again on boot. Once you enable it again it will be back and leaving the self-defence module off leaves avast at risk of being disabled by malware.