Question Regading V3 and startup scan

[zfrangi]

Hey all:


First time poster but long time lurker on these boards. Ive recently embarked on trying to update the whole organization from 2.7 to version 3.0 of nod 32. I did create a package for v3 along with blackspears settings for the package. I did make some changes to his recommended settings. I did install it as a test on a coworkers pc here in our office. The first thing he noticed when he rebooted and logged back on is the machine started to lag really bad. Turns out it was running a scan. I thought the only scan it would do would be the weekly scan I put in the schedule. Turns out I guess there is a automatic startup file check which runs every 24 hours and after a/v updates. How can I go about turning this off? Ive tried removing it from the schedule and then export the settings but it seems to stay. I have done some research on this from this board and it does look like im not the only one asking this. Unfortunately the settings are a tad bit confusing. Hoping someone can point me in the right direction. Basically I dont want the pc to be doing anything during the day that would slow down the machine cause that generates more phone calls for me.



Thanks in advance...

[Marcos]

I'd strongly recommend keeping the default settings which provide the best balance between detection and speed. Disabling any of the modules, including default startup scans, will make your system more vulnerable to threats. The default startup scans are run with as low priority as possible so you shouldn't notice them running at all. However, if you schedule a disk scan with all options enabled, this may slow down the system performance. Such scans should be scheduled at the time when the computer is not being used extensively.

[edwin3333]

There are a lot of bugs in the product. If you mess with any of the scan or scheduler settings, you will likely find them. You will see things like Nod32 running the wrong scan profile for the startup scan, or running the same scan twice at the same time, or running the scans over and over and over.

I've reported these to support, they are aware of the issues, and recommend not changing these settings. They will not, apparently, fix them.

From what I can tell a lot of the information is hard coded in the client. For example, create a new scan profile and schedule it to run. Let it complete. In the registry it stores that it completed in @In-depth, not the newly created profile.

You are much better off leaving these settings at default due to all the bugs.

[xMarkx]

{QUOTE-> I'd strongly recommend keeping the default settings which provide the best balance between detection and speed. Disabling any of the modules, including default startup scans, will make your system more vulnerable to threats. The default startup scans are run with as low priority as possible so you shouldn't notice them running at all. However, if you schedule a disk scan with all options enabled, this may slow down the system performance. Such scans should be scheduled at the time when the computer is not being used extensively. <-QUOTE}
Hello Marcos,

Did you ever look into why the startup scans on my Vista (but not XP) PC have never run once at bootup? (Made a thread about it a few months back - you said you would get the issue looked at).

Regards,

Mark.