If it ain't broke, don't fix it!!!!

Discussion in 'ESET NOD32 Antivirus' started by ioniancat21, Jul 23, 2009.

Thread Status:
Not open for further replies.
  1. ioniancat21

    ioniancat21 Registered Member

    Joined:
    Apr 23, 2008
    Posts:
    32
    I too am having the majority of my issues with Vista machines similar to GldRush98's experiences above. What scares me is that Windows 7 is being released shortly and if NOD32 is having issues running on Vista, how is Windows 7 going to look being that they can't get it running error-free on the older Windows versions.

    Do yourself a favor all, skip the 4.0 series completely and stick with 2.7 until the wheels fall off as I've been advising to others I know who use NOD32. I've seen on the WWW that NOD32 4.0.437 is being touted by some as a "final". If this is their "final" stable build and there is truth to these statements, Eset is in big trouble as this current version is definitely not ready for primetime.

    It saddens me to have to make comments like these and I really do wish that version 4.0 was 10000% better than 2.7, unfortunately it's not. It shouldn't be too hard to make me a believer Eset, simply make a product as reliable as the 2.7 version and I'll gladly update all my messages related to this here with happy-joy, sugar sweet reviews about just how great NOD32 is.
     
  2. rnfolsom

    rnfolsom Registered Member

    Joined:
    Nov 9, 2005
    Posts:
    247
    Location:
    Monterey, California
    Possible synthesis or summary of the "I'm having problems with Eset NOD32 AV 4.0.437" posts here:

    Not everyone here has made clear what Windows version he is running, or whether he is installing Eset NOD32 AV 4.0.437 on multiple computers using
    a) a Workgroup (peer-to-peer) network
    or
    b) a domain (server-client) network

    In fact, I don't think anyone who is dealing with multiple computers has mentioned which network type he is using, but it's likely b).

    So I'll go out on a limb and guess that most users who have trouble installing Eset NOD32 AV 4.0.437 are installing it on computers running Windows Vista (messages 2 and 22 above refer to Vista Sp2), and/or are using some type of network (probably Domain) to install Eset NOD32 AV 4.0.437 on multiple computers, perhaps on a collection of client computers using different operating systems or at least different service packs.

    Of course, that guess does not deny, in any way, that Eset needs to explain in greater detail how to avoid these (apparently mostly network) installation problems, and if necessary to fix any bugs that are causing them.

    My own network is a workgroup (peer-to-peer) with all computers using Win2kSp4, but with only three machines I'll install Eset NOD32 AV 4.0.437 manually on each computer. I've had no problem with the first installation (on the computer on which I am writing this), and I don't anticipate problems on the remaining two computers. But that's cold comfort to someone trying, over a network, to install on multiple computers.

    Given that this is message 27, I'm locking the stable door after the horse is out, but I hope that any additional posts on this thread, regardless whether they are reporting success or failure, give a fairly complete description of the environment: installing manually on separate computers or using a network to install on multiple computers; workgroup or domain network; operating system and service pack information about the source computer and client computers; and method used and steps taken (including folder deletion) to uninstall the previous antivirus software (e.g. my message 16).

    Roger Folsom
     
    Last edited: Aug 2, 2009
  3. ioniancat21

    ioniancat21 Registered Member

    Joined:
    Apr 23, 2008
    Posts:
    32
    I just wanted to add in some positive information for others testing out there. Within my test lab, it seems that NOD32 v4.0.437 installs and runs just fine on Windows 7. So far all installations on this operating system have had no issue. I only have Windows 7 in the lab and on Vista and XP, where I actually need it to work, it doesn't which is why many of us have refused to upgrade from 2.7.

    Looking on the bright side though, it's been nice to actually see the client running correctly for once. Just to add, version 2.7 also runs fine in Windows 7 so those who are stuck in the past like myself can continue on this path.
     
  4. ioniancat21

    ioniancat21 Registered Member

    Joined:
    Apr 23, 2008
    Posts:
    32
    Just to keep all updated;

    I kept the few 4.0 clients in place that would install without issue and unfortunately, I had to roll back to v2.7 on 2 of those 5 remaining clients. The two clients I rolled back suffered from the unfixable "Analysis of application protocols will not function" issue. Despite reinstalling, using the Eset uninstaller or anything else I tried, was unable to get those clients to ever work after that issue. So..........now there are only 3 clients left. I'm laughing with a friend here and were making bets on how long these 3 clients will run until they also fail.

    I've said it before...................GET YOUR STUFF TOGETHER ESET, IT'S TIME TO EITHER FIX THESE CORNY ISSUES OR DUMP THE WHOLE 4.0 JUNK APPLICATION AND RELEASE 2.7 NEXT YEAR WITH A 5.0 STICKER ON IT!!!
     
  5. ccomputertek

    ccomputertek Registered Member

    Joined:
    Jul 27, 2009
    Posts:
    371
    Geez, temper temper lol, can you say L-O-V-E ........... lmao

    I was thinking to myself while playing with NOD32 starting from version 2.7

    " :eek: man, are all these release candidates called final release versions :eek: "

    Don't know why you love 2.7, it looks like it never left the windows 3.1 age and it did in fact have many flaws, one of which you mentioned I.E. getting blow out easily and disabled by mediocre viruses.I have found the rest of the flaws while i was poking around with it.Then I found my true love, version 3.0.684.0 .... there is a slight problem with it I have experienced, but the rest of 3.0 is flawless IMO.Then i tinkered with 4.0, I did not have any issues with it, but for some reason I could not stand it, they got too happy and put a bunch of crap in it / on it, that IMHO was not necessary.I had 4.0 for one day and said screw this, I'm never leaving 3.0.I just wish / hope that their virus definitions stay unified, unlike other antivirus companies who force you to upgrade by making it so the latest definition models no longer work in older versions, like symantec for example.The last version of symantec I was able to tolerate honestly was 2003, before that it was norton antivirus 2000 for many years, till they made the new definitions incompatible with older versions.2003 is still supported and still works, but not for much longer i'm sure.Please do not do this ESET, I have no plans on leaving version 3.0 EVER !

    stop getting happy with these GUI's and all the other stuff, you had it right with 3.0 ! just some minor fixes thats all.

    I will now be submitting a resume to ESET, to work in the test / compatibility labs or as some type of PC tech / specialist.I wonder, I allways wanted to go to Cali, But perhaps they have an office in Romania or Slovakia, the girls there are freakin' HOT ! :eek: o_O
     
    Last edited: Aug 19, 2009
  6. edwin3333

    edwin3333 Registered Member

    Joined:
    Aug 29, 2007
    Posts:
    244
    I'm currently removing Nod32 from over 600 PC's. Yes, I did remove Nod32 and rebooted twice before installing 4.0.437. The problems occur on new PC's installed from XP CD that never had any other AV. Yes, I've contacted support on many of these issues and they have acknowledged my issues are valid. Sometimes it took a few months of work to get that far. But none were resolved. My 2.7 PC's are stable but are the ones getting viruses all the time.

    I've tried Kaspesky 2009, KIS, and KAV . We have had around 60 PC's with it. I don't recommend it either. It's an exception wh0re. WGET, Robocopy, HTTP streaming all get broken and need major exceptions to work. It's in their forums..

    Symantec ESS 10 through 10.3 have had major issues too. File shares just quit working after a few days. But 10.4 MP4 seems to have fixed all the issues. You have to manually upgrade your server to get that version update though.

    Didn't all the AV vendors have to re-write their products because Microsoft removed the way products such as 2.7 hooked into the OS in Microsofts newer OSes? Is that the reason why 3.0 and 4.0 are so different than 2.7 with no IMON but with the new proxy? I kind of think this change is the reason why I have so many problems. Cheyenne AV was like Nod2.7 in various regard. Then when CA modified it in 8.0 gold, I went through many very similar issues I am facing with Nod32 from 2.7 to 3/4.0. That's what made me switch to Nod in the first place.

    Anyway, not ranting. I'm a lost customer and that's the reason why. In 3 years I will re-evaluate. Nod will be on the re-evaluate list..
     
  7. jeremyf

    jeremyf Registered Member

    Joined:
    Jul 14, 2008
    Posts:
    61

    lol, wut?
     
  8. Cosmo32

    Cosmo32 Guest

    I do not know whether I even belong in this conversation, but, I am now considering an upgrade to ESET V4.0BE.
    I have now lived behind the V2.7BE code since 2006. I have been infection-free. At this date I rate this ~100%; and, I do NOT use the XP firewall and such.
    For my money I only expect ESET to sell me a product that works. So far it has in spades! I am impressed.
    I still have some fear of V4, but, I am still listening to the voices here.:D
     
  9. ethos

    ethos Registered Member

    Joined:
    Aug 26, 2008
    Posts:
    30
    Upgraded 90ish clients to 4.0.437.0 from 2.7, was a bit of a pain as it meant uninstalling 2.7 before updating. My method was:

    * Uninstall Nod32 2.7, reboot later
    * Install Nod32 4.0.437.0 and import config file
    * Reboot Machine

    I've had 0 problems so far, the startup scan seems a little longer but I'd imagine it's just searching for more / a more thorough scan.
     
  10. tsherr

    tsherr Registered Member

    Joined:
    Jan 30, 2007
    Posts:
    62
    I've been installing v4 since May with zero problems. These installs have been on: XP Home, XP Pro, Vista Home (32 and 64), Business, Ultimate (32 and 64.) Not sure where you guys are finding the problems, and I don't doubt you are having them, but I've actually seen fewer problems with v4 installs than with 2.7 installs (and have fixed several machines that refused to run 2.7 by installing v4 installed.

    T
     
  11. ioniancat21

    ioniancat21 Registered Member

    Joined:
    Apr 23, 2008
    Posts:
    32
    It's sad to see others in my boat although I am happy there have been some success stories here with the 4.0 client.

    Like other users have said, v2.7 isn't as powerful against some of the newer virus and spyware types as compared to 3.0 and 4.0 but it's stability is unmatched, which to me is the more important feature.

    Just to add, I've been working in I.T. for almost 20 years and I'm also doing consulting work as well. For most of the antivirus deployments I do, in most cases customers want Symantec's Endpoint Protection 11 MR4. In my experience, deployment of this product has been easy and Symantec has improved the client drastically since the Antivirus Corporate 10 version which was much more of a pain to deploy and had one of the biggest footprints I've seen in an AV client. While I know this is the ESET FORUM, I thought I'd share my experiences with others who are on the fence.

    My experiences with NOD32 server-based deployment are few as many of my business partners are in the financial sector and Antivirus reporting is high on their list of needed features. Symantec Reporting is one of the most robust of the group as Sophos, McAfee, Kapersky, NOD32 and others either don't offer these options or don't do it as well. When I have deployed NOD32, it's usually been in smaller business settings as I feel that client fits best in that environment. The point is, the competition in this genre is fierce, if Eset doesn't get it together, they could lose their customer base very easily in this market. Stability, rather than features should be on Eset's list of goals, instead they continue to frustrate users of their product with unreliability. I hope the Eset support team understand that our goal here is the same, to have a happy, event-free experience running, deploying and administering the Eset 4.0 Client. I don't enjoy railing a product I've loved for years and am saddened by the diminshed reliability of their latest client. We all want this product to work as we remember. I can imagine most of us here were sold on this product initially in the v2.0 days. Years later, we're all still here wanting what we had, a lightweight client offering good protection from virus that's not too problematic to install. What we are currently getting is an unreliable, unstable product instead and this is why users in the forum seem frustrated. Most NOD32 users are not about seeing new versions every year and can live with all as it is provided that Eset in return gives them a client they can depend on. Eset has set their bar high with the 2.7 client, the question is; can Eset manage to get their stuff together finally and produce a stable product so we can all come here to the forum in praise of your product, rather than to complain about it.
     
    Last edited: Aug 21, 2009
  12. ioniancat21

    ioniancat21 Registered Member

    Joined:
    Apr 23, 2008
    Posts:
    32
    Also..........
    Edwin3333 - Symantec ESS 10 and the whole damn series is absolutely wacked and I don't suggest that damaged fossil to anyone. If NOD32's deployment is giving you issues and you can't deploy it, check out Symantec's Endpoint Protection 11 MR4 as I can tell you from experience that this is the best antivirus product to come from Symantec since 2000 when Norton Systemworks 2001 was still good and not the bloatware they sell today along with their Norton 360 product, which is also junk I hope to never see again. Also, stay clear away from anything McAfee as machines slow to a crawl with that bloated, unstable horror story of a client.

    Good Luck, CAT
     
  13. jeremyf

    jeremyf Registered Member

    Joined:
    Jul 14, 2008
    Posts:
    61

    -what is an "ESET driver"?

    -how does order of install determine priority for loading "drivers" in Windows at startup? (please include reputable source)

    -even if the procedure you outline: installing Windows on a freshly formatted partition, painstakingly installing all MS updates, then "reboot at least 10 times" (lol, what is 10th reboot for?). Even if this solved his problem on one machine, did you read he had 600 PC's? How would this help? Who has time for this?

    -you did read his post was a conclusive statement that he was finished with eset right? not a request for "help"?

    this is why I lol, wut?
     
  14. ccomputertek

    ccomputertek Registered Member

    Joined:
    Jul 27, 2009
    Posts:
    371
    1. An eset driver is someone who gets behind the wheel of a motor vehicle and just happens to use eset NOD32 antivirus.

    2. If you install other software services that use drivers, like a firewalls ETC. first, then the eset drivers that are set to go into a load order group will get a TAG of say 18, 38 or 42, whereas if you installed NOD32 first before them, it would get a TAG of say 8 which would make it start before the others in the same load order group.... and I am the reputable source.

    3. I retract my previous statement and deleted my 2 previous posts.

    4. I retract my previous statement and deleted my 2 previous posts.

    I made an interesting discovery while doing another fresh install of windows XP SP3 with only the video and network card installed by windows and no other software yet, including the windows firewall being turned off.I will post up what I have found in the original problem threads later sometime.


    **************************************************************************************
    -even if the procedure you outline: installing Windows on a freshly formatted partition, painstakingly installing all MS updates, then "reboot at least 10 times" (lol, what is 10th reboot for?). Even if this solved his problem on one machine, did you read he had 600 PC's? How would this help? Who has time for this?
    **************************************************************************************

    I was being sarcastic about the 10 reboots, a problem i have encountered started happening after exactly 4 reboots and I have traced the problem to 2 things, driver load order and what I just discovered, windows XP prefetch seems to be the culprit, I disabled it and the problem went away.will update that discussion later like I said.

    As you may or may not know, most companies " the smart ones " try to stick with about the same config for all 600 of their pc's, so testing a method to get around a problem on 1 out of 600 will most likely work for the other 599 pc's in your deployment.
     
    Last edited: Aug 21, 2009
  15. volvic

    volvic Registered Member

    Joined:
    Aug 17, 2009
    Posts:
    220
    Really ...... let us know when you are done........
     
  16. cloneman

    cloneman Registered Member

    Joined:
    Aug 22, 2009
    Posts:
    1
    NOD32 2.7 reaks awesomeness for older machines. I couldn't care less if it only blocked 1 virus in the world, the fact that it uses so little system resources is what made it popular. High detection rates are just a bonus :)

    Some "fixing" was needed by the ESET team though since a modern rootkit can kill v2.7.
     
Thread Status:
Not open for further replies.
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.