Its related to superantispyware but I wondered whether anyone can help
I tried to run a complete scan but it hung on the file scanning phase yet the clock was still ticking, I tried to quit it but it wasnt responding so I had to manually restart my computer, what I would like to know is if any file corruption or anything similar may have occured as a result of me manually restarting as I appear to have more free space than I did before the forced restart, please help
Yes it can files in use could be damaged, though this is less of a problem if your are using NTFS file format and not FAT32 format. Even then it isnāt that common, when your system reboots it may jump into the chkdsk function because of the non-standard shutdown.
If you have to do this again, you should press and hold the power button in for five seconds, this attempts to close down as tidily as possible given the circumstances.
I would heed their advice and scan again, either that or uninstall because if you are worried you might as well not have it. I have never had any freeze during scans and I have always had the DDA function enabled from when it was introduced.
I also always pause the standard shield (not that I believe this had involvement) when I do an on-demand scan by any third party security application. This avoids any possible clash if a detection is made and it will also reduce the overall scan duration as there will be less duplication of files scanned.
I have NTFS file system and previous versions worked fine for me but since the latest versions have been out it has started freezing up, I may try their advice tomorrow as I could do with their software when the need arises. Also I always pause Avast before scans so thats not the problem. I will post back here if I need anymore help
ps why is NTFS file system different than FAT32 in regard to improper shutdown??? Is there anyway of seeing if any ācorruptionā has been caused as chkdsk didnt auto run on boot up?
Well the DDA access has been in SAS for a while now not just the latest version. I would suggest a visit to their forums and see if there are any similar topics. It might be worthwhile looking at the change log (like the avast version history) to see what was included in the last update.
Personally I wouldnāt be expending that much energy on it as this could have been nothing more than a one off hiccup, I only start chasing if something is a regular occurrence.
It is just the way NTFS is designed to be more resilient than old FAT32 file system.