Hi
After executing Grimefighter I performed the analysis again and got the same story.
5 applications that I don’t need
10 config system
3GB of garbage.
So… What happened? Did it work?
This is all about trust in AVAST!!! I hope that you realize that our computers are in your hands,connected to the net.
Can you convince me that it worked? and remove from my head the doubt of what was doing the application during 2hs having access to my personal computer/data.
Thanks for your answer.
Yes, I executed the tool in Grimefighter mode and after reading the results, re start Windows. Then, being curious I re ran the scan and Grimefighter performing issues analysys result is the same, as if I never execute Grimefighter.
I can only suggest looking in the F.A.Q. link that I gave as I don’t have any personal experience with GrimeFighter (GF).
I do know that there is only limited functionality in the free version, but that should still be able to remove that content if you elect to clean it. This could possibly mean that the recurrent items aren’t covered by the free GF version.
Have you got the paid version of GF ?
Edit - extract from f.a.q. (so worth looking):
[b]Can I view details of what Avast GrimeFighter will optimize?[/b]
Upon the completion of an Avast GrimeFighter scan, you will be provided with an option to review and modify any of the recommended changes before performing the final system cleanup. This will take you to a list of all the unnecessary and sometimes malicious files which are slowing down your computer, and here you can also easily set which action you want to apply for each item, one by one.
Can you please mention what version of Avast you are running and what OS? You can find the Avast version by opening the program, going to Settings, and then About Avast then program version.
OS + Operating System, which includes this information - Windows 7, SP1, 32bit.
e.g. what version of windows, its SP (Service Pack) number, it includes (as you put) if the OS is 32bit or 64bit.
Thanks for reporting this issue. It is a bug we are aware of. A fix won’t make it into the release planned for tomorrow but will be included in a update that should go out in the next couple of weeks.
It’s basically a flaw in the grime detection logic that needs updating/testing.