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