Getting this Error after Update

Hi igor,
I posted my Registry info on my original post:

http://forum.avast.com/index.php?topic=17560.0

Thanks,
Acco

Late Edit/Update:
I'm posting my reg info screenshot here, and abandoned my post (link listed above), as jd500 started this problems thread here,, first.
Note: This popup only occurs on a Limited User account (WinXP), and not while trying to scan in an Administrator's account.

Hi,

HKLM\software\clients\mail
contains
(default) RG_SIZE Outlook Express

HKLM\software\clients\mail\Outlook Express
contains
DLLPath RG_EXPAND_SZ %Program Files%\Outlook Express\msoe.dll

I hope this is the info you wanted.

As I said, this error only occurs in the only limited account on this machine.

Igor,

just did some testing with another user who was experiencing this error message.

We both have Thunderbird set as the default mail client so our “Default” and dllpath were identical.

The only difference between us is that he has a subkey:

HKEY_LOCAL_MACHINE\SOFTWARE\Clients\Mail\NoMailClient

set to:

Either there is no default mail client or the current mail client cannot fulfill the messaging request.*Windows Messaging

This subkey is not present on my system and I have not experienced the error message. He could reproduce the error message at will with this subkey present. When he removed the NoMailClient subkey the error message no longer appears.

I notice that in posting his registry info that user Acco did not have the NoMailClient subkey. He did have another subkey that is not present on my system.

My registry simply has the Default and the PreFirstRun subkey.

Hope this helps.

I’m afraid that is the same as mine. There is no NoMailClient subkey either. And I don’t have LastUserInitiatedDefaultChange like Acco.

OK, guys, try this file, please.
Go to avast! installation folder, rename aswEngin.dll to something else (e.g. aswEngin.dl_) and extract the content of the archive to the folder.
I hope it should fix the problems.

If file is in use, you need to stop avast, rename or even use Unlocker tool.

No, you don’t :wink: - at least not in NT/2000/XP.
That’s why I wrote to rename it first.

Thanks Igor, that has solved the problem :smiley:

One question though, do you recommend keeping this new version or should the old version be restored?

Thanks again.

I just couldn’t rename… file access denied by ashserv.exe.
I’m using, as you know, XP SP2+
Only with disabling avast and using Unlocker I could rename and copy the new files there.
How can I test if it is working?

You can safely keep the new version.

Don’t know… it works for me. I even tried on SP2 right now to make sure that it wasn’t changed recently (I don’t use SP2 personally), but it’s OK. You can rename a running executable/DLL (even move to a different folder within a partition).

Well, if the error message appears for you (with the build 731), it should disappear now. If it doesn’t… it’s probably not necessary to use this version. No idea how the error can be “invoked” if it doesn’t show by itself.

Just by way of confirmation …

I asked a user who could could reproduce the pop-up error message at will to install the update. Once installed on WinXP SP2 (he reported he needed to terminate the active avast processes before being allowed to install the update) and avast was restarted he is no longer able to produce the pop-up error message.