Avast Initialization Error: RPC error

Avast Free Antivirus / Premium Security
1

Hi all,

I am getting error like following many a times. The error persists even after multiple restarts. can any please tell me ehat exactly is happening. This is not the first time for me to see this error. I am having Windows XP-Pro on PIII, 1.13GHz

"Avast Initialization Error: RPC subsystem failed to start "

Avast user interface do not opens.
About avast dialog box displays VPS database destroyed.

Avast log Viewer recorded following errors

  1. AAVM - initialization error: AavmStart: avworkInitialize failed, 0000A438.
  2. AAVM - initialization error: Unhandled exception in AavmProviderStop, STANDARD.
  3. Internal error has occurred in module aswar scan function failed!, function C0000005.
  4. x_AavmCheckFileDirectEx: avfilesScanReal
    00000005. 0000001E. 00000570.

Windows Error reporting tool recorded following errors:-

  1. AAVM - initialization error: AavmStart: avworkInitialize failed, 0000A438.
  2. Function setifaceUpdatePackages() has failed. Return code is 0x20000004, dwRes is 20000004.
  3. aswServ::AavmStart ERROR…
  4. AAVM: VPS load failed, trying to get a fresh copy…

_____________________________________________________________–

I scanned the drives for errors and repaired avast too, but nothing happened.
After a few restarts now it is behaving normal. But I am sure from these experiences this will happen again soon.

I will be thankful to all for the help.

Thank you.

2

Do you have any other antivirus installed in your system? Did you have in the past?
Any other security programs that could interfere?
Is there any useful information into Control Panel > Administrative Tools > Events, specially ‘Errors’?

Can you try to repair your installation?
Go to Control Panel > Add/Remove programs > avast! antivirus > Remove. Then choose Repair function in the popup window (Repair).
If this does not help, can you uninstall / boot / install / boot again?

3

What version of Avast are you using? I had same issue with 1282 however
1290 sorted it out.