SweX

Hi Chris Yes they will just fine. You can actually have how many on-demand (second opinion) scanners that you like, as long as they are on-demand scanners they shouldn't cause any conflicts with ESET at all. So having 5 different on-demand scanners sitting on your desktop shouldn't cause any problems. Like an example. But IMO you're fine with just HitmanPro and Malwarebytes.

No problem, happy to hear that it sorted itself out sometimes it does that too

Not sure where you heard that but the interval is bigger. Ok here it is: https://www.wilderssecurity.com/showpost.php?p=2200547&postcount=14 Though you didn't say every 3-5 min, but "every few minutes". It was these updates I was referring to. But maybe you thought I meant some other type of updates? Bump bump. Sorry for bumping but I really would like an answer to this to clear things out a bit. Because it feels wrong knowing I have said this if it's not true facts.

Yes indeed the bold part will work great as far as I know. You shouldn't encounter any issues doing it that way.

What exactly are they detected like? I think it would be good if you could send a couple of these files to ESET for analysis to see if they really are FP's or not.

And/or try clicking the update button manually a couple of times in a row sometimes fixes this too.

Exactly, it's not really that NOD32 AV is incompatible with the "firewall function" in outpost, it's that Outpost Firewall Pro is a very feature rich firewall, and as I said in my first post the more features it has the bigger the chance that it will argue with some of the essential functions in NOD32. Wich is why I also said, chose a firewall that is a firewall, and not a a firewall plus 5 additional features. The new features in NOD32 V7 is great features and not meant to be disabled. And I also think that it is probably easier for Outpost to tweak their firewall and the additional features than it is for ESET to start testing their AV with 15+ firewalls to make sure it is working with them. And No ESS was not created as a replacement for NOD32. Many NOD32 users let their hardware firewall handle the firewall bit, and on the software side the Win OS firewall. Not all NOD32 users use a 3'rd party firewall because NOD32 doesn't have one.

Hmm I see. It's just that I thought about what would happen with a PC that only got 512MB to begin with...not that I know of anyone having that little these days

Same here. FWIW when I renewed my license this past July I received the email just fine. It didn't even end up in the Spam folder.

But it looks like 7 replies by ESET mods on the first page in this thread is not enough. Instead it have evolved into a "I know best" type of discussion.

You're welcome Chris.

First you said your opinion, then Arakasi said his opinion, and after that you called him a fanboy and that he was defensive. So it was you who didn't accept his opinion I would say. Now let's leave this behind and let ESET develop their software shall we.

I agree with Arakasi. ESET knows their software in and out, and have developed and improved their software/s over a long period of time. And if there would be something they can do to make it run better, faster, more effective or whatever they would of course already have done it to the products. Norton360 uses less resources in what way exactly? If it is about the "low" RAM usage then i'm not interested, too many discussions about that already. If not then go ahead tell us more Fanboy this Fanboy that LOL! Arakasi likes the software and how it runs on his machine, and so do I for that matter. If that makes me a fanboy then so be it. Great software = happy boy! And I hereby officially ban the word Fanboy, it is overused everywhere these days.

The site to check for that is: hxxp://www.eset.com/us/beta/ Where all available BETA products are listed for both Home & Business. Cheers

FWIW ESET is still scanning in realtime even if he disables AMS (advanced memory scanner) wich only scans in the memory afaik. And if disabling AMS indeed makes a difference, then that's all he need to do. Though AMS shouldn't really create issues like this while playing I think. But let's wait for an official ESET reply to see if there is a better workaround than disabling features.

@gooberbear, Yeah memory leak or not, all I can say is that, that memory usage is not anywhere near the normal amount that the ESET process should be using. It's using around 1,3GB if I read it correctly wich is around 12 times more than it should be Maybe (hopefully) ESET will request you to make some logs about it so they can take a look.

Welcome Fred. No problem at all. The more you read and write English the better you will get. Several members in here including me, don't have English as our first language and we're doing just fine I think.

