Still on v4 - is a move to v6 worth the effort?

Discussion in 'ESET NOD32 Antivirus' started by Vocalpoint, May 31, 2013.

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

    Vocalpoint Registered Member

    Joined:
    Mar 11, 2008
    Posts:
    31
    I do not pop around very often - but when a new version becomes available - I like to see whether things have improved.

    After what I saw as a "debacle" with NOD 32 v5 - I skipped it completely.

    Now with v6 - is it ready for prime time? Better yet - it is worth my time to turn away from my ever trusty 4.2.71.2 - which I must say - has been one of the best pieces of software I have ever used. Nary an issue in months and months of running it...

    So - what say you?

    VP
     
  2. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    Not sure what you mean. It's a matter of fact that every software suffers from certain bugs but I don't recall severe bugs in v5 than those in v4.
    Every new version brings improvements and changes under the hood besides the visible ones in gui. Among other things, v5 brought LiveGrid, a significant improvement that allows for scanning less files whitelisted in cloud. V6 has brought antiphishing protection, improved protection against 0-day threats, Anti-Theft and protection against CVE exploits (ESS).
     
    Last edited: May 31, 2013
  3. Vocalpoint

    Vocalpoint Registered Member

    Joined:
    Mar 11, 2008
    Posts:
    31
    Apologies - but you must have a short memory. 5 had the Huge USB hub issue and a number of other things that were not exactly "good".

    And for kicks - go ahead and review this thread (again) as you and I were both in it....

    https://www.wilderssecurity.com/showthread.php?t=312377

    That was basically enough for me.

    So again - is 6.0 worth a shot?

    VP
     
  4. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    Every new version has its bugs, be it v3, v4, v5 and the same holds true for any software vendor. V5 had many new features, some coded from scratch to give even better protection and to take advantage of the features supported in modern operating systems. Although it's true that a small number of users encountered certain issues, for the vast majority of users v5 and v6 have been working perfectly without any issues.

    If you've encountered certain issues with the latest v5 or v6, please provide more details.
     
  5. TheKid7

    TheKid7 Registered Member

    Joined:
    Jul 22, 2006
    Posts:
    3,469
    I am also thinking about upgrading from version 4.2.71.2 to version 6.X.

    Is version 6.X "install and forget" or is there anything special that I should know?

    I saw somewhere that version 6.X needs to go through some sort of "learning" for a day or two. Is that the case? Please explain.

    Also, do you install version 6.X over version 4.2.71.2 using the Live Installer?

    Thanks in Advance.
     
  6. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    Just install install v6 over v4 and that's it. No further configuration or "learning" is needed. V6 provides quicker protection against newly emerging threats thanks to LiveGrid.
     
  7. TheKid7

    TheKid7 Registered Member

    Joined:
    Jul 22, 2006
    Posts:
    3,469
    Is the Live Installer the only option now or is it still possible to download the whole installation exe?
     
  8. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    It's up to you. You can switch between Live and offline installer on the download page.
     
  9. TheKid7

    TheKid7 Registered Member

    Joined:
    Jul 22, 2006
    Posts:
    3,469
    I did the upgrade (using the Live Installer) on one of my Windows XP Pro 32 bit PC's and got two of the following Event Log items (~36 seconds between each item):

    ..........HIPS Communications with driver failed. HIPS does not work.

    Is this anything to be concerned about? Should I uninstall and then reinstall using the full downloaded installer?
     
  10. ronjor

    ronjor Global Moderator

    Joined:
    Jul 21, 2003
    Posts:
    57,719
    Location:
    Texas
    Did you restart the computers after the install?
     
  11. TheKid7

    TheKid7 Registered Member

    Joined:
    Jul 22, 2006
    Posts:
    3,469
    Yes.

    I think that the two events happened before Restart.

    Also, AppGuard was turned completely OFF prior to the installation and remains turned OFF.
     
  12. ronjor

    ronjor Global Moderator

    Joined:
    Jul 21, 2003
    Posts:
    57,719
    Location:
    Texas
    You can do that or go to the control panel, uninstall program, right click the ESET program, and select change. You can try a repair install from there.
     
  13. TheKid7

    TheKid7 Registered Member

    Joined:
    Jul 22, 2006
    Posts:
    3,469
    Thank you.
     
  14. TheKid7

    TheKid7 Registered Member

    Joined:
    Jul 22, 2006
    Posts:
    3,469
    At first I tried to do a Repair, but the NOD32 Installer said that it could not find the file it needed in a Temp folder.

    So, I decided to go the 'conservative' route.

    1. Restored a Differential Image which was made a few days ago.
    2. Downloaded the standalone NOD32 6.X 32 bit Installer.
    3. Uninstalled NOD32 4.X.
    4. Restart of PC.
    5. Installed NOD32 6.X.

    The HIPS Event was not seen this time.

    However, while AppGuard remained turned OFF, I added ekrn.exe to both the PowerApps & Memory Guard Exceptions (Write). When I had just finished clicking on Apply for the Memory Guard Exceptions addition, I got a BSOD. I am guessing that the BSOD was probably not related at all to AppGuard since AppGuard was still turned OFF. I do not know what caused the BSOD. Windows then went into a Restart and everything appears to be OK now.

    What do you make of the BSOD? Possible cause(s) of the BSOD?
     
  15. TheKid7

    TheKid7 Registered Member

    Joined:
    Jul 22, 2006
    Posts:
    3,469
    Should I leave the HIPS settings at the default of "Automatic mode with rules"?

    Should I wait a while before turning AppGuard back on to "High"?
     
  16. ronjor

    ronjor Global Moderator

    Joined:
    Jul 21, 2003
    Posts:
    57,719
    Location:
    Texas
    Sure.
    Driver conflict maybe.
    Your choice but ESET is a robust program. Maybe wait and see how things go.
     
  17. TheKid7

    TheKid7 Registered Member

    Joined:
    Jul 22, 2006
    Posts:
    3,469
    Since I am curious to what caused the BSOD, I just contacted ESET to ask for an EMail address where I can send the Windows Minidump file.
     
  18. ronjor

    ronjor Global Moderator

    Joined:
    Jul 21, 2003
    Posts:
    57,719
    Location:
    Texas
  19. TheKid7

    TheKid7 Registered Member

    Joined:
    Jul 22, 2006
    Posts:
    3,469
    I just made a SysInspector log. I hope that the Minidump + SysInspector log will be good enough give an idea of what happened.
     
  20. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    Please upload the dump to a safe location and PM me the download link.
     
  21. TheKid7

    TheKid7 Registered Member

    Joined:
    Jul 22, 2006
    Posts:
    3,469
    What is a "safe location"? Example?
     
  22. TheKid7

    TheKid7 Registered Member

    Joined:
    Jul 22, 2006
    Posts:
    3,469
    I figured out how to put a file for download at a "safe location". I have just sent you a PM with the link.
     
  23. TheKid7

    TheKid7 Registered Member

    Joined:
    Jul 22, 2006
    Posts:
    3,469
    I have found out that the cause of my BSOD crash is that ESET and AppGuard use the same operating system mechanism for process launch detection. Windows XP OS only permits one application to use this mechanism at any given time.

    I never had this BSOD issue with NOD32 version 4.2.71.2 and AppGuard running together on three Windows XP Pro PC's for about a year. Is there anything different in NOD32 version 6.X that would cause this problem to show up?

    If I upgraded to Windows 7, does Windows 7 have a mechanism for process launch detection which will separate NOD32 and AppGuard?

    Thanks in Advance.

    Note: I have not had any more BSOD's on the PC with NOD32 version 6.X installed.
     
Thread Status:
Not open for further replies.