Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 1 reply
  • Subscribers 1 subscriber
  • Views 2544 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

System freezes during scan

sophos-icated

I've had sophos installed on a modestly provisioned system for 3 months or more with no issues.  Beginning April 30th everytime a console invoked scan was started the system would freeze to the point I had to completely reboot the system since the keyboard and mouse had no effect.  I recently invoked a scan through the system desktop and it completed without freezing the system.  (No viruses were found.)

Wondering if the issue had been resolved I decided to initiate a scan from the console which completed successfully .  I then remembered that when the freezes occured a web browser was running and the freeze always seemed to occur during an update of the weather.com page.  So I activated the browser, making sure the usual pages were open, and initiated another console scan which completed successfully.

So the system is now operating normally with no freezes during a console initiated scan.  However this is occuring on other systems so am still searching for an answer.

The system the freeze occurred on is running XP service pack 3, 512 Mb RAM.  We are running enterprise console 4 and endpoint version 9.

Thanks in advance!!!

:3064


This thread was automatically locked due to age.
Parents
  • 0

    Hi,

    The only difference as far as I can tell between running the default scan "Scan my computer" at the client or running a "Full system scan" from Enterprise Console on the the client is the context under which the scan runs.

    "Scan my computer" as run from the client when logged on as user1 will run as user1.  If you initiate a a "Full system scan" from Enterprise Console, the same "Scan my computer" scan is run but it runs as system.  So there is potential for the scan from SEC to be able to access more files and therefore take longer.

    With that being said, it would be interesting to know if you see a difference between running the scan locally or remotely in the above mentioned ways.  It would also be interesting to try different scheduled scans running as different users with different scanning options to compare.

    Jak

    :3087
Reply
  • 0

    Hi,

    The only difference as far as I can tell between running the default scan "Scan my computer" at the client or running a "Full system scan" from Enterprise Console on the the client is the context under which the scan runs.

    "Scan my computer" as run from the client when logged on as user1 will run as user1.  If you initiate a a "Full system scan" from Enterprise Console, the same "Scan my computer" scan is run but it runs as system.  So there is potential for the scan from SEC to be able to access more files and therefore take longer.

    With that being said, it would be interesting to know if you see a difference between running the scan locally or remotely in the above mentioned ways.  It would also be interesting to try different scheduled scans running as different users with different scanning options to compare.

    Jak

    :3087
Children
No Data