DanielJUK 0 Posted June 16, 2021 Share Posted June 16, 2021 Hi, I have a really old Windows 7 machine which is not my main computer and I use the old Windows Live Mail 2012 on it as really an archive for my email. It still works fine until the computer updated to Internet Security 14.2.10.0. After restart, it now illegal errors on start. It was working fine up to that moment or restarting for the update. I turned off the email client integration and it opens again without crashing. So I can access my email boxes. But now sending and receiving ends in popmail failure. I have tried turning off the pop3 scanner and also disabling firewall and protection. It just can't seem to connect anymore to send or receive. Could this be a bug in the new update? It was working fine until eset updated. WLM does not seem to be corrupted and there is internet access on the machine. I can load websites. Any ideas? I wanted to report it in case anyone else is affected by it. Dan Link to comment Share on other sites More sharing options...
Administrators Marcos 5,092 Posted June 17, 2021 Administrators Share Posted June 17, 2021 The issue has been narrowed down to Deep Behavior Inspection and we are investigating the cause. Creating a DBI exclusion resolves the issue in the mean time. Link to comment Share on other sites More sharing options...
DanielJUK 0 Posted June 20, 2021 Author Share Posted June 20, 2021 thanks @Marcos this is why I always stay with Eset the support is excellent I have been trying to work it out myself and also have an old Win7 laptop with a licensed Internet Security. When I turned it on and it updated Eset to the latest version, it immediately caused the same problem with Windows Live Mail. So I could reproduce it. I tried turning on pre-release updates but they didn't solve it. I solved that connection problem on the first computer though because it was not happening on my old laptop. Turning off the client integration allows me into the mail programme. I looked at the pop3 error message code (it fails immediately, doesn't even try to connect to the net) on google and it turns out it means the message list is corrupt. I found a simple registry change which makes WLM rebuild the message list and it connects fine now! So the problem is just with the spam integration only. I will have a go with the DBI exclusion. Is it the setting under HIPS and then I add windows live mail to exclusion under Deep Behaviour Inspection? I will give this a go and then see if I can use the spam integration again. Thanks Link to comment Share on other sites More sharing options...
Administrators Marcos 5,092 Posted June 21, 2021 Administrators Share Posted June 21, 2021 8 hours ago, DanielJUK said: Is it the setting under HIPS and then I add windows live mail to exclusion under Deep Behaviour Inspection? Yes, that's the exclusion list that WLM should be temporarily added to. Link to comment Share on other sites More sharing options...
Radnon 0 Posted June 25, 2021 Share Posted June 25, 2021 Hi, For few days I have the same problem with Windows Live Mail 2012 on Windows 7 64bit (program keep crashing on startup with error message) but still using Eset 14.1.20. DBI exclusion seems to resolve issue temporary. Can we get some new info about official fix? Thanks! Link to comment Share on other sites More sharing options...
Administrators Marcos 5,092 Posted July 5, 2021 Administrators Share Posted July 5, 2021 The issue is still being analyzed. Please use the work around suggested above. Link to comment Share on other sites More sharing options...
100 2 Posted August 18, 2021 Share Posted August 18, 2021 Hello, I have had v14.2.10 for months/weeks, then .19, .23 and now .24 and no problems with Windows Live Mail on Windows 7 x64. Only since today it occurs after a system reboot. Previously I had done an on-demand scan ("scan only, no action"). Selected were only the drive for backup files (not c:\), memory, boot sectors, WMI database and registry. Then did DBI not work at all before because of inplace updates and was only enabled by the on-demand scan? The exception of wlm.exe in HIPS DBI works as a workaround, but a fix would of course be better. Can we still hope for it, Marcos? That would be really nice! Link to comment Share on other sites More sharing options...
Administrators Marcos 5,092 Posted August 18, 2021 Administrators Share Posted August 18, 2021 2 minutes ago, 100 said: The exception of wlm.exe in HIPS DBI works as a workaround, but a fix would of course be better. Can we still hope for it, Marcos? That would be really nice! The issue is being investigated so it's not clear yet what will be the ultimate solution. Link to comment Share on other sites More sharing options...
100 2 Posted August 18, 2021 Share Posted August 18, 2021 Hm, thanks for the quick reply. It's strange that I've only had the problem since the on-demand scan. Link to comment Share on other sites More sharing options...
100 2 Posted August 19, 2021 Share Posted August 19, 2021 6 hours ago, 100 said: The exception of wlm.exe ... wlm.exe wlmail.exe Link to comment Share on other sites More sharing options...
saintsuperb 0 Posted October 13, 2021 Share Posted October 13, 2021 I could not get the wlmail.exe exception to work. I had to disable deep behavioral inspection to be able to use Windows Live Mail. Link to comment Share on other sites More sharing options...
100 2 Posted October 14, 2021 Share Posted October 14, 2021 This works fine for me. Did you do it differently? Link to comment Share on other sites More sharing options...
saintsuperb 0 Posted October 14, 2021 Share Posted October 14, 2021 Wow! Thanks for your post! Yes it does work fine. I did not have the full path. I only had wlmail.exe. Thanks for bringing this to my attention! Link to comment Share on other sites More sharing options...
100 2 Posted October 14, 2021 Share Posted October 14, 2021 I thought so. I think wildcards don't work there, but are still accepted as input. I'm glad I could help you. Link to comment Share on other sites More sharing options...
Recommended Posts