Avast WEBforum

Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: schar07 on December 04, 2004, 10:35:35 PM

Title: Startup delay
Post by: schar07 on December 04, 2004, 10:35:35 PM
Hi,

i have W2K Pro latest Win Update.

Avast 4.1 was running great, also with Kerio Pers. FW.

Avast 4.5 has always taken about 30 secs to finish startup after login, but moving from 4.5.523 to 4.5.549 increased the delay up to 3-4 min.! The notorius red interdiction sign on its systray icon is visible and most of other processes get stuck in the meanwhile. Clicking it shows the classic "The AAVM subsystem detected a RPC error" popup.

At the same time a warning is logged in the App Log (WMI ADAP was unable to process the RemoteAccess performance library due to a time violation in the open function), an error is logged in the Sys Log (The avast! Antivirus service hung on starting) and the Avast Antivirus service shows up as "starting" in the Services MMC snapin.

Pls note that i already tried:
- repair installation
- remove/reboot/reinstall/reboot/update/reboot
- remove Kerio 4.1(2)

and verified that RPC services are running fine.

Could somebody gimme some other ideas pls?

Thank you,
Schar07
Title: Re:Startup delay
Post by: DukeNukem on December 04, 2004, 10:52:10 PM
I had win2k installed on my pc a few days ago and was experiencing the exact same problem with 4.5 home ed

Perhaps its a bug??

Title: Re:Startup delay
Post by: Lisandro on December 05, 2004, 04:56:27 AM
and verified that RPC services are running fine.

Sure they will... you won't even start Windows without this service  ;D

Do you have any other antivirus installed in your computer?
Did you have in the past? Which one?
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).

If this does not help, can you uninstall / boot / install / boot again?
Title: Re:Startup delay
Post by: Lisandro on December 05, 2004, 04:57:07 AM
Perhaps its a bug??

No, it's a problem on your computer or on your avast installation...  :'(
Title: Re:Startup delay
Post by: techie101returns on December 05, 2004, 05:26:51 AM
schar,

Try one of these links.  I believe that the first link should solve your problem.

http://support.microsoft.com/default.aspx?scid=kb;en-us;266416  (http://support.microsoft.com/default.aspx?scid=kb;en-us;266416)

also..

http://support.microsoft.com/default.aspx?scid=kb;en-us;259796  (http://support.microsoft.com/default.aspx?scid=kb;en-us;259796)

Good luck.
Title: Re:Startup delay
Post by: schar07 on December 06, 2004, 12:22:25 PM
Hi,

Techie101,
thanks for suggestion. I Set PerfDisk and RemoteAccess Performance Counters to disable and now i no longer have those warnings in the logs. It means they weren't related to Avast.

Technical,
Repair does not work, neither does Uninstall/Reboot/Install/Reboot, i tried several times.

I had PC Cillin 2002, then moved to Avast 4.1 and so forth. I have cleaned disk and registry a long ago, though, and Avast was doing great.
I have Kerio Personal Firewall 4.1(2), but it is not the issue (see below).
I do have Norton SystemWorks 2004, Norton Utilities 17.0.0.82 and Norton Cleansweep 8.0.0.79 but no Norton AV, if it matters.
I am always logged-in as Administrator.
I also used Dependency Walker to analyze ashserv.exe: no suspect missing functions or libraries, of course.

OK, let's try again.

I uninstalled Avast (and Kerio), cleaned HD and Registry with tool from Alwil (and instructions from Kerio website FAQ) and manually, removing also the relevant LEGACY_* protected keys. Of course with reboot after every step.

Then i started installing a copy of Avast 4.1: same issue.
This means something happened to my W2K installation. However Avast is the only program to have issues, and if you wait long enough .. it works great.

Avast is simply waiting for a timeout, somewhere ...

4.1 up to 4.5.523 do show 1:37 delay in the System Log between these 2 events:
Information - eventlog - Microsoft (R) Windows 2000 (R) 5.0 2195 Service Pack 4 Uniprocessor Free.
Error - Service Control Manager - The avast! Antivirus service hung on starting.

4.5.549 delay is 4:34.

After 6 seconds all hung startup processes have loaded, and Avast tray icon is active and working with no further issues at all until next reboot.
An example of process waiting for Avast is the 2nd User-owned kpf4gui.exe (while kpfss.exe and System-owned kpf4gui.exe start flawlessly), but there are other programs that will wait if i run them while Avast is hung.

All delays are very consistent.

So Avast is somewhat guilty, here: what did change between 523 and 549?? Answer to this could lead to issue solution.

Oh, yes: i find quite funny that ashserv.exe stays "starting" for so long ... and right after logging the error in the System Log it moves to "started" and works flawlessly :-)

