Problems with update to SUPERAntispyware

[mhl]

Since installing the update to SUPERAntispyware 4.1, when I run a SUPERAntispyware scan it stalls when scanning .dat files in
C:\Documents and Settings\<user>\Application Data\. At first I thought it was just Mozilla\Firefox\pluginreg.dat but, after moving that file temporarily, I find the same happens with other .dat files. The timer is still clocking up the minutes, but SAS is no longer scanning. I have to terminate the process within Task Manager.

Any suggestions?

[mhl]

This is very strange. I have the same SUPERAntispyware update installed on 3 other PCs, each of which has the same users, and none of these other PCs is showing the same problem. I uninstalled SAS from the problem PC, and re-installed - still the problem remains. What makes it even stranger is that the scan stalls on the .dat files of only one user: equivalent .dat files exist for the other users, and the SAS scan flies through them OK.

[HAN]

I'm stumped! I have installed SAS on several PCs and never seen anything like this. I see that you have posted over at the SAS forum. Hopefully they can get you going again quickly...

[mhl]

HAN

I have been contacted by SAS tech support and asked to test a possible fix for the problem. At least one other user has reported the same problem. I am impressed by the company's urgency to fix the problem - gives some confidence in the product.

[HAN]

I'm impressed by them too. Hope a fix will be coming soon!

[Broni]

asked to test a possible fix for the problem

Did you try it?

[mhl]

Did you try it?

Yes, but it made no difference

However SAS tech support warned me that pinpointing the problem may take a few iterations. I now have a second fix to try which was sent to me overnight (I'm 8 hours ahead of SAS tech support in Oregon) - so I'll try that later this morning.

In the meantime there have been one or two more posts in the thread which I started on the SAS forum, from others who are experiencing similar problems (see http://forums.superantispyware.com/v...p?p=8113#8113). You will see that there is the suggestion of turning off DDA in SAS's Scanning Control Preferences - may work for some, so I'll try that too.

Off to walk the dog now. I'll keep you posted with any news, good or bad.

[mhl]

Update - the second 'fix' which tech support sent me works, but it has a lot of functionality removed. I think it is merely intended as a stepping stone to finding a solution which can be released.

I also tried running the original SAS executable (4.1.1046), which caused the problem, with DDA disabled and it doesn't stall - but it doesn't pick up the tracking cookies which I know are there.

SAS tech support are still working on it. Watch this space ...

[Broni]

Pretty good service

[mhl]

Update - after 5 or 6 iterations, SAS tech support have managed to solve this problem and I have a fix A variable was being overwritten when a long line of text was parsed from the firefox cookies.txt file during an SAS scan. I guess a general update to take care of this will be released pretty soon.

Pretty good service for a user who only has the freeware version.

[HAN]

Cool!