Startup Scan Progress

Discussion in 'ESET NOD32 Antivirus' started by wibo, Mar 17, 2010.

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

    wibo Registered Member

    Joined:
    Apr 10, 2007
    Posts:
    27
    I'm using Eset for many years now but it seems to more and more CPU and memory consuming.
    The low memory and cpu usage was the reason why I switched to Eset.
    But the last years things have changed.
    The memory usage is more and the cpu much more.

    The whole day my Eset is doing this "Startup Scan Progress"
    and is using 80-99% of CPU.
    With Startup Scan Progress I'm not enable to do my usual work.

    What's happening?

    ps:
    I have the latest beta 4.2.35 but nothing changed.
    Same with all other previous betas.
     
  2. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    Try disabling the automatic startup scan task run after an update to minimize the number of startup scans run each day. Or you can edit the task and set it to run when the computer is idle.
     
  3. Meganeoman

    Meganeoman Registered Member

    Joined:
    Dec 20, 2007
    Posts:
    13
    I have the same problem :'(
    Nod32 is not what its used to be anymore!
     
  4. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    As of v.3 / 4, various scan limitations have been removed and now the user can configure the limits himself. What's more, v3/v4 contains additional modules for better detection/cleaning/protection and thus keeping the user away from emerging threats that v2 might not be able to protect against.
     
Thread Status:
Not open for further replies.