Schar07
Title: Re:Startup delay
Post by: Eddy on December 06, 2004, 12:31:45 PM
There is a util with which you can manage Windows boot options and the sequence in which way applications are loaded at boot time. I can't remember the name and don't know if it will work with 2k, but give it a try. It is mentioned in several threads here.
Title: Re:Startup delay
Post by: Lisandro on December 06, 2004, 02:02:05 PM
There is a util with which you can manage Windows boot options and the sequence in which way applications are loaded at boot time. I can't remember the name and don't know if it will work with 2k, but give it a try. It is mentioned in several threads here.

It is Startup Delayer: http://www.r2.com.au/downloads/files

Anyway, I think Alwil team should make some tests with the compatibility with Kerio Firewall. Maybe some 'extra' update is needed for it (as it was for Norton and McAffee firewalls...).
Title: Re:Startup delay
Post by: DukeNukem on December 06, 2004, 02:26:15 PM

Information - eventlog - Microsoft (R) Windows 2000 (R) 5.0 2195 Service Pack 4 Uniprocessor Free.
Error - Service Control Manager - The avast! Antivirus service hung on starting.


I have done 4 clean re installs of 2k and still get this error message.

Each time all i had installed was nforce system drivers and display drivers, no other software.

On each reboot once I was at the desktop you cant do anything  for about 3 mins until avast has started.

I will try win2k and avast on a completely different PC and post back my results.

Title: Re:Startup delay
Post by: schar07 on December 07, 2004, 12:24:52 AM
Anyway, I think Alwil team should make some tests with the compatibility with Kerio Firewall. Maybe some 'extra' update is needed for it (as it was for Norton and McAffee firewalls...).

Actually my tests convinced me that Kerio is not the bad boy here, see prev. post.

Guys,

I tried several startup tools one after the other, like StartupFaster, NitroBOOT, Startup Guru, Startup Faster! 2004 and Startup Delayer.

All of them focus on startup programs launched by registry keys or startup group, and none of them allows to control the services load order neither to put some checkpoints/breaks within the boot sequence (if you are aware of such a tool let me know, please).

Here ashserv.exe is the problem, unfortunately, and it starts far earlier.

The only dependency it has got is RPC service (which has none itself). So with Process Explorer i got the PID of the svchost -k rpcss instance and confirmed that when Avast starts the RPC service is already started and running:

- RPC = 456
- aswUpdSv = 532
- ashserv = 548
- ashDisp = 1252

1st startup program has PID = 1076, just to give you the idea (well, of course supposing that greater PID means more recent process...mmhhh)

Great, so why the hell is Avast hanging for so long???

