Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: RicardoB on September 02, 2006, 05:53:25 PM
-
When my Windows XP with SP2 starts,
Avast takes around 1 (ONE) minute to get ready.
During this time, a red circle appears in the "a" icon and other functions in Windows (like opening a txt file in notepad) don't work properly... so I always have to wait until the red circle dissapears to use the computer.
My computer is a Pentium 4 HT 2.8 Ghz, 1,5 Gb RAM, I don't have any other antivirus...
I have uninstalled and reinstalled Avast but the problem persists.
I know it is not the right behavior because I saw other computers starting avast as soon as Windows starts.
Anyone have an I idea to help me on this?
-
Are you using Automatic IP detection for networking devices (LAN card) ?
This is usually the cause for incredibly long boot and startup times.
-
This computer is at home, if I connect, it connects to the Internet.
It is really configured to automatic detection but I enable and disable my network connection only when I want to use the Internet..
So, I believe it is not the problem because when Windows starts the connetion is disabled. What do you think?
-
Which is your Standard Shield sensitivity level? High or Normal?
Which firewall do you use?
Which programs you have allowed to start automatically with Windows?
-
In Avast, I chose the middle option.
I use only Windows Firewall and Avast.
I avoid setting programs to start automatically.
The program that appear in my Start folder is only the Acrobat Reader. On the sysbar, when Windows starts, there is only the clock, Avast and sound icon.
-
In Avast, I chose the middle option.
Middle? Look at the screenshot, did you click on Details buttom?
Middle seems High, which is not good. The best balance between resources and protection is NORMAL.
I use only Windows Firewall and Avast.
But did you use in the past any antivirus besides avast?
-
I changed it to "Normal" now.
It seems that it loads a bit faster but I still have to wait for more than 30 seconds until avast finish starting (with the same red circle on the icon).
I had Norton last year and I read that it is too heavy and we need an extra tool to remove everything Norton leaves in the computer. I found one "Norton ALL Removal" and then I've installed Avast. (My machine became 3 times faster after that.. hehehe)
Do you think I should try another Norton removal anyway? Any suggestion?
-
I changed it to "Normal" now.
It seems that it loads a bit faster but I still have to wait for more than 30 seconds until avast finish starting (with the same red circle on the icon).
You can TEST if two other settings help or not...
1. Disable scan files on open and created/modified
Boot and analise
2. Disable kernel-mode scanning
Boot and analise
3. Disable Scan dynamic libraries on load
Boot and analise
Do you think I should try another Norton removal anyway? Any suggestion?
It will be good...
Use Symantec removal tool following the three steps defined in the SymNRT (http://service1.symantec.com/SUPPORT/sharedtech.nsf/docid/2006031710323113?Open&src=&docid=2005033108162039&nsf=tsgeninfo.nsf&view=docid&dtype=&prod=&ver=&osv=&osv_lvl=&seg=) tool info.
-
This same problem is happening to me. Avast never used to do this before, but it started one or two months ago. I can't remember changing anything at the time.
Have you had any luck with this?
-
Tech,
I did all that configuration changes and also run the Norton Removal Tool as you suggested.
Unfortunately I still have the same behavior... The red circle for almost one minute.
I don't get why it is happening.
I don't fill my computer with bullshits, I searched for spyware and found nothing.
Everything is normal after Avast starts.
I don't want to have to format my computer and reinstall everything.
Thanks for your help... and do you have another idea?
-
I don't fill my computer with bullshits, I searched for spyware and found nothing.
For any reason, did you change folders icons? Specially, icons of the Start Menu subfolders?
-
I'm on cable and I get the red circle on boot but it doesn't take very long for it to go away. I don't view this as a problem. It takes a moment for Avast to come online along with everything else that is booting up at the same time. Enabling and disabling your connection rather than being online all the time is something that can be selected in the Avast menu settings.
-
Guys, what if you wait for a while (e.g. a minute) before logging on? (i.e. before pressing Ctrl+Alt+Del and typing your username/password). Does it then still take so long for the red circle to go away?
Thanks
Vlk
-
I'd bet it doesn't.
-
Tech,
I moved the "avast Antivirus" folder from the Programs folder to the Accessories subfolder. But I don't see why it would influence.
... and I don't have any Avast icon in the Startup submenu, but it starts automatically. (When I run "msconfig" I see Avast is set to startup)
(just curiosity, I see you have a Brazilian flag in your profile. I'm from São Paulo)
Vlk,
As I use this computer at home, my exclusive use, I set Windows to automatic log on with an administration account so I don't pass through that Ctrl+Alt+Del screen.
I could wait for one minute until Avast finishes starting, but I see that in other computers Avast opens already loaded and running. I'd like to have the same behavior.
-
yea...i experienced this too before...it can really take a long time during rebooting... ???
-
I moved the "avast Antivirus" folder from the Programs folder to the Accessories subfolder. But I don't see why it would influence.
... and I don't have any Avast icon in the Startup submenu, but it starts automatically. (When I run "msconfig" I see Avast is set to startup)
Well, the problem could be that avast needs to scan the files where the icons of all Start Menu are placed (not only avast folder).
It won't help moving the avast links folder to another subdirectory...
As I use this computer at home, my exclusive use, I set Windows to automatic log on with an administration account so I don't pass through that Ctrl+Alt+Del screen.
That is EXACTLY what seems to be happening.
Windows needs to start a lot of services and drivers before you can logon.
Automatically logon bring to you a false impression: the boot time (loading services and drivers) has not finished and you have already start to logon (automatically logon).
What's making the logon slower could be the non-finished boot-time.
Hope I make myself (Vlk and Igor) clear 8)
-
The higher the standard shield sensitivity, the longer the boot as it will scan more files. If you have any other security based programs that also scan on boot, this can cause duplication of scans and also prolong the boot.
I used to have long boot times with earlier versions of avast (much improved in the latest versions) and that was caused by my firewall being very active on boot and standard shield on High, but never once did it result in the red circle.
For me it takes about 25-30 seconds before the log on screen appears, I log on and it takes a further 30 seconds before all boot activity is complete (no avast icon rotating), overall about 1 minute but no red circle.
-
I don't consider it a big deal. I guess I could take the time to review a boot log but I don't think anything is wrong with avast scanning files during boot up while everything else is booting up at the same time. It just takes time. It still doesn't take as as long as a Linux distro to boot up. I'm going to reboot and time the red circle if it appears again....
16 seconds. And the red circle disappears after everything is through booting up. In fact, I don't even think it is slowing down the boot up. The first system tray icon to appear is Avast and the last system tray icon to appear is the firewall and after that the Avast red circle goes away. For appearances sake it appears to be normal. Let me know if I'm incorrect on my assumption.
BTW, I'm using XP with auto logon.
-
My boot takes 30 seconds until the Desktop screen appears and almost ONE minute MORE until Avast run.
So, you think that it is normal?
Well, now I have to check with the people I saw it running right when windows starts and check if they have automatic logon and how long their boot takes.
Did I get it right?
-
Well, you can do several things like scanning your PC with Avast, look to see how many other programs are loading on start up, and so forth. Also, it would help us to know how much random access memory you have installed, your processor type, if DMA is enabled on your hard drive, and examine your boot log. For a benchmark you can unintall Avast and time you entire boot process. For all we know your entire boot process has been 90 seconds or more and the Avast icon is your first indication of such. My first inclination is that you have too much stuff loading on boot and now you have added Avast into the line up. In other words, the red circle in Avast isn't you main problem.
-
Ricardo,
during the one minute when avast is not active, can you check the Task Manager, Processes tab, if there's a process called ashServ.exe? (you can sort the process name column by clicking the header).
Thanks
Vlk
-
Well, I've run that test and ashserv.exe is present. I've determined that the red icon is related to the system boot up. In particular, the cable modem and router coming online. Starting IE during boot up shows a blank browser screen until right after the red circle disappears on the Avast icon at which point IE starts downloading the home page. So, I'm assuming that Avast is going to show that red circle until it has an internet connection. Let me know if this is incorrect.
-
Well,
I have a Pentium 4 HT 2.8 GHz; 1,5GB RAM; 40 GB HD SATA.
I took a Print Screen while the processes were loading...
And also one when the processes were loaded (ALL Process).
I see video card driver, avast, DVD Launcher, VMWare, MS Defender etc.
But the ones that use more memory are
Explorer.EXE;
ashServ.exe;
SVCHOST.EXE;
MsMpEng.exe.
Does it give an idea if there is a problem or it is normal?
-
VMWare
Are you automatically (startup item) loading a virtual machine or just the services?
VMWare is a intense memory user...
-
OK, please dump the ashServ.exe for analysis of where it's stuck.
To do this, download the program http://public.avast.com/~vlk/hangrep.exe , run it, select ashServ.exe in the list of processes, click Save As and save the dump file (please note that this needs to be done WHEN THE PROBLEM IS PRESENT, ie. before the avast tray icon red circle disappears).
When you have the dump, ZIP it and upload it to ftp://ftp.avast.com/incoming (note that you won't have READ access to the ftp site, just write)
Thanks
Vlk
-
Tech,
It is just the VMWare service that is loaded. No virtual machine is started.
-
OK, please dump the ashServ.exe for analysis of where it's stuck.
To do this, download the program http://public.avast.com/~vlk/hangrep.exe , run it, select ashServ.exe in the list of processes, click Save As and save the dump file (please note that this needs to be done WHEN THE PROBLEM IS PRESENT, ie. before the avast tray icon red circle disappears).
When you have the dump, ZIP it and upload it to ftp://ftp.avast.com/incoming (note that you won't have READ access to the ftp site, just write)
Thanks
Vlk
uploaded as CULPEPER*.*
-
Tech, It is just the VMWare service that is loaded. No virtual machine is started.
Ok... no trouble.
But, if you disable automatic logon, and wait 1 minute after booting and before logon, will this happen?
-
Culperer, thanks for that, unfortunately, the file on the ftp site seems to have zero length. Could you please try to upload it once more?
Many thanks
Vlk
-
Culperer, thanks for that, unfortunately, the file on the ftp site seems to have zero length. Could you please try to upload it once more?
Many thanks
Vlk
I keep getting a hangrep failure code 13 and it saves the file with zero length.
-
Hmm, if hangrep doesn't work, try using the command-line version http://public.avast.com/~vlk/userdump.exe . The syntax is
userdump.exe ashServ.exe c:\ashServ.dmp
(producing dump file in the root of C:\ drive) but I guess you have to be quick! ;) ;D
-
Hmm, if hangrep doesn't work, try using the command-line version http://public.avast.com/~vlk/userdump.exe . The syntax is
userdump.exe ashServ.exe c:\ashServ.dmp
(producing dump file in the root of C:\ drive) but I guess you have to be quick! ;) ;D
Okay, I uploaded it again in .zip format. Let me know if I didn't get to it quick enough. I'll create a batch file or something to run userdump if I need to.
-
Thanks for the dump - no it seems to be working (readable).
However, it seems to me that the dump was taken after ashServ fully initialized - ie. it seems to be done with the initialization phase, and ready to scan...
Maybe you really weren't fast enough... ;)
Thanks
Vlk
-
Thanks for the dump - no it seems to be working (readable).
However, it seems to me that the dump was taken after ashServ fully initialized - ie. it seems to be done with the initialization phase, and ready to scan...
Maybe you really weren't fast enough... ;)
Thanks
Vlk
I was afraid of that. The command line was stalled for a few seconds before it completed the task. Next, I'll try a simple batch file at start up. I only have like less than 15 seconds to grab that dump file for you. I'll give it another try tonight. This morning's attempt was as I was rusing out the door. :o
-
GDay All,
Culpeper, this may be a boot priority issue, where windows will start other services before/after the avast service, which in essence, stops avast from starting until other services have finished starting.
I have seen the behaviour you describe and I have usually corrected it by running Microsoft BootVis.
If all else fails, give it a try and let us know if it helps or not.
P.S. I have just now encountered the same problem under Vista RC1. This time though, I can't use BootVis to correct it. :(
Should I try to obtain a dump also and ftp it to you VLK ??
-
vlk:
I know I got it this time before the red circle disappeared using a batch file to confirm the dump. Let me know. It's uploaded.
Trumpy:
I think in Vista you can create a dump file through the Task Manager by right clicking on the process and selecting create dump file. I've read that somewhere.
-
I never used this dump thing, but I run it using the command:
userdump.exe ashServ.exe c:\ashServ.dmp
while the red circle was there.
And it generated a 70MB file. Zipped, it goes to 27MB.
How do I analyse it?
-
No problem. First, add RicardoB to the Zip file name so Vlk will see it is your file. In Explorer right click the Zip file and select copy. Open a new browser window and go to ftp://ftp.avast.com/incoming . Then select Edit, Paste and it should upload it to the ftp for Vlk to examine.
-
Thank you Culpeper for the explanation.
Vlk, I uploaded the file "RicardoB_ashServ.zip", it was generated with userdump.exe during start process.
Can you analyse it for me, please?
-
vlk is one of the staff members of Alwil, the maker of Avast. He'll get back with us on these dump files for any possible bugs. Thanks for bringing this problem to our attention. Please be patient. ;)
-
Hi guys, thanks again for the help. Unfortunately, it didn't work even this time... :(
Culperer's dump seems to be somehow corrupted (the debugger just refuses to load it, with no specific details); Ricardo's one seems to be valid, BUT is probably taken TOO EARLY -- that is, during the NORMAL initialization phase (normally, it takes a couple of seconds for the process to start up).
Please, guys, don't give up and try once more, maybe this time we'll be lucky! ;D
Thanks
Vlk
-
Hi guys, thanks again for the help. Unfortunately, it didn't work even this time... :(
Culperer's dump seems to be somehow corrupted (the debugger just refuses to load it, with no specific details); Ricardo's one seems to be valid, BUT is probably taken TOO EARLY -- that is, during the NORMAL initialization phase (normally, it takes a couple of seconds for the process to start up).
Please, guys, don't give up and try once more, maybe this time we'll be lucky! ;D
Thanks
Vlk
I'll keep trying until it kills me. Currently uploading Culpeper_0914*.zip
-
Thanks :)
Got the file, this time it's working - but it's very similar to Ricardo's one! Maybe this time, you were TOO fast...? I mean, how long after you captured this dump did it take for avast to start?
Thanks
Vlk
-
Thanks :)
Got the file, this time it's working - but it's very similar to Ricardo's one! Maybe this time, you were TOO fast...? I mean, how long after you captured this dump did it take for avast to start?
Thanks
Vlk
Well, this time I opened hangrep.exe and watched the window and the Avast icon until ashserv showed up in the hangrep window. Then I ran the userdump .bat file to create the dump file. It took about 5 seconds for userdump.exe to create and copy the ashserv.dmp file. After that the red circle continued to appear on the Avast icon for about another 5 seconds before it went away. So, doing the math it took about 5 seconds after the red circled Avast icon appeared in the system tray before ashserv.exe showed up in the hangrep window, another 5 seconds for userdump.exe to create and copy the dump file, and another 5 seconds before the red circle disappeared. That comes to 15 seconds, which is the average amount of time the red circle is present on the icon. If I try to create the dump file too soon using userdump.exe it will give a message that it is unable to locate ashserv.exe. Let me know.
-
Vlk,
I have uploaded two files:
>> RicardoB_ashServ_with_red_Circle.zip
I believe I got it right because it was right when I saw the "ashServ.exe" process running. Did I ?
The red Circle dissapeared just a few seconds after I run it.
>> RicardoB_ashServ_after_red_circle_dissapears.zip
(Just in case it helps for any reason.
The "ashServ.exe" process keeps running after Avast starts.)
I realized that "ashServ.exe" process takes a long time to appear in the Task Manager, and when it does, avast starts in a few seconds.
What is more strange is that during this "long time" no processes appear to use more than 1 percent of the processor. (99 percent CPU idle) Maybe a memory scanning or any memory procedure???
-
fwiw: I have the very same problem on two notebooks running vista rc1. on a 2processor Thinkpad the "delay" is 30sec, on a 1processor 1.2Ghz Sony it is almost 1 min.
-
drahnier, could you please check the status of the ashServ.exe process during the delay?
What is the duration of the period betwen ashServ.exe starting (i.e. first appearing in the Task Manager) and the red circle disappearing?
I.e. e.g. on the machine where it takes a minute to load, is ashServ.exe there for the whole minute, or only for a part of it?
Because so far it seems to me that ashServ.exe is not really hung, it just takes the system long time to load it! Maybe it's because it has a dependency on the RPC service which (under certain circumstances) loads slowly (?)
Thanks
Vlk
-
Vlk
I'm thinking along the same thing. My red circle does not disappear until after I have an internet connection. With my cable modem and router the red circle disappears as soon as everything is online and able to access the Internet. In my case that is taking about 15 seconds after the Avast icon appears in the task bar. Avast may be trying to establish an internet connection and can't during that short time period?
-
Vlk
I'm thinking along the same thing. My red circle does not disappear until after I have an internet connection. With my cable modem and router the red circle disappears as soon as everything is online and able to access the Internet. In my case that is taking about 15 seconds after the Avast icon appears in the task bar. Avast may be trying to establish an internet connection and can't during that short time period?
If this is the case, wouldn't it help to set the ashServ.exe to start delayed? This is a new feature in Vista which I havn't tried yet, but probably avast is a nice candidate for this.
I can do some further testing tomorrow eavening at the earliest but maybe someone with a litle more time at hand and running Vista could try this.
-
If this is the case, wouldn't it help to set the ashServ.exe to start delayed?
Do you know how to delay a Windows Service startup? I haven't found a way to do so...
This is a new feature in Vista which I havn't tried yet, but probably avast is a nice candidate for this.
OS is becoming better and better 8)
-
If this is the case, wouldn't it help to set the ashServ.exe to start delayed?
Do you know how to delay a Windows Service startup? I haven't found a way to do so...
This is a new feature in Vista which I havn't tried yet, but probably avast is a nice candidate for this.
OS is becoming better and better 8)
from memory: administrative tools -> services will start a management console which will list all installed services and their current state. double-click the avast antivirus service to pop up a properties box. set startup type as "Automatic (Delayed Start)". quit mgmt console and restart computer.
-
from memory: administrative tools -> services will start a management console which will list all installed services and their current state. double-click the avast antivirus service to pop up a properties box. set startup type as "Automatic (Delayed Start)". quit mgmt console and restart computer.
I see no option for Automatic (Delayed Start). Jus for Automatic.
-
from memory: administrative tools -> services will start a management console which will list all installed services and their current state. double-click the avast antivirus service to pop up a properties box. set startup type as "Automatic (Delayed Start)". quit mgmt console and restart computer.
I see no option for Automatic (Delayed Start). Jus for Automatic.
look harder ...
-
All I have is automatic, manual, Disabled. How come you have that extra option?
-
Snap Frank on XP Pro, perhaps this is a Vista beta ?
-
I see no option for Automatic (Delayed Start). Jus for Automatic.
This is Vista...
Do you know how to delay a Windows Service startup? I haven't found a way to do so...
I was thinking on XP... ::)
Net start command only works if the service is logged as an user.
How to start a service as System or Network?
-
You can delay how services are started in XP but it requires messing with what the service is dependent upon. Personally, I'm not willing to go that far with Avast. If I had a problem with Avast starting up like some of the other folks then I may want to look into it. But my 15 seconds is not long since the computer is actually still in the process of booting up when the red circle disappears on the Avast icon.
http://support.microsoft.com/?kbid=193888
-
Tech,
On my current system I just wrote a small routine to delay 2 minutes at startup and then NET START:
Diskeeper Service
Fax Service
Windows automatic update service
all the services start, as they should as SYSTEM.
-
That sounds like a useful routine, care to share Alan ;D
-
On my current system I just wrote a small routine to delay 2 minutes at startup and then NET START:
all the services start, as they should as SYSTEM.
Living and learning... a very good thing to test... I'll do soon 8)
-
Guys, I'm afraid I'm unable to follow... What we're trying to do is SPEED UP the startup of the avast service, not DELAY it, right?? ;)
I mean, there is absolutely NO need for the Internet connection to be present when the service is starting. It seems that somehow, the service control manager is locked and isn't starting other services (avast including) while that one is initializing...
The avast service has a dependency on "RPC" - but so do many other services built into Windows - so it's not very likely this is the culprit. Anyway, you could try to remove the RPCSS dependency and see if it makes any difference.
Cheers
Vlk
-
Is there a bug in the Avast startup?
-
Vlk,
sorry if the "delaying" issue is confusing you. The issue related to deferring the start of other non-essential services (not avast) at startup to reduce any potential interference with avast completing its startup tasks.
-
Hi guys, I've got some news. Igor was kind and mentioned that he has seen a similar issue on one of his own machines (running Windows x64 - but that doesn't seem to make any difference). So, I did some monitoring and found that the problem is caused by the "Workstation" service that hangs on startup (most likely communicating with the network stack) while holding the global SCM (Service Control Manager) lock (preventing other services from starting).
So, what I did is create a dependency of the "Workstation" service on the avast services - and voila, the problem was solved. You can try the same - chances are it will help on your machines, too.
I have created a reg file to make it simple - just import http://public.avast.com/~vlk/avast-fast.reg , reboot the machine and see if it makes any difference.
Please note that the reg file assumes that you're using the "Web Shield" and "Internet Mail" providers, that is, that the two corresponding services are installed on started (almost always the case - unless you have played with the avast config a bit).
Cheers
Vlk
-
Very good! Thank you.
-
So - did it make a difference? :)
-
I have created a reg file to make it simple - just import http://public.avast.com/~vlk/avast-fast.reg , reboot the machine and see if it makes any difference.
Troubles.
1. BSOD in next boot. PAGE_FAULT_IN_NONPAGED_AREA. Error Message: STOP 0x00000050.
I think it's related to AntiKill feature... but I'm not sure.
2. Troubles with Comodo firewall after the second, valid, boot.
The avast services 'refuse' to connect ???
The CPU activity of the firewall process goes above 90%
3. Removing the Registry key and booting... things become ok again.
-
These is beyond the average user and would probably be best if corrected in a future version of Avast.
-
1. BSOD in next boot. PAGE_FAULT_IN_NONPAGED_AREA. Error Message: STOP 0x00000050.
I think it's related to AntiKill feature... but I'm not sure.
Hardly, but to verify, you can send me the corresponding minidump (from \windows\minidump).
2. Troubles with Comodo firewall after the second, valid, boot.
The avast services 'refuse' to connect
The CPU activity of the firewall process goes above 90%
Heh, seems like a bug in Comodo...(?) There's nothing inapropriate in the reg file, I mean, what it's doing is legal and valid - but Comodo probably gets somehow confused...
...and would probably be best if corrected in a future version of Avast.
Well, the point is, this is really a problem in Windows. One of the services (in Igor's case, "Workstation") is locking the whole system and so other services are not given a chance to start... ;)
Cheers
Vlk
-
Hardly, but to verify, you can send me the corresponding minidump (from \windows\minidump).
Not this time... The feature was disabled...
Well, the point is, this is really a problem in Windows. One of the services (in Igor's case, "Workstation") is locking the whole system and so other services are not given a chance to start... ;)
My logon was slower than ever... The task bar took more than one minute just to appear...
Before, it appears, avast was working and not a trouble. Using the reg file I can even see the taskbar, system tray, programs loading, etc. ::)
-
That doesn't sound too surprising given that the Comodo process was eating almost 100% CPU... :)
BTW you really have generation of (any kind of) dumps disabled?? That's very odd! Why's that? It doesn't bring any benefits as far as I can tell...
Cheers
Vlk
-
BTW you really have generation of (any kind of) dumps disabled?? That's very odd! Why's that? It doesn't bring any benefits as far as I can tell...
No, I don't have it by choice...
The Alert service was down due to Computer Locator service (or whatever is its name) either...
Even set to Automatic start... So, I can't configure dumps right now...
Maybe next boot... Something is blocking them ???
-
They both depend on the Workstation, which (by doing the change) now depends on the three avast services. Do you normally run both WebShield and Internet Mail providers? (as otherwise, the reg file will not work for you, as one of the services will not start).
-
They both depend on the Workstation, which (by doing the change) now depends on the three avast services.
How can I turn back the system to the original state?
Just deleting HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanworkstation key or just a value of it?
Do you normally run both WebShield and Internet Mail providers? (as otherwise, the reg file will not work for you, as one of the services will not start).
Sure... but they start manually (the default values).
-
I'm on cable and I get the red circle on boot but it doesn't take very long for it to go away. I don't view this as a problem. It takes a moment for Avast to come online along with everything else that is booting up at the same time. Enabling and disabling your connection rather than being online all the time is something that can be selected in the Avast menu settings.
I've been following this thread with interest because I've got a similar problem...
You can delay automatic windows logon by doing following, see if that helps:
Start->run...->type "gpedit.msc" (Only in XP Pro)->Press enter->Navigate to "Local Computer Policy"->"Computer configuration"->"Administrative Templates"->"System"->"Logon"
From there, enable "Always wait for the network at computer starup and logon"
This will delay starting of explorer right after logon until the network is available...
But this doesn't solve my problem:
When PC starts up and logs on automatically, explorer loads and system starts normally. When everything's done I end up with all startup programs loaded (both from registry and Startup folder) but more than half of the sys-tray icons are missing. As such, I can't access any of those programs from sys-tray. If I then logoff and logon again, everything is normal. I have tracked it down to Avast being the cause of this somehow, if I uninstall avast only, leave the rest the way it is, I don't have this problem.
Any ideas?
-
I have had problems with that darn Avast system tray icon every since I switched to XP. There are threads in the very forum discussing such things as missing Avast icon that gives some ideas on what can be done. Such as the following...
http://forum.avast.com/index.php?topic=16372.0
and
http://forum.avast.com/index.php?topic=19370.0
-
Do you normally run both WebShield and Internet Mail providers? (as otherwise, the reg file will not work for you, as one of the services will not start).
Should I set the services to automatic?
-
Vlk,
forgive me if I have extrapolated too far the logic of your analysis with the Workstation service. In discussing this with one of my folks (who has the red circle) we decided to perform a quick test on his machine, not with the registry changes but simply wiith the Workstation service set to disabled.
The result was - no change in the appearance of the red circle.
-
forgive me if I have extrapolated too far the logic of your analysis with the Workstation service. In discussing this with one of my folks (who has the red circle) we decided to perform a quick test on his machine, not with the registry changes but simply wiith the Workstation service set to disabled.
The result was - no change in the appearance of the red circle.
This most likely means that it was not the Workstation service which was causing the problem in his case. It would be actually interesting which service locked the SCM then. To find this out, start the services applet (services.msc) when the red cross is on, sort the list by Status, and see which of the services is in the "Starting" state (as opposed to "Started" or a blank space which means stopped).
BTW I'm assuming that this will be done when the ashServ.exe process is still not started, i.e. the avast service hasn't been given a chance to start (yet).
Thanks
Vlk
-
Do you normally run both WebShield and Internet Mail providers? (as otherwise, the reg file will not work for you, as one of the services will not start).
Should I set the services to automatic?
Vlk :'( :'( :'(
-
Should I set the services to automatic?
No, not really, it makes no difference as the providers start them anyway.
-
Should I set the services to automatic?
No, not really, it makes no difference as the providers start them anyway.
Thanks... I`ve thought that they were started when 'needed', I mean, while opening the browser for the first time, WebShield service will be started, when the email program is opened, mail service will start.
So, as I can see, I`m completely wrong. The services seem to be started by avast!
-
Vlk, did have a clue with the dump file I uploaded?
You think the problem is from the Operating System or from Avast?
-
well, as I said, the dump seems clean. I.e. it shows normal initialization of the ashServ.exe process - which is indeed not taking so long, even on your machine (according to what you said).
The real problem lies in the fact that Windows starts the ashServ.exe process late. I.e. it takes a long time for the process to even appear in the list of running processes.
This is usually caused by the Service Control Manager waiting for some other service to complete loading - and as I suggested, this may often be the case of the "Workstation" service which tends to wait for a network connection to become active.
At this stage, I'm not sure how to help further... I'll try to investigate other methods of loading the ashserv.exe process earlier, but it will probably never be 100% (MS said this should be improved in Vista where there's no Service Control Manager lock in place anymore).
Thanks
Vlk
-
I'll try to investigate other methods of loading the ashserv.exe process earlier
If you find something for XP, please, let us know.
Besides the net start and net stop methods, I can't find how to manage XP Services loading.
-
Hi
I have been having the same problem with the long startup and red circle and have read with interest all the posts here.
I have somehow managed to rid myself of the problem, but I don't know exactly which of the following did the trick. I thought I would post what I did in order to help out others who are experiencing this rather frustrating issue. Mine only started when I built a new computer and re-installed Avast.
In order, I:
1. Ran the Workstation registry patch provided earlier in this posting.
2. Changed the Avast Antivirus startup to 'Automatic' (explained earlier in this thread).
3. Changed every other entry referencing Avast to 'Automatic' that was listed in Startup.
4. Ran Ashampoo WinOptimizer and stopped the following services from starting up at boot:
a) all the Acrobat services - Speed launcher, Gamma Loader, Acrobat Assistant & UpdateScheder
b) Bluetooth Authentication Agent
c) Nerocheck.exe
d) Quicktime Task
e) SunJavaUpdateSched
Then, Windows Services:
a) Messenger
b) Netmeeting
c) QoS RSVP
d) Remote Desktop Help Session Manager
e) SSDP Discovery Service
f) Task Scheduler
g) Terminal Services
h) Uniterruptible Power Supply
i) Alerter
Obviously, these can be changed without purchasing and running Ashampoo - run services.msc from the 'Run' menu and disable/enable as described. I don't work for Ashampoo!
My specs are:
XP Home SP-2
AMD X2 Dual Core 4400+ Socket 939
Asrock Dual SATA II MB
2gb PQI RAM DDR400
Asus 7900GTX Video Card
Seagate 300gb SATA II HD
Pioneer 109 DVD-RW
BenQ 52X CD-RW
Nothing overclocked and no goofy software that would screw around with XP startup.
I am sorry I didn't properly test each step listed above to ascertain which startup service was delaying Avast, but I hope that this may help others eliminate the red circle.
If I can help in any other way, please let me know.
Many thanks to all for your posts that helped me, especially Vlk's.
Jack
-
I thought I would post what I did in order to help out others who are experiencing this rather frustrating issue.
Thanks Jack. Indeed it could help.
Ran the Workstation registry patch provided earlier in this posting.
This is the most important and, for the majority of the users, the only thing they have to do.
2. Changed the Avast Antivirus startup to 'Automatic' (explained earlier in this thread).
It's the default...
3. Changed every other entry referencing Avast to 'Automatic' that was listed in Startup.
I'm waiting for Vlk's answer to my post about this ::) ::)
Stopped the following services from starting up at boot:
a) all the Acrobat services - Speed launcher, Gamma Loader, Acrobat Assistant & UpdateScheder
b) Bluetooth Authentication Agent
c) Nerocheck.exe
d) Quicktime Task
e) SunJavaUpdateSched
Won't harm... indeed will make a faster boot...
Then, Windows Services:
f) Task Scheduler
i) Alerter
I won't do with this two Services...
-
http://forum.avast.com/index.php?topic=24617.0
From the inserted thread link I have been having the same problems
I think that the only real way around it is for avast to put out some sort of patch ::)before a lot of us migrate to AVG.
I will give it one month before I migrate
-
Jack4378
Thanks a lot
I copies your suggestion word for word and it's all sorted
Cheers
-
Hi
Glad to hear my suggestions worked for you.
I had to come back to my own list here (lost my favourites) and re-do the steps as I reinstalled Windows after a hard drive failure.
For me, it is clear that the registry patch provided a few pages back is definitely the step that fixed the problem for me. I tried all of my own steps and nothing worked until I patched.
Jack