NIS by default schedules this task to run only when the user is logged in. I mentioned that the scan properly works and completes only when you are logged in exactly because if you change the settings from the task scheduler it will run but because noone is logged in, it cannot display the UI with the results of the scan so the task will not complete. The only way is to kill the process and as EsieB mentioned, this is a workaround.
I get the points though from both EsieB and yourself and I will check with our team to see how we can better address them. Stay tuned!
Thank you, athena, for checking on this. As I have several people using the same machine, and they will not properly handle a running system scan (as in they will log off when they are done using the machine, whether a scan is running or not), I need to have this run at night when folks are not using the systems. Also, when the scan is running, system performance is not good. Anything Symantec can do to help me get this to run properly without logging in will help greatly. I know that Symantec corporate products do this, so it would be nice if the consumer products can as well.
is this scheduled liveupdate done through the program or via the Windows task scheduler? when i schedule it from within the program, it shows up in the log. i haven't tested via the Windows task scheduler.
do you should see quick scans listed almost daily, as they are kicked off after LiveUpdate brings down new defs.