Thanks all in the meanwhile,
Schar07
Title: Re:Startup delay
Post by: Vlk on December 07, 2004, 02:24:18 AM
Hi, let me ask a question: do you have Outlook (I don't mean Outlook Express, I mean the regular Outlook) installed? :)
Title: Re:Startup delay
Post by: chips on December 07, 2004, 01:11:53 PM
Hello I have Windows XP with Service pack 2.

I have the same problem. Startup with version  4.5.549 is taking alot more time. Avast stucks for a minute(avast icon is there, but protection is disabled) and all other processes don't load either at the same time. I don't have Kerio and I have installed Outlook, but I don't configured that one and it's not my standard client.
Title: Re:Startup delay
Post by: schar07 on December 07, 2004, 02:58:28 PM
Hi, let me ask a question: do you have Outlook (I don't mean Outlook Express, I mean the regular Outlook) installed? :)

Yes Vlk,

Outlook 2003, installed and default client. And if it matters ....
C:\Program Files\Common Files\SYSTEM\MSMAPI\1033\MAPIR.DLL
is version 11.0.6355.0.

I attached the WinDbg debugger to ashserv.exe for Avast 4.5.523 and 4.5.549: i attach the debugs one by one, you can find where it stops loading looking for my comments, between "!!!!!".
Title: Re:Startup delay
Post by: schar07 on December 07, 2004, 02:59:25 PM
----- 4.5.523 -----
Symbol search path is: c:\temp

Microsoft (R) Windows Debugger  Version 6.3.0017.0
Copyright (c) Microsoft Corporation. All rights reserved.

CommandLine: "C:\Network\Avast\ashServ.exe"
Symbol search path is: c:\temp
Executable search path is:
ModLoad: 00400000 00416000   ashServ.exe
ModLoad: 77f80000 77ffd000   ntdll.dll
ModLoad: 77d30000 77da1000   C:\WINNT\system32\RPCRT4.dll
ModLoad: 7c570000 7c623000   C:\WINNT\system32\KERNEL32.DLL
ModLoad: 7c2d0000 7c332000   C:\WINNT\system32\ADVAPI32.DLL
ModLoad: 64580000 6458c000   C:\Network\Avast\aswAux.dll
ModLoad: 12000000 12103000   C:\Network\Avast\xerces.dll
ModLoad: 77e10000 77e75000   C:\WINNT\system32\USER32.dll
ModLoad: 77f40000 77f7b000   C:\WINNT\system32\GDI32.DLL
ModLoad: 7c340000 7c396000   C:\WINNT\system32\MSVCR71.dll
ModLoad: 7c3a0000 7c41b000   C:\WINNT\system32\MSVCP71.dll
ModLoad: 64080000 640a2000   C:\Network\Avast\aswCmnB.dll
ModLoad: 64000000 6400f000   C:\Network\Avast\aswCmnOS.dll
ModLoad: 75050000 75058000   C:\WINNT\system32\WSOCK32.dll
ModLoad: 75030000 75044000   C:\WINNT\system32\WS2_32.DLL
ModLoad: 78000000 78045000   C:\WINNT\system32\MSVCRT.DLL
ModLoad: 75020000 75028000   C:\WINNT\system32\WS2HELP.DLL
ModLoad: 64280000 64362000   C:\Network\Avast\aswEngin.dll
ModLoad: 782f0000 78535000   C:\WINNT\system32\SHELL32.dll
ModLoad: 63180000 631e9000   C:\WINNT\system32\SHLWAPI.dll
ModLoad: 71710000 71794000   C:\WINNT\system32\COMCTL32.dll
ModLoad: 77a50000 77b3f000   C:\WINNT\system32\ole32.dll
ModLoad: 64200000 64214000   C:\Network\Avast\aswScan.dll
ModLoad: 64100000 64126000   C:\Network\Avast\aswCmnS.dll
ModLoad: 779b0000 77a4b000   C:\WINNT\system32\OLEAUT32.dll
ModLoad: 64500000 64538000   C:\Network\Avast\ashBase.dll
ModLoad: 77820000 77827000   C:\WINNT\system32\VERSION.dll
ModLoad: 759b0000 759b6000   C:\WINNT\system32\LZ32.DLL
ModLoad: 77570000 775a0000   C:\WINNT\system32\WINMM.dll
ModLoad: 64800000 64818000   C:\Network\Avast\ashTask.dll
ModLoad: 64400000 64409000   C:\Network\Avast\aswInteg.dll
ModLoad: 64a00000 64a07000   C:\Network\Avast\aswIdle.dll
ModLoad: 65000000 65029000   C:\Network\Avast\Aavm4h.dll
ModLoad: 65100000 65108000   C:\Network\Avast\AavmRpch.dll
(22c.228): Break instruction exception - code 80000003 (first chance)
eax=00000000 ebx=00131f04 ecx=00000009 edx=00000000 esi=7ffdf000 edi=00131f70
eip=77f813b1 esp=0012f984 ebp=0012fc98 iopl=0         nv up ei pl nz na pe nc
cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00000202
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntdll.dll -
ntdll!DbgBreakPoint:
77f813b1 cc               int     3
0:000> g
ModLoad: 75e60000 75e7a000   C:\WINNT\system32\IMM32.DLL
ModLoad: 10000000 1001b000   C:\WINNT\system32\apitrap.dll
ModLoad: 690a0000 690ab000   C:\WINNT\system32\psapi.dll
ModLoad: 759c0000 759c7000   C:\WINNT\system32\mmdrv.dll
ModLoad: 75170000 751bf000   C:\WINNT\system32\NetApi32.dll
ModLoad: 00cb0000 00cbf000   C:\WINNT\system32\Secur32.dll
ModLoad: 77bf0000 77c01000   C:\WINNT\system32\NTDSAPI.dll
ModLoad: 77980000 779a4000   C:\WINNT\system32\DNSAPI.DLL
ModLoad: 77950000 7797a000   C:\WINNT\system32\WLDAP32.DLL
ModLoad: 751c0000 751c6000   C:\WINNT\system32\NETRAP.dll
ModLoad: 75150000 7515f000   C:\WINNT\system32\SAMLIB.dll
(22c.228): Unknown exception - code 000006b5 (first chance)
(22c.228): Unknown exception - code 000006b5 (first chance)
ModLoad: 66080000 6608e000   C:\Network\Avast\English\Base.dll
ModLoad: 66100000 66351000   C:\Network\Avast\English\Lang.dll
ModLoad: 7c140000 7c243000   C:\WINNT\system32\MFC71.DLL
ModLoad: 5d360000 5d36e000   C:\WINNT\system32\MFC71ENU.DLL
ModLoad: 6c920000 6c941000   C:\WINNT\system32\mapi32.dll
ModLoad: 03350000 03554000   C:\WINNT\system32\MSI.DLL
ModLoad: 03350000 03554000   C:\WINNT\system32\MSI.DLL
ModLoad: 03350000 03554000   C:\WINNT\system32\MSI.DLL
ModLoad: 35f70000 360be000   C:\Program Files\Common Files\SYSTEM\MSMAPI\1033\MSMAPI32.DLL
ModLoad: 03390000 03594000   C:\WINNT\system32\msi.dll
ModLoad: 35e80000 35f40000   C:\Program Files\Common Files\SYSTEM\MSMAPI\1033\MAPIR.DLL
(22c.334): Unknown exception - code 000006b5 (first chance)
(22c.334): Unknown exception - code 000006b5 (first chance)


!!!!!It stops 1 min 37 sec here!!!!!


ModLoad: 03c50000 03cb1000   C:\WINNT\system32\userenv.dll
ModLoad: 03c50000 03c9b000   C:\Network\Avast\UNACEV2.DLL
ModLoad: 75170000 751bf000   C:\WINNT\system32\NetApi32.dll
ModLoad: 364c0000 364cf000   C:\WINNT\system32\Secur32.dll
ModLoad: 77bf0000 77c01000   C:\WINNT\system32\NTDSAPI.dll
ModLoad: 77980000 779a4000   C:\WINNT\system32\DNSAPI.DLL
ModLoad: 77950000 7797a000   C:\WINNT\system32\WLDAP32.DLL
ModLoad: 751c0000 751c6000   C:\WINNT\system32\NETRAP.dll
ModLoad: 75150000 7515f000   C:\WINNT\system32\SAMLIB.dll
ModLoad: 65980000 6598b000   C:\Network\Avast\AhResNS.dll
ModLoad: 65280000 65289000   C:\Network\Avast\AhResOut.dll
ModLoad: 658c0000 658c9000   C:\Network\Avast\ahResP2P.dll
ModLoad: 65180000 6518c000   C:\Network\Avast\AhResStd.dll
ModLoad: 64880000 6488d000   C:\Network\Avast\ashSODBC.dll
ModLoad: 1f7c0000 1f7f4000   C:\WINNT\system32\ODBC32.dll
ModLoad: 76b30000 76b6e000   C:\WINNT\system32\comdlg32.dll
ModLoad: 1f900000 1f916000   C:\WINNT\system32\odbcint.dll
ModLoad: 1f920000 1f93a000   C:\WINNT\system32\ODBCCP32.dll
ModLoad: 1f940000 1f982000   C:\WINNT\System32\odbcjt32.dll
ModLoad: 1b000000 1b170000   C:\WINNT\System32\msjet40.dll
ModLoad: 1b5d0000 1b665000   C:\WINNT\System32\mswstr10.dll
ModLoad: 013b0000 013be000   C:\WINNT\System32\odbcji32.dll
ModLoad: 013c0000 013cd000   C:\WINNT\System32\msjter40.dll
ModLoad: 013d0000 013f6000   C:\WINNT\System32\MSJINT40.DLL
(22c.334): C++ EH exception - code e06d7363 (first chance)
(22c.334): C++ EH exception - code e06d7363 (first chance)
ModLoad: 775a0000 77630000   C:\WINNT\system32\CLBCATQ.DLL
ModLoad: 1b810000 1b84a000   C:\WINNT\System32\msjtes40.dll
ModLoad: 0f9a0000 0f9ab000   C:\WINNT\system32\VBAJET32.DLL
ModLoad: 0f9c0000 0fa22000   C:\WINNT\system32\expsrv.dll
(22c.334): C++ EH exception - code e06d7363 (first chance)
(22c.334): C++ EH exception - code e06d7363 (first chance)
(22c.334): C++ EH exception - code e06d7363 (first chance)
(22c.334): C++ EH exception - code e06d7363 (first chance)
(22c.56c): C++ EH exception - code e06d7363 (first chance)
ModLoad: 774e0000 77513000   C:\WINNT\system32\Rasapi32.dll
ModLoad: 774c0000 774d1000   C:\WINNT\system32\RASMAN.DLL
ModLoad: 77530000 77552000   C:\WINNT\system32\TAPI32.DLL
ModLoad: 77830000 7783e000   C:\WINNT\system32\RTUTILS.DLL
ModLoad: 77520000 77525000   C:\WINNT\system32\ICMP.DLL
ModLoad: 782c0000 782cc000   C:\WINNT\System32\rnr20.dll
ModLoad: 77340000 77353000   C:\WINNT\system32\iphlpapi.dll
ModLoad: 77320000 77337000   C:\WINNT\system32\MPRAPI.DLL
ModLoad: 773b0000 773df000   C:\WINNT\system32\ACTIVEDS.DLL
ModLoad: 77380000 773a3000   C:\WINNT\system32\ADSLDPC.DLL
ModLoad: 77880000 7790e000   C:\WINNT\system32\SETUPAPI.DLL
ModLoad: 09770000 097d1000   C:\WINNT\system32\USERENV.DLL
ModLoad: 77360000 77379000   C:\WINNT\system32\DHCPCSVC.DLL
ModLoad: 777e0000 777e8000   C:\WINNT\System32\winrnr.dll
ModLoad: 777f0000 777f5000   C:\WINNT\system32\rasadhlp.dll
ModLoad: 09800000 09817000   C:\Network\Avast\Setup\SetIFace.dll
ModLoad: 09930000 09947000   C:\Network\Avast\Setup\SetIFace.dll
ModLoad: 09930000 09947000   C:\Network\Avast\Setup\SetIFace.dll
Title: Re:Startup delay
Post by: schar07 on December 07, 2004, 03:00:17 PM
----- 4.5.549 -----
Symbol search path is: c:\temp

Microsoft (R) Windows Debugger  Version 6.3.0017.0
Copyright (c) Microsoft Corporation. All rights reserved.

CommandLine: "C:\Network\Avast\ashServ.exe"
Symbol search path is: c:\temp
Executable search path is:
ModLoad: 00400000 00416000   ashServ.exe
ModLoad: 77f80000 77ffd000   ntdll.dll
ModLoad: 77d30000 77da1000   C:\WINNT\system32\RPCRT4.dll
ModLoad: 7c570000 7c623000   C:\WINNT\system32\KERNEL32.DLL
ModLoad: 7c2d0000 7c332000   C:\WINNT\system32\ADVAPI32.DLL
ModLoad: 64580000 6458c000   C:\Network\Avast\aswAux.dll
ModLoad: 12000000 12103000   C:\Network\Avast\xerces.dll
ModLoad: 77e10000 77e75000   C:\WINNT\system32\USER32.dll
ModLoad: 77f40000 77f7b000   C:\WINNT\system32\GDI32.DLL
ModLoad: 7c340000 7c396000   C:\WINNT\system32\MSVCR71.dll
ModLoad: 7c3a0000 7c41b000   C:\WINNT\system32\MSVCP71.dll
ModLoad: 64080000 640a2000   C:\Network\Avast\aswCmnB.dll
ModLoad: 64000000 6400f000   C:\Network\Avast\aswCmnOS.dll
ModLoad: 75050000 75058000   C:\WINNT\system32\WSOCK32.dll
ModLoad: 75030000 75044000   C:\WINNT\system32\WS2_32.DLL
ModLoad: 78000000 78045000   C:\WINNT\system32\MSVCRT.DLL
ModLoad: 75020000 75028000   C:\WINNT\system32\WS2HELP.DLL
ModLoad: 64280000 64362000   C:\Network\Avast\aswEngin.dll
ModLoad: 782f0000 78535000   C:\WINNT\system32\SHELL32.dll
ModLoad: 63180000 631e9000   C:\WINNT\system32\SHLWAPI.dll
ModLoad: 71710000 71794000   C:\WINNT\system32\COMCTL32.dll
ModLoad: 77a50000 77b3f000   C:\WINNT\system32\ole32.dll
ModLoad: 64200000 64214000   C:\Network\Avast\aswScan.dll
ModLoad: 64100000 64126000   C:\Network\Avast\aswCmnS.dll
ModLoad: 779b0000 77a4b000   C:\WINNT\system32\OLEAUT32.dll
ModLoad: 64500000 64538000   C:\Network\Avast\ashBase.dll
ModLoad: 77820000 77827000   C:\WINNT\system32\VERSION.dll
ModLoad: 759b0000 759b6000   C:\WINNT\system32\LZ32.DLL
ModLoad: 77570000 775a0000   C:\WINNT\system32\WINMM.dll
ModLoad: 64800000 64818000   C:\Network\Avast\ashTask.dll
ModLoad: 64400000 64409000   C:\Network\Avast\aswInteg.dll
ModLoad: 64a00000 64a07000   C:\Network\Avast\aswIdle.dll
ModLoad: 65000000 6502a000   C:\Network\Avast\Aavm4h.dll
ModLoad: 65100000 65108000   C:\Network\Avast\AavmRpch.dll
(22c.228): Break instruction exception - code 80000003 (first chance)
eax=00000000 ebx=00131f04 ecx=00000009 edx=00000000 esi=7ffdf000 edi=00131f70
eip=77f813b1 esp=0012f984 ebp=0012fc98 iopl=0         nv up ei pl nz na pe nc
cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00000202
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntdll.dll -
ntdll!DbgBreakPoint:
77f813b1 cc               int     3
0:000> g
ModLoad: 75e60000 75e7a000   C:\WINNT\system32\IMM32.DLL
ModLoad: 10000000 1001b000   C:\WINNT\system32\apitrap.dll
ModLoad: 690a0000 690ab000   C:\WINNT\system32\psapi.dll
ModLoad: 759c0000 759c7000   C:\WINNT\system32\mmdrv.dll
ModLoad: 75170000 751bf000   C:\WINNT\system32\NetApi32.dll
ModLoad: 00cb0000 00cbf000   C:\WINNT\system32\Secur32.dll
ModLoad: 77bf0000 77c01000   C:\WINNT\system32\NTDSAPI.dll
ModLoad: 77980000 779a4000   C:\WINNT\system32\DNSAPI.DLL
ModLoad: 77950000 7797a000   C:\WINNT\system32\WLDAP32.DLL
ModLoad: 751c0000 751c6000   C:\WINNT\system32\NETRAP.dll
ModLoad: 75150000 7515f000   C:\WINNT\system32\SAMLIB.dll
(22c.228): Unknown exception - code 000006b5 (first chance)
(22c.228): Unknown exception - code 000006b5 (first chance)
ModLoad: 66080000 6608e000   C:\Network\Avast\English\Base.dll
ModLoad: 66100000 66351000   C:\Network\Avast\English\Lang.dll
ModLoad: 7c140000 7c243000   C:\WINNT\system32\MFC71.DLL
ModLoad: 5d360000 5d36e000   C:\WINNT\system32\MFC71ENU.DLL
ModLoad: 6c920000 6c941000   C:\WINNT\system32\mapi32.dll
ModLoad: 03350000 03554000   C:\WINNT\system32\MSI.DLL
ModLoad: 03350000 03554000   C:\WINNT\system32\MSI.DLL
ModLoad: 03350000 03554000   C:\WINNT\system32\MSI.DLL
ModLoad: 35f70000 360be000   C:\Program Files\Common Files\SYSTEM\MSMAPI\1033\MSMAPI32.DLL
ModLoad: 03390000 03594000   C:\WINNT\system32\msi.dll
ModLoad: 35e80000 35f40000   C:\Program Files\Common Files\SYSTEM\MSMAPI\1033\MAPIR.DLL
(22c.2f4): Unknown exception - code 000006b5 (first chance)
(22c.2f4): Unknown exception - code 000006b5 (first chance)


!!!!!It stops 4 min 34 sec here!!!!!


ModLoad: 03c50000 03cb1000   C:\WINNT\system32\userenv.dll
ModLoad: 03c50000 03c9b000   C:\Network\Avast\UNACEV2.DLL
ModLoad: 75170000 751bf000   C:\WINNT\system32\NetApi32.dll
ModLoad: 364c0000 364cf000   C:\WINNT\system32\Secur32.dll
ModLoad: 77bf0000 77c01000   C:\WINNT\system32\NTDSAPI.dll
ModLoad: 77980000 779a4000   C:\WINNT\system32\DNSAPI.DLL
ModLoad: 77950000 7797a000   C:\WINNT\system32\WLDAP32.DLL
ModLoad: 751c0000 751c6000   C:\WINNT\system32\NETRAP.dll
ModLoad: 75150000 7515f000   C:\WINNT\system32\SAMLIB.dll
ModLoad: 65980000 6598b000   C:\Network\Avast\AhResNS.dll
ModLoad: 65280000 65289000   C:\Network\Avast\AhResOut.dll
ModLoad: 658c0000 658c9000   C:\Network\Avast\ahResP2P.dll
ModLoad: 65180000 6518c000   C:\Network\Avast\AhResStd.dll
ModLoad: 64880000 6488d000   C:\Network\Avast\ashSODBC.dll
ModLoad: 1f7c0000 1f7f4000   C:\WINNT\system32\ODBC32.dll
ModLoad: 76b30000 76b6e000   C:\WINNT\system32\comdlg32.dll
ModLoad: 1f900000 1f916000   C:\WINNT\system32\odbcint.dll
ModLoad: 1f920000 1f93a000   C:\WINNT\system32\ODBCCP32.dll
ModLoad: 1f940000 1f982000   C:\WINNT\System32\odbcjt32.dll
ModLoad: 1b000000 1b170000   C:\WINNT\System32\msjet40.dll
ModLoad: 1b5d0000 1b665000   C:\WINNT\System32\mswstr10.dll
ModLoad: 013b0000 013be000   C:\WINNT\System32\odbcji32.dll
ModLoad: 013c0000 013cd000   C:\WINNT\System32\msjter40.dll
ModLoad: 013d0000 013f6000   C:\WINNT\System32\MSJINT40.DLL
(22c.2f4): C++ EH exception - code e06d7363 (first chance)
(22c.2f4): C++ EH exception - code e06d7363 (first chance)
ModLoad: 775a0000 77630000   C:\WINNT\system32\CLBCATQ.DLL
ModLoad: 1b810000 1b84a000   C:\WINNT\System32\msjtes40.dll
ModLoad: 0f9a0000 0f9ab000   C:\WINNT\system32\VBAJET32.DLL
ModLoad: 0f9c0000 0fa22000   C:\WINNT\system32\expsrv.dll
(22c.2f4): C++ EH exception - code e06d7363 (first chance)
(22c.2f4): C++ EH exception - code e06d7363 (first chance)
(22c.2f4): C++ EH exception - code e06d7363 (first chance)
(22c.2f4): C++ EH exception - code e06d7363 (first chance)
(22c.2f4): C++ EH exception - code e06d7363 (first chance)
(22c.2f4): C++ EH exception - code e06d7363 (first chance)
(22c.2f4): C++ EH exception - code e06d7363 (first chance)
(22c.2f4): C++ EH exception - code e06d7363 (first chance)
(22c.588): C++ EH exception - code e06d7363 (first chance)
ModLoad: 774e0000 77513000   C:\WINNT\system32\Rasapi32.dll
ModLoad: 774c0000 774d1000   C:\WINNT\system32\RASMAN.DLL
ModLoad: 77530000 77552000   C:\WINNT\system32\TAPI32.DLL
ModLoad: 77830000 7783e000   C:\WINNT\system32\RTUTILS.DLL
ModLoad: 77520000 77525000   C:\WINNT\system32\ICMP.DLL
ModLoad: 782c0000 782cc000   C:\WINNT\System32\rnr20.dll
ModLoad: 77340000 77353000   C:\WINNT\system32\iphlpapi.dll
ModLoad: 77320000 77337000   C:\WINNT\system32\MPRAPI.DLL
ModLoad: 773b0000 773df000   C:\WINNT\system32\ACTIVEDS.DLL
ModLoad: 77380000 773a3000   C:\WINNT\system32\ADSLDPC.DLL
ModLoad: 77880000 7790e000   C:\WINNT\system32\SETUPAPI.DLL
ModLoad: 09770000 097d1000   C:\WINNT\system32\USERENV.DLL
ModLoad: 77360000 77379000   C:\WINNT\system32\DHCPCSVC.DLL
ModLoad: 777e0000 777e8000   C:\WINNT\System32\winrnr.dll
ModLoad: 777f0000 777f5000   C:\WINNT\system32\rasadhlp.dll
ModLoad: 09800000 09817000   C:\Network\Avast\Setup\SetIFace.dll
ModLoad: 09930000 09947000   C:\Network\Avast\Setup\SetIFace.dll
ModLoad: 09930000 09947000   C:\Network\Avast\Setup\SetIFace.dll
Title: Re:Startup delay
Post by: schar07 on December 07, 2004, 03:02:01 PM
So, once more ... M$'s guilt ???  ;)

Many thanks,
Schar07

PS: i'll be away for 2-3 days
Title: Re:Startup delay
Post by: Vlk on December 07, 2004, 05:04:57 PM
I thought so. It must be the initialization of the "MAPI" unpacker. I've seen similar stuff in the past.

There's currently not an easy workaround I'm aware of. Well let me think.....


Avast reads the path to the mapi dll from the following registry location: HKEY_LOCAL_MACHINE\SOFTWARE\Clients\Mail\Microsoft Outlook, value called "DllPath".

If you patch this value (normally i think it's "mapi32.dll", so change it e.g. to "_mapi32.dll" - simply to prevent avast from finding the DLL), it should "fix" the problem.

This change should not affect Outlook in any way but may affect other programs (that work similar to avast) - e.g. some PDA/cellphone synchronization stuff etc...

This is a just a temporary solution. Just make sure to put the original value back after the next avast program update - which will fix the problem by itself. Or, use the Aavm4h.dll patching method described in my next thread below.



Thx Vlk
Title: Re:Startup delay
Post by: Dwarden on December 08, 2004, 02:24:55 AM
are You ATI user using drivers 4.11 or 4.12beta ?

I got this issue with Avast 4.5 since beta and these drivers ...

older Avast and older drivers were ok ....

first i thought its KPF also ... i was wrong ...

i noticed in my case it was Windows Image Acquisition (WIA) what hang ...
setting it to manual mode solved the delay ...

when i was browsing rage3d.net forums i discovered someone posted there about similar issues...

i think it's related somehow to drivers and certain system config / application combination with it ...

this is only brainstorming and maybe helps You to track real source of problems ...
Title: Re:Startup delay
Post by: Vlk on December 09, 2004, 08:33:19 PM
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).


Thanks
Vlk
Title: Re:Startup delay
Post by: schar07 on December 09, 2004, 11:24:34 PM
are You ATI user using drivers 4.11 or 4.12beta ?
Dwarden,

i am an ATI ref driver user indeed, 4.11 and now 4.12beta, but i cannot remember if the issues with Avast started at the same time i upgraded from older release ... however you may be right.

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.

Vlk,

both your solutions (REG_trick/patch) do work indeed, one by one or together, and now i am just using the patch. Will we find this patched DLL in the next release, so?

Thanks for this hotfix,
Schar07
Title: Re:Startup delay
Post by: Vlk on December 10, 2004, 10:47:27 PM
Sure, it will be in the next program release.
Title: Re:Startup delay
Post by: schar07 on December 12, 2004, 03:48:43 PM
Thanks to you for your prompt support here, and to Alwil for this good piece of software.

Regards,
Schar07
Title: Re: Startup delay
Post by: northy84 on January 06, 2005, 11:13:30 PM
i have posted here a question dealing with this topic please look at it if the link works http://forum.avast.com/index.php?topic=9014.30

thanks for any help
Title: Re: Startup delay
Post by: rhammond84 on January 11, 2005, 11:24:41 AM
Before upgrading to 4.5.561, I had used the patch above to fix this startup delay problem (demonstrated on both my Win2K machines).  With the upgrade, the patch will only persist through to the next boot, when Avast automatically updates again and the startup delay returns.  Any suggestions as to what to do about this?
Thanks,
Rich.
Title: Re: Startup delay
Post by: Lisandro on January 11, 2005, 12:00:45 PM
Before upgrading to 4.5.561, I had used the patch above to fix this startup delay problem (demonstrated on both my Win2K machines).  With the upgrade, the patch will only persist through to the next boot, when Avast automatically updates again and the startup delay returns.  Any suggestions as to what to do about this? Thanks, Rich.

Did you use Startup Delayer (http://www.r2.com.au/software.php?page=2&show=startdelay).
I do not understand what are you calling 'patch' here...
Welcome to avast forums...
Title: Re: Startup delay
Post by: rhammond84 on January 11, 2005, 12:07:11 PM
Did you use Startup Delayer (http://www.r2.com.au/software.php?page=2&show=startdelay).
I do not understand what are you calling 'patch' here...

The 'patch' posted above by Vlk (reply #18).  Startup Delayer does not help.
Thanks for your help,
Rich.
Title: Re: Startup delay
Post by: khass on January 12, 2005, 03:08:12 PM
I have the same trable :(

avast! home 4.5.561, win2k sp4 RUS, MS Outlook 2003 RUS

About 3-5 min delay at startup.
Can I use VLK files to fix this problem, or it only for old 549 release?
Title: Re: Startup delay
Post by: jmd on January 12, 2005, 08:53:49 PM
Hello,

Message for Vlk

You wrote that to install the patch for Startup delay, in step one, we must kill all Avast components.
How can I do for killing the components?
Title: Re: Startup delay
Post by: rhammond84 on January 13, 2005, 12:19:16 PM
Any solution to this problem - I thought the patched dll would have been included in the latest release?  It's incredibly frustrating having to go and find something else to do when my PC takes 5 minutes to become usable on startup.
Rich
Title: Re: Startup delay
Post by: khass on January 13, 2005, 01:29:15 PM
I deactivated Exchange plugin of AVAST! and the problem disapeared....but I hope, it will be fix in next releases  ;)
Title: Re: Startup delay
Post by: jmd on January 17, 2005, 08:50:12 PM
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?
Title: Re: Startup delay
Post by: bob3160 on January 17, 2005, 09:11:47 PM
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. ;D

To disable service, go to add/remove select avast! and then choose change
Title: Re: Startup delay
Post by: jmd on January 18, 2005, 07:20:23 PM
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.
Title: Re: Startup delay
Post by: siteguru on January 21, 2005, 10:37:07 PM
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?
Title: Re: Startup delay
Post by: Lisandro on January 22, 2005, 12:19:06 PM
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).
Title: Re: Startup delay
Post by: alphanumeric on January 22, 2005, 03:38:03 PM
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?   :(
 
Title: Re: Startup delay
Post by: TourGuide on January 23, 2005, 02:24:07 PM
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  :)
Title: Re: Startup delay
Post by: Vlk on January 23, 2005, 07:59:04 PM
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
Title: Re: Startup delay
Post by: alphanumeric on January 23, 2005, 08:16:48 PM
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?
Title: Re: Startup delay
Post by: Vlk on January 23, 2005, 09:40:06 PM
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 :) ;D)

Cheers
Vlk
Title: Re: Startup delay
Post by: alphanumeric on January 23, 2005, 11:11:49 PM
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.
Title: Re: Startup delay
Post by: TourGuide on January 24, 2005, 01:55:42 AM
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.
Title: Re: Startup delay
Post by: jmd on January 24, 2005, 08:06:37 PM
It's OK for me.
The solution with Dllpath = "_mapi32.dll" in registry solve the problem.


Thank you very much

Title: Re: Startup delay
Post by: Vlk on January 24, 2005, 10:38:41 PM
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