Incompatible modules

Discussion in 'ESET Smart Security v3 Beta Forum' started by whscott, Sep 14, 2007.

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

    whscott Registered Member

    Joined:
    Mar 18, 2005
    Posts:
    15
    ESS(b2,winxp sp2) pops this box up that says "Incompatible modules" and no explanation. What does this mean?
     
  2. mayt

    mayt Eset Staff Account

    Joined:
    Mar 12, 2007
    Posts:
    84
    Location:
    Bratislava
    You may need to delete content of the folder c:\Documents and Settings\All Users\Application Data\Eset\Eset Smart Security\Updfiles and run update manually after that.
     
  3. GarretN

    GarretN Registered Member

    Joined:
    Sep 14, 2007
    Posts:
    2
    Hi Everyone, this is my first post here.

    I actually started receiving this same error this morning out of the blue. Deleting the folder mentioned and manually attempting an update doesn't fix the issue.

    I'm going to try reinstalling in a few minutes.

    Update: Uninstalling and Reinstalling fixed the issue -- doing all required reboots when asked.
     
    Last edited: Sep 15, 2007
  4. crummock

    crummock Registered Member

    Joined:
    Aug 19, 2004
    Posts:
    198
    Same problem on Vista 64 bit.

    The suggested solution doesn't work.
     
  5. Gizmo

    Gizmo Registered Member

    Joined:
    Apr 23, 2003
    Posts:
    34
    Same thing on XP 32bit and ESS beta 2 . Deleting Updfiles content doesn't help.
     
  6. trial and error

    trial and error Registered Member

    Joined:
    May 19, 2007
    Posts:
    72
    Location:
    the former USA
    I'm getting it with XPx64 sp2 also. It happens when the program tries to update and its definitions are already current. --- http://www.eset.eu/support/update-xy1
    My taskbar icon turned kinda amber the other day, when I opened the program it was too.

    With NOD32 it recognized that the definitions were current and did not tell the user that they were "not protected".
     
  7. crummock

    crummock Registered Member

    Joined:
    Aug 19, 2004
    Posts:
    198
    If that's the case then it should be an easy fix for Eset to implement and I'm surprised we are not all seeing it all the time.
     
  8. the_redders

    the_redders Registered Member

    Joined:
    Sep 15, 2007
    Posts:
    3
    Also having the same problem.
     
  9. crummock

    crummock Registered Member

    Joined:
    Aug 19, 2004
    Posts:
    198
  10. VIPOR1

    VIPOR1 Registered Member

    Joined:
    Apr 7, 2007
    Posts:
    7
    Thanks Crummock, running that fix AGAIN worked for me. :thumb:
     
  11. the_redders

    the_redders Registered Member

    Joined:
    Sep 15, 2007
    Posts:
    3
  12. Degine

    Degine Registered Member

    Joined:
    Sep 12, 2007
    Posts:
    18
  13. Concepts

    Concepts Registered Member

    Joined:
    Aug 7, 2007
    Posts:
    26
    I am having the same problems as well running Vista x64 and have tried all the current fixes as well but still getting the error with database 2533 happened with 2531 as well. Reinstalling fixes it but as soon as another update is released the same problem appears again.
     

    Attached Files:

  14. deputy963

    deputy963 Registered Member

    Joined:
    Nov 9, 2006
    Posts:
    18
    Well, after the update issues last week everything seemed to work itself out. Updates were functioning correctly, until now.

    After attempting an update ESS's tray icon turned orange and I knew there was a problem.

    Incompatible Modules

    Vista Business 32bit.
     
Thread Status:
Not open for further replies.