Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[tuftedduck]

I am sorry that it is not working for you.

I don't use AVG any more so cannot test the thing for myself, but I will trawl through the AVG forums until I find the discussion where I first read about this, and post the link.

[kitz]

Thanks TD

I did try have a look myself - and came across a few similar to this.

Obviously that one is a case of AVG wrongly profiling a prog and in cases like that they will normally then update their records to say the prog is ok.  Which I hardly think they are likely to do with some of my files. :/


I noticed this

AVG Free doesn't have an exclude feature... that is available only in AVG Pro but Grisoft responds very quickly to the reports.

which doesnt look too promising. :/

[mr_chris]

I suppose they do need to reserve some functionality for the pay version... I think providing what they do for free is brilliant

[tuftedduck]

I have done a bit of homework, and the facility that I described applies only to certain files as noted below which are liable to be changed following Windows updates/patches and which change makes AVG suspicious.

kernel32.dll Change C:\WINDOWS\system32\kernel32.dll

user32.dll Change C:\WINDOWS\system32\user32.dll

shell32.dll Change C:\WINDOWS\system32\shell32.dll

ntoskrnl.exe Change C:\WINDOWS\system32\ntoskrnl.exe

So it is not a general "exclude" function.

I also mentioned the facility was enabled by clicking the F3 key whilst the scan result window was open. Another error on my part, it is when the Test Centre window is open 


Please accept my apologies for leading you astray. It was not my intention to do so, I am sorry for the confusion that I caused.

[kitz]

>> It was not my intention to do so, I am sorry for the confusion that I caused.

Im sure it wasnt - No worries TD
- Honestly it was worth a shot and it made me delve a bit deeper into AVG than I had done previously.

[mr_chris]

Heh.. if nothing else it gave our F3 keys a bit of a workout

[kitz]

lol - too damn right 

[ken_1947]

I have done a bit of homework, and the facility that I described applies only to certain files as noted below which are liable to be changed following Windows updates/patches and which change makes AVG suspicious.

kernel32.dll Change C:\WINDOWS\system32\kernel32.dll

user32.dll Change C:\WINDOWS\system32\user32.dll

shell32.dll Change C:\WINDOWS\system32\shell32.dll

ntoskrnl.exe Change C:\WINDOWS\system32\ntoskrnl.exe

So it is not a general "exclude" function.

I also mentioned the facility was enabled by clicking the F3 key whilst the scan result window was open. Another error on my part, it is when the Test Centre window is open 


Please accept my apologies for leading you astray. It was not my intention to do so, I am sorry for the confusion that I caused.

I have found that by removing the file avg7qt.dat from the C:/ drive, avg nolonger finds these files suspicious and updates no longer require a boot. Suggest renaming the avg7qt.dat file and running an avg scan that will create a new one. If something odd should happen you can revert back to the old .dat file by removing the new one (assuming it got created as it did for me) and renaming the original back.

Ken

[Astral]

Welcome to the forum, Ken.

[kitz]

Thanks for the suggestion

and welcome to the forum