Beta 3 & 'Pooter lockup after scheduled full scan

[mvsgeek]

If I schedule a full scan overnight, the 'pooter is locked up next morning, and requires a power off reboot. The mouse cursor still functions, but the keyboard and mouse buttons are unresponsive. Also saw this with beta 1 and 2.

I know this has been reported elsewhere, but Outlook also hangs up when receiving mail from a POP3 account. Maybe a conflict with Avast AV. Solution is to disable OnGuard while checking mail.

Environment :
Win XP SP2 with all patches
Avast 4.7 Home Edition
Comodo firewall 2.4.17.183
Outlook 2003

[Support]

Mvsgeek,

Thank you for your report.

I have escalated this report to the Technical Support team.

They will respond to your query soon.

Kind regards,

Nicholas
PC Tools Support Services

[Petertron5000]

Ive tried running a scheduled scan and everything is A OK.

Can you perform a normal Full scan? Does it lock up during this scan?

Petertron5000

[mvsgeek]

So far it hasn't locked up when running a full scan manually, only when run as a scheduled task.

[Petertron5000]

This is really weird, because if it locks up during a scheduled scan, it should do the same when performing a scan. I would have thought that it stopped because it came across some entry which it could not get pass, but thats not the case.

There is a known issue with the email guard freezing the computer however. Try a scheduled scan and disable the email guard tool to see if this helps. If it does it means its the known issue.

Petertron5000

[mvsgeek]

Good news - no more lockups :-) I still don't know the root cause, but I have my suspicions. Here's what I did :

1. Uninstalled all previous SD beta versions, and installed beta 5.
2. Disabled e-mail OnGuard.
3. Disabled Windows indexing service.
4. Uninstalled ACDSee 8.1, and performed a minimal re-install without all the plug-ins. I did this because I've been getting an increasing number of Win Explorer "not responding" situations, usually after accessing image files with ACDsee. So far so good since the re-install.

For sheer masochistic pleasure, I may try a full re-install of ACDSee to see if lockup issues resurface. It would be nice to identify the culprit beyond reasonable doubt.