Avast not working properly atfter update

High,

I did an update on Avast last night and since then have some problems.

Now I have 4.7.936 and the following problems:

I have a file with a test virus. With the last AVAST version, every time I clicked on the file,
a warning poped up, AVAST played the Warning-Sound-File and showed me a dialog,
whereher I could choose what to do with the file.

Now, with the new version, I get the “Blue-Red on Yellow” pop-up, telling me that AVAST
found a virus and thats it. No dialog-window asking me what I want to do, no sound
telling me that there is a virus!

I uninstalled AVAST, rebooted and reinstalled - that didn’t solve the problem.

Any ideas how I get Avast back to “normal” functionallity?

Thanks

Reiner

PS:
In the log I get:

14.01.2007 21:37:43 Reiner 1712 AAVM - scanning error: CallGuiVirusProc: unhandled exception!, 00000000.

every time I try to scan the file!

The virus dialog…

Isn’t this the popup message right above the system tray area (near the system clock)?

As a workaround, to now see the messages, add the file to the Exclusion lists:

For the Standard Shield provider (on-access scanning):
Left click the ‘a’ blue icon, click on the provider icon at left and then Customize.
Go to Advanced tab and click on Add button…

For the other providers (on-demmand scanning such as the screen-saver or the Simple User Interface):
Right click the ‘a’ blue icon, click Program Settings.
Go to Exclusions tab and click on Add button…

You can use wildcards like * and ?.
But be carefull, you should ‘exclude’ that many files that let your system in danger.

Maybe you misunderstood me.

I want AVAST to show me the virus dialog! Since the update, it is not shown anymore.
How can I get the dialog back?

Yes, the popup is right above the system tray area, thats OK.

But that the virus dialog and the sound are NOT working anymore.

Reiner

No… we’re talking the same…

If you boot the computer, will the first time on next boot work properly?

Just rebooted the computer, no changes.

Just the Blue-Red on Yellow warning.

No sound, no dialog.

Sorry

And the same error in the log-file

Sorry,

the error in the log is a bit different:
14.01.2007 22:39:24 SYSTEM 2016 AAVM - scanning error: CallGuiVirusProc: unhandled exception!, 00000000.

Reiner, I need Alwil team support… can’t imagine what’s wrong… ::slight_smile:

OK,

I’ll check back tomorrow.

Look at http://forum.avast.com/index.php?topic=25983.0
it seems to me, that I’m not totally alone, at least concerning the sound.

Thanks

Just performed another test:

I right-clicked on the test-virus-file and had it checked doing a check with the
explorer context-integrated virus scan. There I get sound and the dialog box pops up.

If I do a right-click and then select “file properties” I just get the Blue-Red on Yellow warning.
No Sound, no dialog box.

Maybe that helps

Reiner

Update to the newest release this morning.

No changes, still no sound, no dialog!

Reiner

can u post the URL to download the test file so i can see the problem and understand what’s wrong?

thnx :wink:

Just use the eicar test virus file.

E.g. from Trendmicro: http://de.trendmicro-europe.com/enterprise/security_info/testfile.php

It is not a problem with the file. A “real” virus file I have, shows the exact same behaviour.

I get the message above the taskbar, but no sound and no dialog box asking me what to do.

If I scan the file directly with avast (via the explorer contex menue) there is sound and the dialog box pops up.

Reiner

Stay tuned, please… an update is coming soon.

When about?

I’m just curious …

Please check the new build:
http://forum.avast.com/index.php?topic=25697.msg212717#msg212717
and let us know if it helps…
Thanks!

Great work!

Everything back to normal

After I downloaded and ran the Beta, rebooted, and everything is OK again

Great Work

Reiner

OK, thanks for your help.

i just wanted to see the behaviour…when i try to download this file a pop up appears with the option “abort conection”…this is the normal behaviour of avast…glad ure ok now :wink:

This is the normal behavior (not Silent Mode) when WebShield detects an infected HTML traffic.
Before the file is saved in the HDD, you can abort the connection to that ‘file’.
Anyway, Dr. Web says this file is clean… ::slight_smile: