Re: Future Changes to EAV 3.0 I don´t know if it´s been said before (I didn´t check), but a "Quit" or "Exit" button like version 2.7 had would be nice... I use it as an on demand scanner only, and it is a pain to be unable to quit the program after running a scan...
Re: Future Changes to EAV 3.0 The animation is definitely required - I would certainly like to know whenever my NOD32 is upto something.
Email response after sample submission It would be great if Eset labs respond the users through email, about the status of detection of the samples sent by the users....like most other AV companies does. I've been sending several undetected (malicious) files to the labs but I never get a response from the labs.....at least they should throw back a small email stating that the sample has been added to the detection bases.
Re: Email response after sample submission They could add a feature to do "remote scanning". As in, scan 1 computer from another with the first computer not accepting non-nod32 inbound connections. It's possible to scan a computer's HD remotely right now, I've tried it, but it would take some coding to acutualy make it reject all non-nod32 connections.
Re: Future Changes to EAV 3.0 I would like to see the ability to add file exclusions based on an MD5 checksum. AND!! the ability to post these MD5s to the RA server for the clients to synchronize with when they check in. The ability to turn on/off this feature too. And the ability to filter files preferably by size, but also name. So that a file under 100MB would be scanned regardless, but a file over 100MB would be checked against the MD5 lists for exclusion first.
UI Changes 1. By default, users shouldn't be notified when new antivirus signatures are downloaded. I would prefer only having a notification if there is a problem. I realize that this can be turned off, but I recommend Nod32 to a lot of people who don't know much about computers, and having to outline how to do this makes things more difficult than they need to be. Also, I tell my friends that Nod32 is very quiet (because on my computer, I only have notifications enabled if they require user interaction), but when my friends install it to try it out, it is very "noisy" making them wonder what I was referring to when I mentioned that Nod32 was so quiet. 2. Allow user to keep only one item in the context menu instead of both "Scan with ESET NOD32 Antivirus" as well as "Advanced Options". With v2.7, there was only one item in the context menu, which kept things clean. However, with v3 I now have to deal with two menu items. I would prefer the option to help slim this down for power users (I understand if this is kept on by default). Note that turning off context menu integration doesn't work because that removes the "Scan with ESET NOD32 Antivirus" option as well as the "Advanced Options" - I only want to turn off the "Advanced Options". 3. Allow at least basic configuration in "Standard Mode" of the interface. Currently, in "standard mode", I cannot configure any options. So, if I need to help my friends disable the Desktop notifications, I have to have them revert to Advanced Mode revealing a bunch of options that most users don't care for. I would prefer to at least show a simplified list of basic config options in standard mode.
Re: UI Changes nowadays many home has multiple pcs and laptops. so i will request if the mirror feature can be included in the home version also. this will save quite a hassle and will bring down the internet bill also.
Re: Future Changes to EAV 3.0 Password protection on an installation package is not in compliance with .msi package standards which is what I heard is the official reason why the option is no longer offered. In addition, if a process is able to reach that point and access msiexec with administrative credentials in the first place, any password protection is going to be relying on a .ini file or registry key someplace on the system. The administrative credentials that the malicious process is using can take ownership of any registry keys or files on the system and modify them to bypass a password protection scheme. And an uninstall password would not stop malware from deleting core components of Nod32, unregistering critical dlls or services, or any other number of ways you can cripple a program once administrative credentials are obtained. Password protection of an installer is nothing more than security through obscurity, and at this point Nod32 isn't an obscure product and such measures will be targeted and circumvented. If you want real assurance that your installed packages won't be modified, don't let users have administrative credentials and keep the system properly patched. Hacks like a password on the installer only add complexity with no real benefit.
Re: Future Changes to EAV 3.0 The ONLY changes I want to see is to make this program stable. ESET needs to bring the quality of this program back to the days of v2 stability. Why bother with changes when you have software that isn't stable and runs more like a BETA release...
Re: Future Changes to EAV 3.0 I'd like to request a way to change the size of the System Tray icon popups (i.e. font size, brief vs verbose, etc). A number of client PCs get the popups and they obscure a fairly large part of the screen - ideally should be able to make smaller and less obtrusive. Thanks!
Re: Future Changes to EAV 3.0 It would be nice to have a better sample submission feature, because it has a size limit and also it does not gives any indication of sending progress or when it finished sent file.
Re: Future Changes to EAV 3.0 I'd like to be able to block an entire top-level domain using the 'blocked addresses' section of the 'Web access protection' settings.
Re: Future Changes to EAV 3.0 I strongly suggest that by default EAV shouldn't append a message to scanned e-mail unless a virus is found so that you have to choose to enable it actively if you want to have a message in all your e-mail. /Preben
Re: Future Changes to EAV 3.0 Changes mainly for the Antivirus version only. 1. Change the GUI back to something similar to v2.7 its because of this it will run on lower end systems and will still run in GUI mode in safe mode. 2. REMOVE the web access protection, v2.7 was great because it was just AV nothing more nothing less and did a damn good job too!!!! Its infuriating that it blocks a site that i KNOW is fine and i try to disable it and it won't 3. After install have it already set to scan within archives etc rather than having to go through everything and set it all. This can be done with v2.7 if the registry entries are exported after it has been set up. 4. Remove the "fancy" bits (i dont just mean the GUI i mean in general) so as to lower CPU and RAM usage. Thats everything i can think of
Re: Future Changes to EAV 3.0 Just realised a really useful function of v2 was that you could see what file was currently being checked via AMON, could we see the Top-10 (or top 50) most checked files? It might be worth it to add them to the exclude list to help with performance issues, if the files where not required to be checked
Re: Future Changes to EAV 3.0 If I recall well, you can choose to install or not, if you choose the personalized install.
Re: Future Changes to EAV 3.0 3.0 is really just a terrible code base and needs to be deleted. Go back to 2.7, streamline it even more, put a pretty interface on the same code base, make it work with exchange 2007 / server 2008 and x64 OS's, improve the remote admin console and tool a bit and you have a winner. If version 4 is just as bad as version 3, ESET will have one less reseller, and a lot of lost clients. We can't put ANYONE on any system on v3 without problems that never happened in 2.x... systems will feel slow and laggy, then be fine again, more crashes and instability. No exchange server on v3 is a real PITA too so we have to try and mix supporting 2.x and 3.x on the same network. Support just doesn't care, I try every build of V3 and it's crap. That's great that some of you have no problems with it, but you may have been used to McAfee Security Center or some other bloated slow POS so of course V3 is better than that. We just have users that tell us, we don't want this new AV it's slower after, and we have to load 2.x back on at our expense.
Re: Future Changes to EAV 3.0 I would like a switch in the settings which cause the application to obey the windows system colour scheme. I have a client who is vision impaired and has a high contrast colour scheme with white text on black. The Nod32 application comes out hellishly bright on his system because it ignores the standard windows settings. D.
Re: Future Changes to EAV 3.0 Have to agree in regard system resources or at least offer a switchable laptop option whereby bare bones rather than bells and whistles is easily catered for as in 2.7. Thank you Eset.
Re: Future Changes to EAV 3.0 Improve the detection Iv'e had a problem with the ardamax keylogger nod 32 didn't detect it. and also some trojans agents that nod 32 didn't detect. my computer went slow and crashed for 3 times. after a scan with zonealarm security suite I detected them and removed them since then he didn't crash.
Re: Future Changes to EAV 3.0 Eset DOES detect this keylogger. https://www.wilderssecurity.com/showpost.php?p=1269677&postcount=6
Re: Future Changes to EAV 3.0 Making the cleaning options of Threatsense, realtime and ondemand scanner to "Strict Cleaning" by default
