Duis mollis, est non commodo luctus, nisi erat porttitor ligula, eget lacinia odio sem nec elit. Sed posuere consectetur est at lobortis. Vestibulum id ligula porta felis euismod semper. Donec ullamcorper nulla non metus auctor fringilla. Aenean lacinia bibendum nulla sed consectetur. Cras justo odio, dapibus ac facilisis in, egestas eget quam. Cras mattis consectetur purus sit amet fermentum. Morbi leo risus, porta ac consectetur ac, vestibulum at eros. Sed posuere consectetur est at lobortis. Etiam porta sem malesuada magna mollis euismod. Cum sociis natoque penatibus et magnis dis parturient montes, nascetur ridiculus mus. Duis mollis, est non commodo luctus, nisi erat porttitor ligula, eget lacinia odio sem nec elit. Cras justo odio, dapibus ac facilisis in, egestas eget quam. Aenean eu leo quam. Pellentesque ornare sem lacinia quam venenatis vestibulum. Curabitur blandit tempus porttitor. Sed posuere consectetur est at lobortis.
I considered that it might be doing an idle full system scan, but the CPU Usage window says it has not yet done one.
I'm aware that a scan can be interrupted if the system leaves the idle state while the scan is in progress, but looking at the graph, you can see it finished doing whatever it was it was doing while the system was still idle, so I didn't interrupt the scan.
Morac,
There are a wide variety of background tasks that the 2009 products will perform; not all of them are listed in the CPU usage graph as they are "internal" to the Product's performance and security enhancements for this release. These tasks will only run when the system is idle.
In your screen shot, the Idle Full System Scan does not appear to have run, as you have suggested. It was likely one of these "internal" background tasks that was running during the 20 minute window.
Regards,
Mike
That makes sense, thanks.
Any idea why the Idle Full System Scan hasn't run yet? I set it to run once a month, but my system was pretty much idle most of the day yesterday and it hasn't run yet. I did run a full system scan manually. Maybe that's why it hasn't run?
Morac,
If you set the Idle Full System Scan to run "Monthly" from the NIS Settings dialog, then it will not try to run for a month. After the month elapses, it will run when the system is idle. Once it completes, it will wait another month.
Regards,
Mike
Thank for responding.
The way you say it works is not what I would have expected. I would have thought that it would run once after installing and then wait a month since the last time it ran was "never", which is technically more than a month ago. Oh well.
This occurred during an idle time so it didn't affect my computer use, but I'm curious as to what NIS 2009 was doing for the 20 minutes that the CPU usage was listed as being greater than 40%.
The screenshot above was taken at about 12:30 PM, so the cpu usage at around 40 minute is the idle quickscan and the one at about 30 minutes should be the norton insight scan.
I can't figure out what the one that is running from about 5 minutes to 25 minutes is though (approximately 12:05 PM to 12:25 PM) since there is nothing in the background jobs that matches up to that time period.
Note that The Norton Community Watch scan says it is running, but doesn't actually appear to be running currently. Either that or it's been running for 30 minutes.
Also note that the idle system scan says it has never run, but I don't have it disabled.
Hi Morac
NIS 2009 is scanning your machine when it is idle. So that could explain it