EAV 6.x Home unusable on XP SP3 Pro machine here

Discussion in 'ESET NOD32 Antivirus' started by eavUser, Mar 27, 2013.

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

    eavUser Registered Member

    Joined:
    Mar 27, 2013
    Posts:
    1
    Windows XP Pro SP3
    Eset EAV 6.0.0308.0 Home
    Used on the mentioned machine along with, amongst others
    Sunbelt Personal Firewall 4.7.5.0
    Acronis True Image 2009 Home, latest available build

    Several weeks ago an upgrade from EAV 5.x Home latest release to EAV Home 6.x builds as mentioned above was performed.
    Since that point of time severe troubles occur.
    Only disabling real-time protection of eav solution helps to avoid the troubles.
    Just disabling the anti-stealth technology only does not help.
    Since the problem root reason was narrowed to eav real-time protect.
    the machine operates practically without AV solution. First, the eav was
    removed completely >>>> indicated troubles not reproducible; then upon two weeks eav 6.x
    was installed again, that time without real-time protect. disabled (again indicated troubles not reproducible).
    Yesterday, two weeks later after that the real-time protect was enabled.
    Succeeding logon as admin shows the troubles again.

    Trouble appearance/picture:
    * Acronis True Image hangs up during its startup splash screen, "Processing" stage is shown
    * logoff needs an eternity, or does not work at all, regardless of if logged on as admin or non-admin
    * shortly after got logged on poor or none interaction with OS, double-clicks on most desktop, or windows
    file explorer, or start button/menu icons does not show any reaction
    * just only mouse cursor movements are possible
    * Control Panel >> Add Remove Programs comes up with for-ever blank window,
    normally noises of working hdd are audible because os is scanning for installed stuff, but not in this case
    hdd does nothing
    * and so on
    Every time a hard reset is needed to get back control over system
    in order to recover system into integral state.
    Every time the chckdsk scan must be performed after such crash, it consumes a lot of time.

    HIPS is disabled
    Reset to default advanced settings was made, with small adaptations to own needs - no help.
    SysInspector logs were generated few minutes ago and are ready for upload.
    Due to excessive efforts it is not acceptable to produce and upload the complete memory dump.

    Dealing with troubles consumed plenty of time resources.
    Lot of regular jobs to be done on this machine are in delay.
    Please help - the purchased license is not productive.
     
  2. er34

    er34 Guest

    Hi and welcome to Wilderssecurity!

    Since you need to work and not to troubleshoot, I would advise you downgrade to ESET NOD32 AV version 4.2

    Your license and any ESET license allows you use any supported version ESET currently has. At the moment this is version 3 / 4 / 5 and 6.

    Version 4 is in my opinion kind of Gold version and trouble free.

    As you can read here, all versions use the same signatures and the same modules - this is most important. In my opinion, using v4 you do not loose any important new features and protection is the same.

    All you have to do now is to :
    1. Uninstall any ESET product and leftovers using ESET Uninstaller (in Safe mode):
    http://kb.eset.sk/esetkb/index?page...earch&viewlocale=en_US&searchid=1364421085148

    2. Visit ESET site and using your license credentials download and install version 4.2 - latest from series 4:
    http://www.eset.com/download/home/detail/family/2/fileflag/4.2.71.5/

    3. After you install the program - use the function for exclusions:
    http://kb.eset.sk/esetkb/index?page...earch&viewlocale=en_US&searchid=1364421104310

    and add Acronis and Sunbelt files to exclusions to avoid conflicts and to make NOD32 not to scan them
     
  3. Geosoft

    Geosoft Registered Member

    Joined:
    Jan 7, 2009
    Posts:
    270
    Location:
    Toronto, Ontario, Canada
    Your computer wouldn't be in a domain environment would it? If so, try adding C:\Windows\CSC\*.* to your exclusions.
     
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.