Well AVG Free started doing it again, just today in fact, although CCleaner is able to remove those bloated files.
I'm going to submit an updated AVG cleaning routine to MrG, so hopefully it will all be taken care of in the next CCleaner release so that other people don't have to deal with AVG bloating.
Earlier in the thread you said that CCleaner didn't clean the bloated files you had. Are the bloated files now in a different file/folder than before?
Earlier in the thread you said that CCleaner didn't clean the bloated files you had. Are the bloated files now in a different file/folder than before?
CCleaner didn't have the files listed in its cleaning routine, I had to add them in myself before submitting the updated AVG cleaning routine. Thankfully after adding those files "*.AVG" CCleaner deals with them, so by the grace of CCleaner I can continue using AVG without AVG becoming bloated.
I did in my "winapp2.ini" a entry for the $*.AVG files that emerged in mine "Avg7Data" folder.
Now I have the entry [*Grisoft AVG 7.5] - with ?*? to distinguish oneself from "winapp.ini", to follow the splendid JDPower'sugestion.
Thank you very much JDPower for this tip!
This is the updated AVG cleaner just in case someone else needs it now, versus waiting for it to become available
[Grisoft AVG 7.5]LangSecRef=3024Detect=HKLM\SOFTWARE\Grisoft\Avg7Default=TrueFileKey1=%allusersprofile%\Application Data\Grisoft|*.AVGFileKey2=%allusersprofile%\Application Data\Grisoft\Avg7Data|*.AVGFileKey3=%allusersprofile%\Application Data\Grisoft\Avg7Data|*.logFileKey4=%allusersprofile%\Application Data\Grisoft\Avg7Data\upd7bin|*.*FileKey5=%allusersprofile%\Application Data\Grisoft\Avg7Data\$history|*.*FileKey6=%allusersprofile%\Application Data\Grisoft\Avg7Data\avg7upd|*.logFileKey7=%windir%\All Users\Application Data\Grisoft|*.AVGFileKey8=%windir%\All Users\Application Data\Grisoft\Avg7Data|*.AVGFileKey9=%windir%\All Users\Application Data\Grisoft\Avg7Data\upd7bin|*.*FileKey10=%windir%\All Users\Application Data\Grisoft\Avg7Data\avg7upd|$historyFileKey11=%windir%\All Users\Application Data\Grisoft\Avg7Data\avg7upd|*.logFileKey12=%windir%\All Users\Application Data\Grisoft\Avg7Data|*.logFileKey13=%windir%\Application Data\AVG7\Log|*.log
I did in my "winapp2.ini" a entry for the $*.AVG files that emerged in mine "Avg7Data" folder.Now I have the entry [*Grisoft AVG 7.5] - with ?*? to distinguish oneself from "winapp.ini", to follow the splendid JDPower'sugestion.
Thank you very much JDPower for this tip!
Glad its been of use
Glad its been of use
I'm find pleasure in using your splendid and useful sugestion. And it is with real pleasure that I do that.
Thanks again.
.gif){kind=icon}
Andavari,
Why don't you give this solution its rightful place next to your RegSeeker customized exclude.ini file ?
That way more users can take advantage of this temporary addition.
Andavari,
Why don't you give this solution its rightful place next to your RegSeeker customized exclude.ini file ?
That way more users can take advantage of this temporary addition.
There's no need to do it because I submitted the updated AVG cleaning routine to the CCleaner developer MrG. It's just a matter of patience and to wait for the next CCleaner release, or whenever he decides to include it.
If it's to be included anywhere in the interim it can go into winapp2.ini, however I didn't submit it as a winapp2.ini entry because that thread clearly states to send updates to MrG if it's already an application cleaned by CCleaner.
It isn't going to be added in v1.40.520.