Michael, Have a look @ these 2 articles…
[1] (http://avgclick.me/reportafalsedetection)
[2] (http://avgclick.me/AddException)
AVG Guru
Hi, I have informed AVG of the false detection, but in terms of the other suggestion, putting the OED folder on the 'exception' list won't work, as the problem files are all ~temp and stored in c:\windows\temp. Would it be wise to make the whole \temp folder and exception? I haven't tried that yet. I'm guessing that the OED creates a ~temp file as it boots -they all have different numbers, such as ~CRF090E.TMP.
Any other thoughts would be welcome. Thanks
Does anyone have any thoughts on this one? Or will AVG continue to block a perfectly good program?
Many thanks,
Mike
I am running the OED dictionary (V2) on my XP computer. One of the files associated with this dictionary is labled a Win32/Heur virus. It is a temp file with a varying number. Earlier versions of AVG did not block this file (an action that stops the OED from running). So if I want to run the OED I have to disconnect my computer from the internet and switch off AVG. Any suggestions as to how I can get AVG to accept the dictionary program?
Does anyone have any thoughts on this one? Or will AVG continue to block a perfectly good program?
Many thanks,
Mike
Hi, I have informed AVG of the false detection, but in terms of the other suggestion, putting the OED folder on the 'exception' list won't work, as the problem files are all ~temp and stored in c:\windows\temp. Would it be wise to make the whole \temp folder and exception? I haven't tried that yet. I'm guessing that the OED creates a ~temp file as it boots -they all have different numbers, such as ~CRF090E.TMP.
Any other thoughts would be welcome. Thanks
Michael, Have a look @ these 2 articles…
[1] (http://avgclick.me/reportafalsedetection)
[2] (http://avgclick.me/AddException)
AVG Guru