Nod32 v4 blocks Messenger Live

I did a clean-up on a pc last week, but found later that Messenger Live was no longer working. General Internet access was fine, as was Skype. After a lot of checking - including removing the bloated "Live" suite & reinstalling, it still didn't work. As a last gasp, I removed Nod32 & Live started working immediately. (As part of my clean-up, I had updated the Nod32 from v2.7 to v4.) I then installed Nod32 v3 which still had the problem, so I went back to v2.7 & all is fine again.

 

I also experienced this difficulty loggin in Windows Live Messenger with v3, sometimes can login, sometimes cannot

 

Hello!

I have Live Messenger (the latest version) and have used prior versions on our computers with Windows XP (SP3). They both use ESS v3 and never had problems.

What about trying again with v3.0 and excluding the application from being scanned or web traffic from being filtered:
http://kb.eset.com/esetkb/index?pag...earch&viewlocale=en_US&searchid=1242048730691


ASpace

 

Thanks, it's a customer's pc. I don't have the opportunity to go back & mess about again.

It was EAV 4 that messed it up. I suspect that EAV 3 just picked up some setting from the registry,

 

Yea, I had trialled v4 before reverting to version 3 that caused this mess of a registry and problem.

 

I'll have to install it on my kids pcs then(lol)

 

You are lucky not to have install or trial v4 on your computers, otherwise, you will join us on this frustrating nag problem.

Does anyone has any idea what in v4 might have caused this ? What other registry keys or folders or files to delete than those mentioned in the "manual uninstall Eset NOD32" KB ?

 

I have installed even BETA versions of v4 on these XP computers I talk about but everytime I have done this , I have "cleaned" them (uninstallation , reboot , deleting ESET folders , deleting ESET keys/reg entries... , etc) . Now v3.0.684 of ESS works great for them .
I have "trialed" v4 because I resell ESET products.

 

Big thanks to Aspace and DesertRat I've identified the culprit and solved my Windows Live Messenger (WLM) login issue !

The culprit lies in this ESET KB solution ---> http://kb.eset.com/esetkb/index?page=content&id=SOLN549

It says add the line :
'C:\Program Files\ESET\ESET NOD32 Antivirus\ecls.exe' --log-file=log.txt --action=clean

This caused and started the problem with WLM login.

I've since changed to using DesertRat's line :
"C:\Program Files\ESET\ESET NOD32 Antivirus\ecls.exe" /clean-mode=strict /quarantine

This big (trivial) difference is in the punctuation marks, have you spot the difference ?

All's back to normal and working well now