Thanks for the update. To your questions, I tried everything from running a deep scan to a smart scan to a simple memory scan, such as a2cmd.exe /m. There should be no reason this should not finish in let's say 6 hours. As to the time out, we are using an automated tool that runs these scripts, so you can define a time out. We are uing AVG, so this may be a problem. I will try to run this again on a system without AVG to see if it's any different. I'll keep you updated. Thanks
Hello I am creating a very basic script to automate scans of the command line scanner. It's a batch file that calls a2cmd.exe with a few switches. I am scheduling it on a computer using the SYSTEM account, because there are multiple user profiles set up on this machine. The scan seems to start (I can see a2cmd in Task Manager) and it using upwards of about 120MB of RAM. But that's all that happens. Eventutally it will stop when the script timeout period is reached. I've set it as high as 6 hours. It does not create a scan.log file as I have specified It does not quarantine anything (and I am sure there must be something on that machines, cookies at least) The SYSTEM account has full access to the a2cmd folder Any ideas?