multiple instances of nod32.exe causing laptop shutdown time to increase

Discussion in 'NOD32 version 2 Forum' started by andy2008, Sep 21, 2007.

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

    andy2008 Registered Member

    Joined:
    Sep 21, 2007
    Posts:
    33
    Hey All new here but been a NOD user for sometime

    Ok so heres the problem. Basically everytime i run the nod32.exe on demand scanner then quit, the on demand scanner closes but it still stays resident in the task manager. So if i scan one directory after the other via the on demand scanner , the number of nod32.exe just mount up in the task amanager. Heres the problem - when i go to restart or shutdown the laptop it hangs as it tries to clear the number of nod32.exe. Now surely when you run the on demand scanner then quit, shouldnt it end the nod32.exe straight away ? ive not observed this on my desktop when i run the on demand scanner. As i say this is a tecra m7 running tablet xp 2005 , 1.5gb ram etc. I had searched the forum about slow shutdown and the 2 main things which were apparent were installing nod32 to c:\eset or c:\nod32 which ive done but that hasnt made a difference. I also run protector suite software with the biometric fingerprint reader but disabling this is not an option. Nod32 does install and it starts up ok. Ive run a full system scan and nothing suspicious has been found. Hopefully a solution can be found for this.

    Many thanks
     
  2. andy2008

    andy2008 Registered Member

    Joined:
    Sep 21, 2007
    Posts:
    33
    should also have mentioned i run the user hive profile cleanup service and that makes no difference. I have isolated it now to nod32.exe. If i dont run the on demand scanner during a windows session i can startup and shutdown no problem what so ever. If i run the nod32.exe on demand scanner during a windows session , if i dont manually terminate the no32.exe process then shutdown takes longer than it should. If i end the nod32.exe process then shutdown is as it should be. Interestingly i repeated the above test on a normal windows xp professional desktop machine then nod32.exe disappears from task manager as soon as the on demand scanner quits. Can a mod please bump this for eset developers as i know they do read the forums.
     
  3. andy2008

    andy2008 Registered Member

    Joined:
    Sep 21, 2007
    Posts:
    33
    Heres more info : (linked thread to ticket submitted)

    Task Manager showing nod32.exe instances after opening then closing on demand scanner several times :

    http://img233.imageshack.us/img233/5417/nodtaskmanager2vq4.jpg

    NOD32 info :

    Trial version
    Days left: 30

    NOD32 antivirus system information
    Virus signature database version: 2543 (20070921)
    Dated: 21 September 2007
    Virus signature database build: 10836

    Information on other scanner support parts
    Advanced heuristics module version: 1.066 (20070917)
    Advanced heuristics module build: 1167
    Internet filter version: 1.002 (2004070:cool:
    Internet filter build: 1013
    Archive support module version: 1.058 (20070906)
    Archive support module build version: 1196

    Information about installed components
    NOD32 For Windows NT/2000/XP/2003/Vista/x64 - Base
    Version: 2.70.39
    NOD32 For Windows NT/2000/XP/2003/Vista/x64 - Internet support
    Version: 2.70.39
    NOD32 for Windows NT/2000/XP/2003/Vista/x64 - Standard component
    Version: 2.70.39

    Operating system information
    Platform: Microsoft Windows XP
    Version: 5.1.2600 Service Pack 2
    Version of common control components: 5.82.2900
    RAM: 1536 MB
    Processor: Genuine Intel(R) CPU T2300 @ 1.66GHz (1662 MHz)
     
  4. andy2008

    andy2008 Registered Member

    Joined:
    Sep 21, 2007
    Posts:
    33
    Summary :

    Expected behaviour

    When running NOD32 on demand scanner (nod32.exe) process should run when user executes on demand sccanner. When user finishes and quits on demand scanner then the process nod32.exe should terminate itself from task amanager.

    Observed behaviour

    Problem i am encountering is when i run nod32.exe to manually scan files , then quit the on demand scanner nod32.exe does not terminate and remains resident in task manager. After scanning multiple directories (right click > nod 32 antivirus > scanning files > quit on demand scanner) multiple instances of nod32.exe can be seen in task manager. The problem is when shutting down or restarting the system showing this behaviour shutdown can take up to 30 to 50 seconds. The increased shutdown time is due to multiple instances of nod32.exe resident in task manager.

    It can be narrowed down to nod32.exe because if the on demand scanner isnt run then the laptop shuts down and restarts within 7 to 10 seconds.

    Steps taken so far :

    Uninstalled then Reinstalled nod32 under program files
    Uninstalled then Reinstalled nod32 to c:\nod32
    Run full nod32 scan no signs of infection or any problems
    Tested normal desktop machine with nod32 and did not observe this behaviour. On a normal desktop machine

    Nod 32 info for desktop machine :

    Trial version
    Days left: 29

    NOD32 antivirus system information
    Virus signature database version: 2541 (20070920)
    Dated: 20 September 2007
    Virus signature database build: 10830

    Information on other scanner support parts
    Advanced heuristics module version: 1.066 (20070917)
    Advanced heuristics module build: 1167
    Internet filter version: 1.002 (2004070:cool:
    Internet filter build: 1013
    Archive support module version: 1.058 (20070906)
    Archive support module build version: 1196

    Information about installed components
    NOD32 For Windows NT/2000/XP/2003/Vista/x64 - Base
    Version: 2.70.39
    NOD32 For Windows NT/2000/XP/2003/Vista/x64 - Internet support
    Version: 2.70.39
    NOD32 for Windows NT/2000/XP/2003/Vista/x64 - Standard component
    Version: 2.70.39

    Operating system information
    Platform: Microsoft Windows XP
    Version: 5.1.2600 Service Pack 2
    Version of common control components: 5.82.2900
    RAM: 768 MB
    Processor: AMD Athlon(TM) XP 2200+ (1802 MHz)
     
Thread Status:
Not open for further replies.