New BETA 4.5.536 - hopefully solving many of the issues...?

[CoJo]

After a few days of things working right, this morning it was back to "internet mail waiting for a sub system to start// 7 providers, 5 running"
reboot, then cold start did not solve it

so I downloaded the patch/fix (?) and it's working fine now.
 

cojo

[Eddy]

The subsystem is your email client. As soon as you start Outlook (Express) you will see 6 out of 7 providers running.

If you open the on-access control panel you will see Outlook/Exchange and the Internet mail provider waiting. And they are just waiting for you to open the email client.

Nothing wrong if the mail scanning is setup correctly, so don't worry.

[CoJo]

The subsystem is your email client. As soon as you start Outlook (Express) you will see 6 out of 7 providers running.

If you open the on-access control panel you will see Outlook/Exchange and the Internet mail provider waiting. And they are just waiting for you to open the email client.

Nothing wrong if the mail scanning is setup correctly, so don't worry.

Eddy...I think you are replying to me?
No, when I opened OE, it still showed 5 of 7 providers running with internet mail waiting for a subsystem to start. And my email did not have all the "clean scanned message" info at the bottom of them.
I downloaded the fix and it is now working properly. I was surprised that it started doing it again after working all right for several days.
 cojo

[S.Z.Craftec]

OK, problem is solved... guys and girls, be serious for a change ! Let's go back to sex topics now !!!          

                             
Jokety-yokeety !!! I'm so happy you (CoJo) solved your problem ! Great news !

[bob3160]

wasid
Welcome to the forum.
If your not running the latest version of avast! then please go HERE and follow the directions to install version BETA 4.5.529.
Let us know how you make out.

[wasid]

wasid
Welcome to the forum.
If your not running the latest version of avast! then please go HERE and follow the directions to install version BETA 4.5.529.
Let us know how you make out.

Ok, ive installed 4.5.529 but i get the same problem. Every time the ashServ.exe service is run, explorer.exe just stops responding. So when i try and use the taskbar or right click on the desktop, i end up having to reset the computer.

[igor]

There's a new build out (531) - could you try it, please?

[housi]

How many entries do you have already inside ?

I'd 12 entries, the false is the 13th.

I've downloaded Build 531. The bug is still present.
MfG
Housi

[wasid]

There's a new build out (531) - could you try it, please?

i still have the problem, its not as bad though. whenever i right click on the desktop it stuffs up, but im now able use the taskbar.
I still get this error in the event log:

AAVM - scanning error: FATAL: GetQueuedCompletionStatus failed!!!!!, 0000007A.  

[Vlk]

wasid, this is very very strange. Can you please check that the following two files both have the file version of 4.5.515?

\Windows\System32\Drivers\aavmKer4.sys
<avast>\Aavm4h.dll


(To show a version of a file, open its Properties in Explorer and go to the Version tab).

Thanks
Vlk

[bob3160]

Vlk
I just checked mine and the driver is v. 4.1.357
The other is 4.5.514
Remember, I'm not having any problems that I'm aware of.
Hope that helps

[Vlk]

housi, there's a size limit for the total size of the expception list and if think it's about 255 bytes... Unfortunately, to extend it is not so simple because it's a limitation of the ODBC storage (I'm not saying it wouldn't be possible, it's just not as trivial as changing this 255 constant somewhere).

Try switching to the XML storage, it may actually help (see e.g. http://forum.avast.com/index.php?board=2;action=display;threadid=8795;start=msg72526#msg72526 for instructions on how to do this). Please note that changing the storage type will probably reset all your customized settings.

[Vlk]

I just checked mine and the driver is v. 4.1.357
The other is 4.5.514
Remember, I'm not having any problems that I'm aware of.

I'm sorry, of course you're right. The version number of aavmker4.sys probably hasn't changed (our fault) so please instead of checking the version of this file, check its size.

It should be approximately 14,784 bytes (as opossed to about about 13,248 which it was in avast 4.1).


Thanks
Vlk

[igor]

It should be approximately 14,784 bytes (as opossed to about about 13,248 which it was in avast 4.1).

Approximately 14,784 bytes means the size actually has a fractional part? A couple of bits more - something like 0.375 byte?  Sorry, couldn't resist

[S.Z.Craftec]

Hihihi...