Should I be able to surf or chat whilst running an Avast (free) scan in standard mode? I noticed it has frozen a couple of times and have had to end the process in Task Manager. The scanning works without a hitch with no sites or messengers active.
What operating system do you use? What was the exact process name that you killed?
XP2
The Avast virus scan prog
OK, but what was the exact name of the process?
Heh Igor, do you think I remembered it? However, I started the scan again and on looking at Task Manager processes, I see ashSimpl.exe there.
Hi Greenhatch :
Being a security-conscious person, I run all my security
programs while NOT on the internet .
Hi greenhatch,
Could this be it:
http://www.trendmicro.com/vinfo/virusencyclo/default5.asp?VName=WORM_BAGZ.C&VSect=T
and consider:
http://www.mcse.ms/archive177-2005-4-1544608.html
polonus
Polonus, if it’s malware causing my scan to freeze, we are all in trouble. No, I think it is just because I had a couple of things running and surfing; probably the scan program prefers to be alone when working on the harddrive :o
Though I await further word from Igor…
Well, yes, ashSimpl.exe is the “Simple User Interface” scanner - but was it frozen? Previously, were you also running a on-demand scan? (I wasn’t sure if you’re talking about the resident protection maybe?)
If it wasn’t frozen now, I’d simply suggest to wait until the next lock-up occurs and then note the exact name of the process and post it here.
Btw, how long did you wait until you claimed the program to be frozen? Were you able to move the window with your mouse, for example (when it was “frozen”)?
Igor,
I did keep the Avast resident scanner on whilst running the virus scanning of the harddrive. And I was able to move the cursor when the scanning of the harddrive froze. It would have been maybe two minutes before I noticed the scanning had frozen and it said ‘not running’ in Task Manager applications, so I stopped it in processes.
I then closed the sites and chat programs, restarted the scanning and it did complete ok in the usual 20 minutes.
Hi greenhatch and igor,
I’d like igor to comment on the following exerpt. Why they mentioned that or is that a thing from the past? Or is this not related to this specific problem.
Someone on alt.comp.anti-virus kindly referred me to the Avast forum at
http://forum.avast.com/index.php?board=2.0
A search of the forum messages turned up two possible solutions: update
the Windows ODBC database files, or change a line in avast4.ini from
“Database=ODBC” to “Database=XML”. Since the second suggestion seems
simpler, I have started with that one. If these don’t work I’ll check it
out in safe mode as you suggest.
polonus
polonus, I don’t think the storage type could have anything to do with that.
It occassionally causes problems when starting the scanner (because the settings cannot be loaded from the storage), but not like this. Anyway, we hope all storage problems will be solved in 4.7 
I finally got fed up with the Avast scan freezing part way through, having each time to end the process via Task Manager. So I have uninstalled Avast and reinstalled it and will advise if the reinstal freezes on scan later this week.
Igor, will be another storage method - besides XML and ODBC - or this refers only to internal (management) procedures?
greenhatch … how much ram does your computer have? You may be using up your computer resources by scanning, keeping too many “things” running, and surfing.
I have 480 ram, Charley, but anyway, I did the last two virus scans on the ‘old’ instal without any programs, sites or messengers on…still froze. I’ve scanned the once with the new instal, that completed ok.
Igor or Vlk
The scan of my Avast Home 4 froze yet again, this time, on the new instal. I was scanning on standard, on drive C, no net connection. I am running Ewido and Windows Defender. I have therefore uninstalled Avast again and installed for a third time! Is there any reason you can think of why the virus scan should keep freezing? Is Avast compatible with Ewido and Windows Defender?
Can go to the program settings and turn on the creation of the report file (with “OK files” to be included as well in the report). This way, you can find out where the scan really stopped (it’s going to be close to the end of the report).
After avast! disappears, check the end of the report file - the “troublesome” file is likely to be close to the end (close in the sense that this particular file will probably not be written in the report, but the previous one will be the last line, so it shouldn’t be hard to guess). We would certainly like to have this file - if it really causes problems to avast! - so that we could fix the problem.
The report file created (if you turned it on in program settings) will be (default location) at \Data\Report\Simple User Interface.txt
With ewido, no trouble.
What is WD? ???
Tech thanks. What you’re saying is it might be a bug or fault? Even if it is the third new instal? (And Windows Defender is WD of course).
Maybe a fault in that precisely file.
Maybe a bug (or problem) into avast.
If we know more about the ‘last’ scanned file… maybe we can do more research about the problem.
Oh… not used (yet) to that letters.
No conflict with avast.