Windows Live Mail crash

Ok, I worte to local support that in 4.2.35 is not working and as an anwser I get..

"You can download 4.2.35 from our site (it'll be available till next friday). It should be fixed in that version."

So can anyone confirm this bug under 4.2.35 too?

 

Crash confirmed for ESS 4.2.35.0 on xp sp3 x86 and Win 7 x64.
Win 7 eventlog:

Same problem I've had all along, I guess it's a result of timing/subclassing in that the WLMail menu is created twice, but no ESS menu.

I'm glad I've had it disabled.

 

Hello,

Can you please Marco the information he outlined in this earlier message? That will be helpful in investigating the issue.

Regards,

Aryeh Goretsky

 

Twicely created WLMail menu and no ESET menu. It happends only with ESET EAV or SS installed (it's from my mails with eset support)



Also please provide the following information:
1, what protocol you use (POP3/POP3S, IMAP,...)
A: POP3 / POP3S

2, which of the following makes a difference:
- disabling antispam protection
A: doesn't help

- disabling POP3 checking in the main setup tree (F5) -> Email client protection -> POP3,POP3S -> untick Enable POP3 checking
A: doesn't help

- disabling integration with the email client
A: doesn't help

- installing EAV instead of ESS (try if possible)
A: doesn't help

3, what version of ESS you use (in this case it's clear that you use the last one 4.0.467, but it's crucial information if anyone reports a problem now or in the future)
A: 4.0.467 (EN and PL / EAV and SS) and 4.2.35 (EN / EAV)

I provided files to local support (SysInspector only, dumps where 200mb+ and they gave up - didn't ask anymore).

 

Version 4.2.40.10 (PL / EAV)
First thing after installing 4.2.40 and running WLM was.. 0xc0000005 error.
So I gave it second chance.. cold reboot.. running WLM and.. 0xc0000005 error.

Hopefully it's turning on.. without that error so I can check mails.. I bet in next version it will crash everytime I run WLM so I won't even be able to write an e-mail to support.. no case - no problem.

Bot there's something new! Top menu is not anymore created twicely..


Can anyone else confirm it too?

 

Ok I finally solved it!

My licence is out of date and I unsintalled nod. No more crashes

Ach, and uninstaller seems to be f-_-ed up too, had to manualy remove eamonm.sys from services because my system at every boot up wasn't able to start that service (file was removed by uninstaller earlier).