Beware also of KB2790655!!!

I have verified this on two different machines.

Problem Replication:
1. Install any one of these: KB2790655, KB2735855, or KB2750841
2. Open Internet Explorer 8 or 9 and go to http://www.msn.com
3. Type anything in the search bar at the top of MSN's webpage and hit Enter
4. Bing will launch a separate window, but the connection will fail and will only display an error message (sorry, I don't recall the exact error message). Refreshing does not help.
5. Disable Eset NOD32 and step 4 works . Re-enable Eset NOD32 and step 4 doesn't work .
6. Remove all of the previously mentioned patches and step 4 works like it's supposed to.

Hopefully this gets added to the other KB Announcement!

Thanks,
Brett

 

Did you try installing KB2789397 yet?

 

Yes, it does nothing for me. I think the problems others were having with those patches were different than ours. However, it may be the same, but a different symptom that I was experiencing.

Kind Regards,
Brett

 

Does help OP, but it works fine here on Win7 64-bit, NOD32 5.0.2126.0. All those patches are installed (latest one installed Feb 13th, 2013).

 

We have not migrated to v5.0 yet. We're still using v4.2.76.

Kind Regards,
Brett

 

Just to clarify, this problem appears to only affect version 4.x. I loaded up version 5.0 along with the patches KB2790655 and KB2750841 and the problems that I was experiencing went away.

Also, It appears that Microsoft has possibly removed KB2735855 from being delivered via Windows Update. At least, after a clean install and fresh patching, it was not installed.

Is there a chance that a patch will be rolled out for the version 4.x series for this problem that fixes the problem I described in my first post?

Thanks,
Brett

 

I, for one, haven't heard of any other user with v4 reporting an issue with KB2735855 and KB2789397 installed.
V4 is not developed any more and fixes and improvements are made only to current versions of Endpoint.

 

Thanks for the reply. I'm pretty sure if you were to follow my instructions from the beginning of this post, you'd also see the problem exists.

I realize that the business version 5.0 has been out for a little while now and I appreciate that Eset decided not to bring it out at the same time as the Home version. With version 4.x we always felt like we were on the bleeding edge (instead of the leading edge) with all the problems that we ran into (I'm sure there are many who would agree). So, you'll have to forgive me if I'm hesitant to upgrade to the latest version when the current version 4.2 works pretty much without any problems (except for this one). I guess at this point I have no option but to upgrade to version 5 to fix the problem.

Kind Regards,
Brett