Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: linwin on May 06, 2008, 11:04:20 AM
-
I just purchased a new notebook today. It has Vista Home as an OS and I immediately dumped Norton and downloaded 4.8 Avast home as a antivirus program. The initial memory check also no problems, but when I started a scan there was no scan! the message "initialzing engine, please wait" came up and the current scanner status, 0% complete also came up and stayed there!! Forever!! No scan. I uninstalled and reinstalled, no differance! What gives?
Richard
-
Hi linwin!
If norton was installed that probably causes problems:
Please try the following:
1. Download the Norton Removal tool:
http://fileforum.betanews.com/detail/Norton_Removal_Tool_for_Windows_2000XPVista/1169144666/1
2. Remove Avast!
3. Run Norton Removal Tool
4. Restart your computer
5. Install Avast!
6. Restart your computer again
7. Try to run a scan again...
yours
onlysomeone
-
Did exactly as you advised with no change! Still no scan.
-
you could try to upgrade to the actual beta - probably it works then...
http://forum.avast.com/index.php?topic=34612.0
if not there are some questions to answer :)
- do you use any other security programs? (antivirus, firewall, antispyware,...)
- how long did you wait for the "initializing engine, please wait" to go away?
-
Does it make any difference if you change the scan sensitivity to Quick/Standard/Thorough?
-
Richard Stay home long enough to answer your phone ;D
I thought of a couple other things you might want to try, first check and see if your user account is an admin account,
Also try running the avast installer with admin privileges you can right click on the installer and you will see the run with admin privileges option in the right click menu.
The weirdest stuff I have run into with vista and applications so far always boils down to user level restrictions...argh!
IF all else fails it might be a great excuse to try out 64bit linux!! ;D
-
I guess it is the same as: http://forum.avast.com/index.php?topic=35280.0
In short, "quick" works, "thorough" works, "standard" doens't work.
BTW, the "standard" scanning with "local hard disks" finally starts if you wait some minutes, it is not really hanged.
-
Can you try if the latest beta version solves this?
Download the updater (http://files.avast.com/files/beta/aswbeta.exe) and run it or go here (http://forum.avast.com/index.php?topic=34612.msg290254#msg290254) for more information.
If the beta does not solve, hmmm, maybe a bug then...
-
I am seeing the same problem of prolonged wait before scan starts on "Standard Scan" of "All local drives" with the current beta.
-
I am seeing the same problem of prolonged wait before scan starts on "Standard Scan" of "All local drives" with the current beta.
Same here,started happening yesterday (6th).The wait for engine to be ready is about 5 minutes,then scans ok.Have been using Avast for about three years now with no probs until now.Do you think this is a Avast problem that will be fixed?
Regards
-
Windows XP-Home, SP2, all upgrades. Avast! build 4.8.1187 (beta) and VPS 080506.0
Individual folder scan OK, but on scan "Local Hard Disks", no activity on Quick or Standard after several minutes. On Thorough the hard drive activity light comes on when Start scan clicked, but again no progress after several minutes. Same story if Test archives ticked or unticked. Can't remember whether it has been this way since I installed the beta version, or just since the last VPS update. Certainly didn't have this problem when I installed the original 4.8 download.
Hope this helps.
-
Have now done some further tests:-
Did complete uninstall of build 4.8.1187, ran aswclear.exe from boot into safe mode.
Installed released version 4.8.1169 and updated VPS to current 080506.0.
Problem was still present. If Scan of C: drive selected from "folder" it worked OK. If scan of "Local Hard Disks" selected (in this case C:,D:,E:,F:) then no apparent scanning had commenced after 2 minutes (exactly as per my previous post. Further, once a scan had been attempted in this maner, if it was aborted, unticked and then a folder scan attempted, it also didn't get under way, but after exit from simple use interface and then re enter, the folder scan would work again.
Next step - As I use Acronis partition images, I reinstalled an image from earlier this week which had Avast 4.8.1187 but with an earlier VPS - namely 080504-0. The scan from both "Local Hard Disks" and from "Folders" works correctly - no significant delay at the start.
Could this problem simply be something not right in the latest VPS update?
Again, hope this helps
-
Hi everyone :
I'm experiencing the same issue but only when I try toperform a scan via "Show Local Disk Options", so maybe a workaund may be :
a) Scan your machine using the Folder Selection Panel
b) Using the Quick Scan (Explorer context menu)
Kindly regards
MiguelAngelXP ;D
-
I am seeing the same problem of prolonged wait before scan starts on "Standard Scan" of "All local drives" with the current beta.
That is the only scan I do and I have to say I don't notice that in my last scan on Sunday.
However, I just started it off now and am watching it spin its wheels so to speak waiting for it to get under way and it just has taking 2.5 minutes to get started.
The status under the local disks shows scanning, the activity bar is moving but the scan shows 0% So it may be that I just didn't notice it stall (or the rootkit scan is taking longer than it should) before it truly starts its on-demand scan.
Which although indicates it seems stalled 2.5 minutes for me isn't the end of the world, but it may well be greater for others and it needs investigation by the Alwil team.
The scan is well under way now so I will see if it includes the duration whilst it was spinning its wheels.
Update:
Scan completed in 16:32 which is a little over 4 minutes longer than my normal scan duration. So I don't know if that extra was a) the addition of the 2.5 minutes spent spinning its wheels plus a little because I continued browsing and answering posts on the forums.
So It would seem that my last scan on Sunday didn't suffer this delayed start as it was in a little over 12 minutes. So the suggestion this might have something to do with a VPS update is one that might carry some weight as there are other functions carried out other than simply updating the VPS.
So somewhere between Sunday and VPS 080505-0, as I'm a day behind on VPS updates, as I have had updates set to manual testing something else.
-
The issue seems to be fixed with today's update (080507-0, 07/05/08).
-
It would still be interesting to know what came down the pipe with a VPS to cause this anomaly.
-
The issue seems to be fixed with today's update (080507-0, 07/05/08).
i agree with you :)
also tried it before and after the update and it in any case changed... :)
(allthrough i usually only use the intensive-scan (or however it is named in the English version))
-
The issue seems to be fixed with today's update (080507-0, 07/05/08).
Agreed, It doesn't freeze, but the scan speed still seems slow.
-
Yes, I can also confirm that the problem is no longer present. So it wasn't there with VPS update 080505-0, it was present with 080506-0 and gone with 080507-0. Looks like it was something in 080506-0.
In my case, the problem existed with Quick, Normal and Thorough and I understand that the root kit scan is only included in the Normal and Thorough, so perhaps it did not relate to the rootkit part of the scan. Would be nice to know what it was. :)
-
It was there with 080505-0 as that was the VPS I had when I tested it.
My last regular weekly scan was on Sunday very early morning (4 May 08) so I probably had 080503-0 during that scan so I would think it was in 080504-0 or 080505-0.
-
Can you try if the latest beta version solves this?
Download the updater (http://files.avast.com/files/beta/aswbeta.exe) and run it or go here (http://forum.avast.com/index.php?topic=34612.msg290254#msg290254) for more information.
There is a new beta, can you try?
-
Tech
Have installed 4.8.1192. Scan from Simple user interface starts Ok with no delay on all three Quick, Normal & Thorough settings. VPS is 080507-0. Scan time in Normal is about the same as it was with 4.8.1187 using the same VPS.
For 4.8.1187/080507-0 it took 16mins 21secs to scan 93,222 files in 10,660 folders 151GB scanned.
For 4.8.1192/080507-0 it tool 16 mins 35secs to scan 93,276 files in 10,664 folders 151GB scanned.
The above is a scan of C:,D:,E:,F: which is 2 drives each 2 partitions. CPU is a 2.40MHz Intel Core2 Duo, memory 1GB. OS is XP-Home, SP2, all current updates. Both scans were carried out with SpybotSD's Teatimer active.
DavidR,
Yes that is strange, in my case I had no problem with the scan starts with 080505-0, or 080507-0, only 080506-0. Maybe something different in our systems.
-
Yes,can confirm all scans now start within a couple of seconds again,although the message "initialising engine,please wait" is still there briefly.Has that message always been there and I didnt notice?
Regards
-
Glad to know the latest beta solved this.
-
But everyone in the thread said it was fixed by the VPS update.
Nobody in the thread said the latest beta fixed it - the beta just made no difference.
-
Not to mention the OP didn't have the beta build installed and some others, olddog even restoring did this:
Did complete uninstall of build 4.8.1187, ran aswclear.exe from boot into safe mode.
Installed released version 4.8.1169 and updated VPS to current 080506.0.
Which basically confirms this would appear to have nothing to to with the beta but a VPS issue as stated here and as I mentioned earlier also as I was on the beta in my previous scan with no issues.
So It would seem that my last scan on Sunday didn't suffer this delayed start as it was in a little over 12 minutes. So the suggestion this might have something to do with a VPS update is one that might carry some weight as there are other functions carried out other than simply updating the VPS.
-
Nobody in the thread said the latest beta fixed it - the beta just made no difference.
Tech
Have installed 4.8.1192.
Beta release ???
-
Tech
olddog already posted posted, several hours before:
Yes, I can also confirm that the problem is no longer present. So it wasn't there with VPS update 080505-0, it was present with 080506-0 and gone with 080507-0. Looks like it was something in 080506-0.
The later post from olddog was simply comparing scan times with the latest beta versus the old production release. It did not report that the beta refresh fixed the problem.
-
Tech
olddog already posted posted, several hours before:
Yes, I can also confirm that the problem is no longer present. So it wasn't there with VPS update 080505-0, it was present with 080506-0 and gone with 080507-0. Looks like it was something in 080506-0.
The later post from olddog was simply comparing scan times with the latest beta versus the old production release. It did not report that the beta refresh fixed the problem.
You win ::)
-
Not a case of winning - just did not want anyone to think that the latest refresh was needed for this problem.