@btm Welcome to the forums. You mention that you have disabled the Web protection module in NOD32, wich is the first and one of, if not the most effective layer in the product. As ESET is very very good at detecting and blocking threats/malware at the source itself. So with that layer disabled you have decreased the protection and detection capability in the product significantly. I just wanted to mention that so you are aware.

Hmmmmm.....harsh mood. 1. Regarding Matousec. It is NOT a firewall test but a HIPS test, check some facts before complaining will you. 2. Change firewall, upgrade to ESS for a small amount and get a product that works great, or return the product. How can you say that it is a bug when you're not using NOD32 AV on it's own? If NOD32 works great on it's own but the problems start when you use it together with Outpost how on earth is that ESET's fault? The latest V7 and outpost are not good friends anymore because of compatibility issues due to changes and improvements in V7, wich have nothing to do with a bug in ESET software as you think. Try using NOD32 AV on it's own to see if you experience any issues. Next time, it may be Outpost that release a new version wich will break compatibility with ESET software instead, then you can go to Outpost complain and tell them to fix it. No you shouldn't. Because Outpost knows that their firewall works great on it's own, like ESET knows that NOD32 AV works great on it's own. It's when you combine them that the issues show up wich isn't Outposts or ESET's fault, it is you that insists on using them together. All AV's and firewalls don't work well together. That's the disadvantage of using a standalone AV that you need to find a 3'rd party firewall that get's along fine, but sooner or later a product update to the AV or firewall may start to cause issue. Unless you would use the Win firewall wich wouldn't cause any issues at all. I use ESS. But if I were to use NOD32 AV with a 3'rd party firewall, I would chose a firewall that had the least features as possible except the pure firewall function to minimize the risk of compatibility issues with the AV. In Outpost...... And what you need is the feature at the top, the firewall function. For a test, try to disable everything except the firewall to see if it makes a difference. I suggested you to try another 3'rd party firewall since there is a good chance it will work better with NOD32, there are several good FREE firewalls around. But if you still want to use NOD32 & Outpost, have you tried exclusions? I didn't mention that in my last post since I thought you would have tried that already. You also say that the AV doesn't have the best detection rates, well I won't even get into that discussion since you will probably not believe what I or others would tell you anyway. ESET makes sure that their products works great on their own and that's all I can ask for as an ESET customer IMO.

Yes and No. This is the ESET forum, and discussing AV's from other vendors is probably not a good idea, since users come here to talk about ESET, and get advice and support with issue they may have with the software. And the forum can be cluttered with threads about other vendors products. Same as if you would talk about ESET and other vendors on Bitdefenders forum, it would also not be a good idea since their forum is about their own products. But a forum such as Wilders Security Forums, where you have a dedicated section for AV software, AM software, where one is allowed to discuss AV's from all vendors is a better place to discuss Antivirus software in general. And maybe this thread could be moved to General if we're going to continue. In my opinion anyway

You could also try another 3'rd party firewall instead of Outpost wich may work better together with NOD32.

Yeah well my browser version is old and so it doesn't support the new standards very well so that's probably why it crashed. But I still like to blame flash player since that is usually the cause for my browser crashes, and I hate it so much it is getting bigger and bigger for every release and the stability that were there in version 7.0 or 8.0 long time ago is no where to be found. And it causes massive ram usage on some websites. I just hate it

And that's yet another thing I like a lot .NET is not something I like.

Hi tommy. Yeah now I remember, it was when the PC had been on for a long time that this could happen just like you say. But no, I am not like you, I shutdown my computer at night or if I am not going to use it anymore that day.

In that case I understand. Well yeah it can't hurt I guess. Or maybe simply add a checkbox in the advanced setup tree under (Update) same place where you can change your license, enable/disable pre-release updates etc etc... "Ticking this box will exchange "activate your product..." with "check for updates" in the tray menu."