Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: adi_dmj on October 27, 2008, 08:29:29 PM
-
win xp sp3
avast 4.8 home
I have a strange problem with avast when i click on blue ball in tray and start the program it scans the memory (shows a flash screen) but does not start on checking the taskmanager ashsimple.exe is found running but no user interface is there.
To correct this problem i had even tried reparing the program from control panel add/remove program
however the nature of problem is intermitant it happens mostly (not always) after vPS updates
if you click on ashsimple.exe in avast folder the program starts immediatly
however clicking on trau icon doses not always. it is a serious bug in program related to services not intracting with desktop
I think the dev should take note of this problem
Regards
adi
-
Well, this has obviously nothing to do with services interacting with desktop, as there are no services affected here (ashsimpl.exe is an ordinary program). ;)
Anyway, could you please create a dump of the "invisible" ashSimpl.exe process, as described e.g. here (http://forum.avast.com/index.php?topic=33616.msg281371#msg281371), and upload it to our FTP? (preferably after compressing it into an archive).
It is necessary to disable avast! self-defense first (avast! Settings / Troubleshooting page), otherwise the dumping will not work. Thanks.
-
Just to test, I suppose that if you run ashSimp2.exe from avast folder, it will start...
If you change the skin (downloading a new one), will it help?
-
good evening to all
ashsimple2.exe runs fine. No problem faced
I have just uploded the dump of "invisible" Ashsimple.exe to ftp,
since this invisibe behaviour does not happen always hence the delay.
This dump was created when using computer as limited user
regards
Adi
-
Hi, I see you're using McAfee SiteAdvisor. Do you think you could do a small experiment?
Try uninstalling this application, and see if it resolves the issue.
This is not meant as a fix, just trying to make sure this is really a conflict between avast and SA.
Thanks
Vlk