Guest User!

You are not Sophos Staff.

Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 6 replies
  • Subscribers 6 subscribers
  • Views 4336 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

Why does the last scanned date not change after I have run a scan?

floridabrits

Hi,

I ran a scan yesterday that 'appeared' to complete properly. I received no messages saying I had any issues.

However, when I click on the Sophos icon and click on Open Sophos Anti-Virus, it still tells me the last scan was in June this year.

Any ideas why this is?  Is this a known bug?

Are there any logs I can look at to confirm the scan did run properly?

Many thanks in advance for any assistance/guidance.

Regards,

Geoff

:1010820


This thread was automatically locked due to age.
  • 0

    Try turning off automatic updates prior to running a scan.  Does this fix the problem?

    In some cases, the scan can end prematurely due to an automatic update.  This is not expected behaviour, but reports confirm that it sometimes happens.

    :1010834
  • 0

    Thanks for the quick response Andrew. That worked :-)

    I've ran the scan and now rechecked the box again.

    Is this a bug that has been logged for fixing in the next release?

    Thanks again!

    /g

    :1010842
  • 0
    floridabrits wrote:

    Thanks for the quick response Andrew. That worked :-)

    I've ran the scan and now rechecked the box again.

    Is this a bug that has been logged for fixing in the next release?

    Thanks again!

    /g

    You're welcome :)

    The bug has been logged; I don't know if it has been picked up for a specific release fix yet.

    :1010848
  • 0

    OK... thanks again Andrew. Great / quick response as always :-)

    Cheers!

    /g

    :1010854
  • 0

    Andrew,

    I, too, have the same problem where scans start, but never complete (so the scan dates always say "never been run"). I have ML v.10.8.2. Based on your comment, I turned off the auto-update, and now scans are actually running!  (However, they are taking forever to scan .zip files - like 8-10 hours for one zip file. I'll post that separately...)

    So, it would appear that I can confirm that the auto-update process kills scans in process. And, given the default is to check once an hour, there is a strong likelihood that a scan will take longer than an hour, and end up getting killed...  :-(

    Karl

    :1010998
  • 0

    Thank you!  I just had the exact same question - off to try the fix.

    :1011008