Startup delay

[jmd]

I've also stop the exchange/outlook service, I've copied both file (new dll and sum) and after I reboot, AVAST install the old dll file automatically.
I really don't understand what happen?
What can I do to stop this starup delay problem?

[bob3160]

jmd
Welcome to the forum.
Please help us help you.
What version of Avast! are you using
What vps version?
What OS?
What exactly is the problem?
etc. etc.
The more information you can supply, the easier it is to help.
Remember, we aren't sitting in front of your computer.

To disable service, go to add/remove select avast! and then choose change

[jmd]

OS : Win2k PRO SP4
Avast : 4.5.561
VSP : 0503-0
Firewall : Zone Alarm
PC : AMD ATHLON 2600 - 512 Mb RAM
Connection : ADSL
Mail : MS OUTLOOK
Problem : When I start the PC, there´s a red circle on avast! a-ball icon in  system tray and when I click on it, the error message appears saying "the AAVM subsystem detected a RPC error" and it's impossible to start any software.
My PC is frozen. Impossible to work.
I must wait 4 to 5 minutes before the red circle disepear and allows me to work.
I've had the same problem with version 4.5.549 solved by 2 files downloaded from the message of Vlk "Reply #18 on: December 09, 2004, 06:33:19 PM".
But now no success with this solution.

Sorry for my english but I'm Belgian and I don't pratice english everyday.
Thank you for your help.

[siteguru]

I am very surprised by the tone of the answer jmd was given. The problem he described is exactly the problem I have now (with 4.5.561) and is exactly the same as the problem to which VLK gave a temporary solution for 4.5.549! A bit of time reading this thread (i.e. less than the time it took to write the reply) would have given this information very clearly.

It seems to me that the issue that VLK's "patch" resolved has not been addressed in the 4.5.561 update, so the question remains - when will this issue be resolved once and for all? This has been doing the rounds for a few MONTHS now - why miss the opportunity in the 4.5.561 update to fix this problem?

[Lisandro]

Problem : When I start the PC, there´s a red circle on avast! a-ball icon in  system tray and when I click on it, the error message appears saying "the AAVM subsystem detected a RPC error" and it's impossible to start any software. My PC is frozen. Impossible to work. I must wait 4 to 5 minutes before the red circle disepear and allows me to work.

This is a tipical RPC error.
RPC error is generally related to other antivirus present or, at least, firewall blocking. Do you use a firewall? Which one?

Anyway, RPC error is most likely correct by this procedure:
Go to Control Panel > Add/Remove programs > avast! antivirus > Remove
Then choose Repair function in the pop up window (Repair).

Take a look into Administrative Tools > Services
and see how the three avast services are set to start (automatically or manual).

[alphanumeric]

Before upgrading to 4.5.561, I had used the patch above to fix this startup delay problem on my Win2K machine.  With the upgrade, the patch will only persist through to the next boot. Avast will immediately say a system reboot is necessary. It then replaces the modified Aavm4h.dll file and the startup delay returns.  Any suggestions as to what to do about this?   
 

[TourGuide]

Hi everyone,

I fixed my startup delay (with the accompanying RPC error) problem for Avast 4.5.561.  In my case, the problem was caused by Task Scheduler beating the Avast! Antivirus service (ashServ.exe) to gaining RPC access, thus causing Avast to report RPC error until Task Scheduler is finished which whatever it's doing with RPC.  To fix this, I made Task Scheduler wait until ashServ.exe is finished with RPC before it start using it.  This is how I did it:

1) Open Regedit & go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Schedule.

2) You should see the value DependOnService with type REG_MULTI_SZ and data RpcSs.  Right-click on DependOnService & select Modify.  On a separate line in the Value Data box (right under RpcSs), enter "avast! Antivirus" (without the quotes).
Press OK & exit Regedit.

3) Reboot & if your case is similar to mine, that's it!  You should see the "a" icon in the system tray spinning right away after showing up. HTH 

[Vlk]

Is this Win2K? On a machine with MS Outlook installed?

Then two worarounds (both functional) are discussed here: http://forum.avast.com/index.php?board=2;action=display;threadid=9435;start=msg79382#msg79382

[alphanumeric]

Is this Win2K? On a machine with MS Outlook installed?

Then two workarounds (both functional) are discussed here: http://forum.avast.com/index.php?board=2;action=display;threadid=9435;start=msg79382#msg79382

In my case it's Windows 2000 Pro sp4 and office 2003 sp1. I used this patch found in this thread to fix the delay.

OK, I've prepared a patch that will avoid the initialization of the MAPI modules. That should solve the startup timeout issue for most folks.

How to install:

1. Kill all avast components
2. Copy the following files to the avast folder
http://www2.asw.cz/~vlk/Aavm4h.dll
http://www2.asw.cz/~vlk/Aavm4h.dll.sum
(overwrite the existing version of aavm4h.dll; thanks to step 1. it should not be locked) (the .sum file is a text file so instead of clicking on it, right-click it and select Save As..., otherwise it will display in the browser window as text instead)
3. Reboot the machine and see if it helps.

This assumes you have the latest version of avast installed (4.5.549).

I believe you said it would be included in the next version, however after updating to 4.5.561 the delay has returned. With the upgrade, the patch will only persist through to the next boot. Avast will immediately say a system reboot is necessary. It then replaces the modified Aavm4h.dll file and the startup delay returns. Could you please tell me what the other fix is?

[Vlk]

You need to redownload the .sum file. It has been updated for the 561 build recently (in avast, the sum (patch-aproving) files hold version info - and the original sum file was created for build 549. All files without a sum file [or with an invalid one] are automatically replaced by the authorized version - this is to prevent malware from tampering with the program binaries).

BTW build 561 was not really a new build - it was a tiny, emergency update that solved a really bad problem with license keys generated in year 2005 (basically, all installs of v549 done after the New Year's Eve had exactly 0 day trial period instead of the regular 60 days )

Cheers
Vlk

[alphanumeric]

Ok, thankyou I didn't realize the files were updated. I just tried it and it looks like it worked. I did download the files again before my last post, but it looks like the sum file got saved as aavm4h.dll.sum.txt. I didn't notice and ended up still using the old file. Doah.

[TourGuide]

Is this Win2K? On a machine with MS Outlook installed?

Then two worarounds (both functional) are discussed here: http://forum.avast.com/index.php?board=2;action=display;threadid=9435;start=msg79382#msg79382

My apology.  I neglected to mention that my machine is running XP Pro (SP2) with Outlook 2003.

[jmd]

It's OK for me.
The solution with Dllpath = "_mapi32.dll" in registry solve the problem.


Thank you very much

[Vlk]

Just make sure to put the original value back after the next avast program update - it's really worth doing so as the DllPath hack may negatively influence some 3rd party apps (such as PDA sync suites).

thanks
Vlk