Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: LittleBit on June 27, 2007, 02:55:46 PM
-
Hi there,
i have a problem with the login to my WinXP64 at the login screen what seemes to me related to Avast! 4.7 Home.
When WinXP64 has booted to the login screen i have a few seconds to select a user profile - when i enter the correkt password the system freezes - no mouse move - no disk activity - no softreboot by external reset.
I can allways login using "last known good configuration" at boottime. So i made a system wide scan - no results.
When i left the computer for a while at login screen (booted without any alternative option) a message has popped up that a process of Avast! has a problem and needs to be closed. I am sorry - i cant really remember the exact message (what a shame).
For testing i deinstalled Avast! - and so the login-problem disappeared. So i hoped this was only a tempory problem with an update and reinstalled Avast! All went fine - for about 3-4 days - and now i am back at the same situation. When i deinstalled Avast! again - all went fine again.
A found an other user with nearly exact the same trouble - and problem started nearly the same time. He also uses WinXP64 and Avast! virus scanner.
Is this a known problem ? Is there a solution to this ? Any suggestions welcome.
Thanks in advance,
Tom
-
No, this is certainly not a known issue, avast! should work correctly in WinXP x64.
I'm afraid we'd need some more info... is there anything in system Event Log (some more details about those crashes I mean - addresses, etc.)
-
Thanks for your fast reply!
The System Event Log gives no hints - only information - some errors related to a unreadable CD.
In the Application Log there are some related to Avast! Allways the exactly the same:
Faulting application avast.setup, version 4.7.0.0, faulting module ntdll.dll, version 5.2.3790.3959, fault address 0x0004d233.
Servicepack2 for WinXP64 is installed - also all critical Updates provided by MS.
Hope that helps a bit more.
Cheers,
Tom
-
The real culprit is the faulting module ntdll.dll, that avast.setup just happened to be using, though I have no idea how to overcome that.
The avast.setup is the avast update process checking for updates, though why it is happening so early is strange (zero personal experience of XP64), probably you have a broadband connection and avast is trying to get out since the connection is established.
I wonder if editing the C:\Program Files\Alwil Software\Avast4\Data\avast4.ini file (notepad or other text editor) to delay the avast auto update check might help. Add the AlwaysConnectedWaitSeconds=120 (delays by 120 seconds, can be increased, default is 30) in the [InetWD] section of the avast4.ini file.
[InetWD]
AlwaysConnectedWaitSeconds=120
-
@DavidR
I have taken a look into the avast4.ini file. There is no entry AlwaysConnectedWaitSeconds and no group [InetWD]. I have done a fresh install on another machine to check whether this is related only to my own System - the other (XP32) also has none of those entries. Should i add them ? Version in both cases Avast! 4.7.1001 Home. Custom install - no OE-Support - no Skins - the rest by default.
Thanks for your answer,
Tom
-
There wouldn't be a line for AlwaysConnectedWaitSeconds (there are many default settings that don't appear in the avast4.ini) which is why I said to add it, though for it to have no [InetWD] section is most strange and certainly for winxp32 bit should be there.
You didn't confirm my assumption you connect to the internet using broadband ?
If so, try this, change the avast Program Settings (right click the avast icon) Update (Connections) so that it matches your connection, not both checked or both unchecked, just check the one that matches your connection. That because of the change may generate the [InetWD] section allowing the edit.
I guess it would be possible to create the [InetWD] section and then add the new line, the section is between the [Simple] and [Quick] sections. See an example of my settings, don't replicate mine as I'm on dial-up.
[Simple]
ShowHelpCheckList=1
SkinUseLayeredWindows=0
TimeOfLastScan=1182645453
[Chest]
MaxSize=512
[InetWD]
UseRAS=1
RASWaitSeconds=120
UpdatePeriod=240
[Quick]
EnableSkins=1
InfectionExitApp=0
ShowResults=1
Yours should/would look like
[InetWD]
AssumeAlwaysConnected=1
AlwaysConnectedWaitSeconds=120
UpdatePeriod=240
-
Hi David,
i added the missing section by setting "use dialup connection" in the option and then edited with the values you recommended. So i have to wait to see if the application errors disappear.
Thanks for your help,
Tom
-
Your welcome.
But, are you using dial-up as your connection method (or did you do change it just to create the [IntWD] section) ?
If you are using dial-up then the suggested method won't work, which is why I have been banging on about what your connection method is ?
If it is dial-up then your {InetWD] section should look my example in the "quoted" section of my avast4.ini.
-
No, this is certainly not a known issue, avast! should work correctly in WinXP x64.
I'm afraid we'd need some more info... is there anything in system Event Log (some more details about those crashes I mean - addresses, etc.)
I follow Igor... I can't see a correlation between update period and connection type with avast freezing Windows and ntdll.dll trouble... (By the way, is it ntldr.sys ???)
-
@DavidR
I am on a broadband connection - so i only used dialup to create the section and then to edit it.
There were no more avast.setup crashes. As they are not so frequently before i am not sure whether it solved that or not - but signs are good. Thanks
@Tech
it is ntdll.dll and not ntldr.sys.
Afaik ntldr.sys is Part of the early boot sequence while ntdll.dll is part of the kernel and is used by many applications.
In another forum i found two users with the same login problem. Both on WinXP64 and avast - one has confirmed to use also SP2 for XP64 - the other has not said about. The one using SP2 for XP64 has also confirmed that there were no problems before installing SP2 (cannot say whether it appears directly after installing SP2). So maybe a interference from SP2 and avast ?
Tom
-
So maybe a interference from SP2 and avast?
Tom, my knowledge does not go so further... we need Alwil team programmers help.
-
@DavidR
I am on a broadband connection - so i only used dialup to create the section and then to edit it.
There were no more avast.setup crashes. As they are not so frequently before i am not sure whether it solved that or not - but signs are good. Thanks
<snp>
Tom
Your welcome, fingers crossed it will remain that way.
Thanks for the feedback.
-
Same issue here: WinXP64Pro, Celeron 64 bit processor (yes, there are such things as 64 bit celerons, search for them before you post), 1 Gig system ram, some system ram is shared to on-board graphics, Avast Home edition installed (registered), worked fine in the beginning, now freezing.
I have some additional information to assist troubleshooters.
1] My PC is never left on all the time, it is powered off until I wish to use it.
When I wish to use the PC, I apply power to the PC, it goes through bootup process (normal for me is GRUB (because I dual boot with Linux), where I manually select Windows XP), booting to the Windows XP welcome screen.
2] From this point, I have 10-20% chance of logging in as my default user without ANY problems.
Important note: the other of the logins all fail no matter which user I elect to log in as.
It was suggested in another forum (TechIMO) that I should try a guest login (possibly they thought my normal user was the problem?). I have had no replies to that thread, after I posted that freezing does not matter which user I select.
3] Actually, the freezing occurs within 5 to 15 seconds of the login screen appearing, so sometimes I can click my icon AND type in my password and then I freeze, sometimes I can't even click my user icon and the system is frozen.
That timing makes me think the failure is NOT a user configuration file (many freezes take place before a user has logged in). To that end, troubleshooting should consider what XP system files are loaded (by windows) before anyone even logs in.
4] I am using SP1 only, it was included with my XP64 CD; no updates are permitted on this machine.
Why? I have heard horror stories about 32 bit XP getting REALLY trashed by service packs, so why would I want to take an even greater risk on updating the LESS popular 64 bit XP?
More:
Presently, I am using a selective startup to disable automatic starting of Avast until I can determine if Avast is the root cause. So far, I have succeeded in logging in once while Avast is not started. But this could also be part of my usual 10 - 20%.
I use DSL.
I use a wireless connection to my wireless router, that connection recently got misconfigured, but is working fine for the past 2 days; today, I had to reboot 6 times, due to freezing at login (I finally chose safe mode and activated the selective startup that I just mentioned). Back when the network was malfunctioning, I was not refused ANY logins, so I'd say the network being functional MIGHT be part of the problem (again, the 10 - 20% success thing might have let me in when the network was malfunctioning).
-
No ideas, anyone?
(If I did something wrong by ADDING my problem to this persons IDENTICAL problem, maybe someone could PM me to tell me to start a new thread..... or maybe a moderator could split this thread).
-
2] From this point, I have 10-20% chance of logging in as my default user without ANY problems.
Important note: the other of the logins all fail no matter which user I elect to log in as.
What does happen? Any error message? Can you boot in Safe Mode?
3] Actually, the freezing occurs within 5 to 15 seconds of the login screen appearing, so sometimes I can click my icon AND type in my password and then I freeze, sometimes I can't even click my user icon and the system is frozen.
That timing makes me think the failure is NOT a user configuration file (many freezes take place before a user has logged in). To that end, troubleshooting should consider what XP system files are loaded (by windows) before anyone even logs in.
Any new hardware added?
Any other antivirus installed (besides avast)?
4] I am using SP1 only, it was included with my XP64 CD; no updates are permitted on this machine.
Why can't you update?
Why? I have heard horror stories about 32 bit XP getting REALLY trashed by service packs, so why would I want to take an even greater risk on updating the LESS popular 64 bit XP?
Staying without update is dangerous and will make even unstable your system. I see no special reason for not to update a legit copy of Windows 64x.
-
Let's try this:
open Regedit, navigate to HKLM\System\CurrentControlSet\Services\Avast! Antivirus, and DELETE (or RENAME) the value called "Group".
Also, do the same for the "avast! Web Scanner" and "avast! Mail Scanner" services.
Then reboot the system and see if it makes any difference.
If not, we may need to capture a full memory dump to find out what's going on. Are you using PS/2 or USB keyboard?
Thanks
Vlk
-
2] From this point, I have 10-20% chance of logging in as my default user without ANY problems.
Important note: the other of the logins all fail no matter which user I elect to log in as.
What does happen? Any error message? Can you boot in Safe Mode?
Which way? If I am allowed to login, nothing is wrong. If I cannot login, the screen is frozen, nothing more for the hour I waited (I've repeated the waiting test several times, various durations - nothing except POSSIBLY cursor movement). I can go in under safe mode, but to what avail? Safe mode is how I am now running msconfig and selective startup and I have deselected all avast startups, seems to be ok for the last 4 boots.
3] Actually, the freezing occurs within 5 to 15 seconds of the login screen appearing, so sometimes I can click my icon AND type in my password and then I freeze, sometimes I can't even click my user icon and the system is frozen.
That timing makes me think the failure is NOT a user configuration file (many freezes take place before a user has logged in). To that end, troubleshooting should consider what XP system files are loaded (by windows) before anyone even logs in.
Any new hardware added?
Any other antivirus installed (besides avast)?
New as of when? Since I installed Avast? No new hardware. Before I installed avast? Well, yes, but the freezing began weeks after I installed avast, which was months after the latest hardware addition. I'd never run 2 antivirus programs, so no, avast is alone.
4] I am using SP1 only, it was included with my XP64 CD; no updates are permitted on this machine.
Why can't you update?
As the admin, I refuse to suffer the screwups which Microsoft always generates (I elaborated on this in my next paragraph). This system is working as is, and was working fine before avast and worked fine until shortly after avast updated its program a few months back.
Why? I have heard horror stories about 32 bit XP getting REALLY trashed by service packs, so why would I want to take an even greater risk on updating the LESS popular 64 bit XP?
Staying without update is dangerous and will make even unstable your system. I see no special reason for not to update a legit copy of Windows 64x.
I stand right there - NO updates. I refuse to be put through the crap which the typical Microsoft update puts people through. Not open for discussion.
-
Let's try this:
open Regedit, navigate to HKLM\System\CurrentControlSet\Services\Avast! Antivirus, and DELETE (or RENAME) the value called "Group".
Also, do the same for the "avast! Web Scanner" and "avast! Mail Scanner" services.
Then reboot the system and see if it makes any difference.
If not, we may need to capture a full memory dump to find out what's going on. Are you using PS/2 or USB keyboard?
Thanks
Vlk
Ok, I'll re-enable the avast startup items which I disabled using msconfig, then I'll cold boot a few times over the next few days to be sure I have returned to the failure mode and THEN get back to you..... maybe a week or two before I get back to you because I only power up once a day.
-
I can go in under safe mode, but to what avail?
To uninstall avast or any other program that is crashing your computer.
Ok, I'll re-enable the avast startup items which I disabled using msconfig, then I'll cold boot a few times over the next few days to be sure I have returned to the failure mode and THEN get back to you..... maybe a week or two before I get back to you because I only power up once a day.
If this happens, please, check the folder <avast>\data\log
Are there any files called unpXXXX there (where XXXX is a random number)?
If so, send them to vlk (at) avast.com
They may contain more information about the problem (maybe a link to this thread).
-
I can go in under safe mode, but to what avail?
To uninstall avast or any other program that is crashing your computer.
But, my friend, I have faith we can FIX this issue!! Besides, I already used safe mode to invoke msconfig so I could get control over startup files! I'm posting because I can now log in, with avast not being started.
(Rhetorical) Why uninstall?? I like avast!!
Ok, I'll re-enable the avast startup items which I disabled using msconfig, then I'll cold boot a few times over the next few days to be sure I have returned to the failure mode and THEN get back to you..... maybe a week or two before I get back to you because I only power up once a day.
If this happens, please, check the folder <avast>\data\log
Are there any files called unpXXXX there (where XXXX is a random number)?
If so, send them to vlk (at) avast.com
Should I get a copy of the file before I undo my msconfig edits (so that you an see before and after)?
They may contain more information about the problem (maybe a link to this thread).
I'm confused. Did you mean to say my \data\log file might have a link to this forum thread?? How could that be?
-
(Rhetorical) Why uninstall?? I like avast!!
Sometimes, uninstall is needed to get a correct install. Sometimes you need to go back to choose the right way...
Should I get a copy of the file before I undo my msconfig edits (so that you an see before and after)?
If the files exist, do it, if they don't exist, forget it.
I'm confused. Did you mean to say my \data\log file might have a link to this forum thread?? How could that be?
No, I said that you can inform in the email body a link to this thread, so Vlk would know what are you talking about and don't need to write all the story again.
-
Sometimes, uninstall is needed to get a correct install. Sometimes you need to go back to choose the right way...
The installation was fine for months....
-
Sometimes, uninstall is needed to get a correct install. Sometimes you need to go back to choose the right way...
The installation was fine for months....
Well... what more can I suggest? I'm empty...
-
Sorry, things got too difficult here at home.
Tech™: I'm still running with Avast disabled, there are no unpxxxx files in my <avast>\data\log. I still need to re-enable the startup items, am doing that right now.
-
Sorry, things got too difficult here at home.
The thread is long (2 pages), which are the exactly problems you're experiencing now?
Did you try to install avast from the scratch?
-
I have NOT uninstalled Avast, I have not reinstalled Avast, I have not edited my registry. I believe that if I remove or remedy the problem, you have nothing to troubleshoot and nothing to learn, so I'm letting this system remain as it is, so that I can help Avast get this right. If Avast is still interested.
With Avast (currently running 4.7.1029) fully enabled:
After booting WinXP64, the system reaches the normal user login screen and then suffers from freezeups, remains frozen until I reboot; second boot attempt usually passes, a few times I needed a third boot and never needed more than 4 boots to get logged in.
The freezing is not related to what the user does - it might freeze during an admin login selection or freeze during a normal user login; it might freeze before while entering a password or might freeze during password entry or (if I'm VERY fast) freeze after password entry but before the screen ever clears. I've seen the system freeze BEFORE I could click a user icon. For the one time that I tested the freeze duration, the freeze has lasted several hours (I then gave up and rebooted).
With MSCONFIG, I used selected startup, uncheck all Avast startup items:
System is fully normal.
You have asked me if I found any unpxxxx files in <avast>/data/log directory; I responded I have not seen any of those files.
I have returned to allowing all Avast items to startup, I have only warm booted, warm booting always allows me to log in. I need full cold boots to get the freezeup problem at all. Now that I have restored Avast to being allowed to start, I believe I need a few cold boots to resume the problem.
-
Try turning on the "Delay loading of avast services" option on the Troubleshooting page of the avast Settings.
Thanks
Vlk
-
Ok, I will do that after the machine resumes freezups... the freezeups take a few cold boots before they return, I have only cold booted once and machine did not freeze this time.
-
Ok, it just froze a few minutes ago on todays first cold boot. 8) I'll assume the problem has returned and hasn't changed.
I am now setting the software to delay loading, as mentioned a few posts above.
-
I know resurrecting an old topic is a no-no, but this one was left hanging.
I have Windows XP Pro x64 (SP2 plus all updates except some optional updates) and avast home 4.7-1043 (on my home computer). I had the Welcome screen hang problem every other boot. One boot would work, but the next would freeze / hang on the welcome / login screen before or after entering the password. This was solidly consistent.
After days of fiddling with updating drivers and firmware without solving the trouble, I broke down and went through the msconfig selective startup to try to isolate the problem. I quickly learned it was a service causing the problem and, through a process of elimination (*many* reboots while methodically adding services to a base setup that worked), I discovered avast was the source of the trouble.
I googled and came upon this thread.
I tried selecting the "always connected" updates preference (neither were selected by default), but that did not help. Same problem.
I tried selecting the "start after other system services" option under the troubleshooting preferences and that has solved the trouble.
I am not really sure when the problem began because I don't reboot often, but there is definitely some kind of errant interaction between other services and avast that causes the trouble. I don't really have time to stick a debugger on this, but it shouldn't be that hard to run down for a fix with later versions.
-
Hmmm....
I dont know what the problem you have currently....
But it seems that you are having a problem with a hardware recognize software or any program that working to recognize any hardware plug in usually mouse, camera or anything...
Maybe you should check this software....I have an experience with this kind of problems....
On the logon screen we cannot even click on the user or we just can enter the password and then the computer or the laptops starting hanging....
Sori for a bad language....
Wish you luck...
-
I was indicating that I found the solution and what that solution was. I am not having any trouble since applying the solution.
I tried selecting the "start after other system services" option under the troubleshooting preferences and that has solved the trouble.