AMON turning itself off

Discussion in 'NOD32 version 2 Forum' started by Gavatron, Aug 8, 2005.

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

    Gavatron Registered Member

    Joined:
    Apr 24, 2004
    Posts:
    6
    I recently loaded the latest NOD32 on to a HP notebook. On occasions when the machine boots up Windows XP indicates there is security issue because NOD is not turned on.

    The exact issue is that the AMON module is not switched on. I have to go into NOD, switch to it on, and everything is happy. AMON is set to enable automatic startup so why does it switch itself off?

    We are running NOD32 on four other machines and no other has this fault.

    Any ideas please?
     
  2. RejZoR

    RejZoR Registered Member

    Joined:
    May 31, 2004
    Posts:
    6,426
    Select AMON module and click Setup button on the right side.
    Select Security tab and enable "Enable automatic startup of AMON".

    You probably used Expert installation mode and unchecked auto start of AMON upon Windows startup during setup process...
     
  3. alglove

    alglove Registered Member

    Joined:
    Jan 17, 2005
    Posts:
    904
    Location:
    Houston, Texas, USA
    Try uninstalling and reinstalling NOD32. It may be easier than trying to track down the specific problem.
    1. Download a fresh copy of NOD32 from Eset.
    2. Uninstall your existing NOD32.
    3. Reboot.
    4. Delete the C:\Program Files\Eset folder.
    5. Reboot.
    6. Install your new copy of NOD32.
    If that doesn't work, then I guess we will have to track down that problem.
     
  4. RejZoR

    RejZoR Registered Member

    Joined:
    May 31, 2004
    Posts:
    6,426
    I assume he unchecked auto startup of AMON while installing NOD32...
    Only logical explanation. You can't force AMON to be shut down when it's laready running (worm/trojan case)
     
  5. Gavatron

    Gavatron Registered Member

    Joined:
    Apr 24, 2004
    Posts:
    6
    As I said in my post Enable Automatic Startup Of Amon is checked (and remains so). Also as I said I installed the latest version of NOD 32 from Eset.

    I did not delete the folder so I guess I'll try another reinstal.

    It looks like further work is needed thanks.
     
  6. Gavatron

    Gavatron Registered Member

    Joined:
    Apr 24, 2004
    Posts:
    6
    I reinstalled a fresh version of NOD32 after uninstall and folder delete. The issue is not consistent. The next two occasions the machine was started it was fine and then next time, bingo! - AMON was turned off.

    I have run an in-depth analysis and that was all clear.
     
  7. Blackspear

    Blackspear Global Moderator

    Joined:
    Dec 2, 2002
    Posts:
    15,115
    Location:
    Gold Coast, Queensland, Australia
    Hi Gavatron, welcome to Wilders.

    With this issue can you please send an email to support@eset.com and place a link to this thread. If you do not hear from Eset within 3 days (allows for weekends), please advise us here...

    We would appreciate if you could keep us in the loop with your progress, as we all learn this way…

    Cheers :D
     
  8. alglove

    alglove Registered Member

    Joined:
    Jan 17, 2005
    Posts:
    904
    Location:
    Houston, Texas, USA
    Strange. But other NOD32 modules, like IMON, are up and actively running?
     
  9. Brian N

    Brian N Registered Member

    Joined:
    Jul 7, 2005
    Posts:
    2,148
    Location:
    Denmark
    There are problems with both IMON and AMON if you reboot your pc with one of them disabled.
    It's a bug in NOD.
     
Thread Status:
Not open for further replies.