@ bong2x
1. I generally don't mess with the ini file and should really only be done for a specific purpose and when suggested. Your image only shows a very limited subset relating to what can be put into the avast5.ini file. These are commonly settings which are either not present in the avastUI or changes to default settings in the avastUI.
The only option in the avast5.ini in your image relating to the anti-rootkit scan is if it should run or not.
2. I don't believe the avast settings, exclusions work in the anti-rootkit scan (technically I would say it isn't an on-demand scan), exclusions are one of the things which can be added in the avast5.ini file for the rootkit scan. However, I never recommend exclusion, where ever they might be unless you are 100% sure that they are clean/clear and that certainly isn't the case here.
So suggesting exclusion in this case is wrong3. If the user chooses to check the don't show this again, then that option must be recorded somewhere and the avast5.ini file seems a prime candidate. The intention was for simran.k to
Look for any such entry and report not
Modify the avast5.ini.
@ simran.k
As strange as it may seem in this case Ignoring it is best, but always submit it to the labs, this will push for it to be analysed.
the file it keeps flagging is c:/windows/system32/explore.exe this is the HCL file..
What do you mean this is an HCL file as there are many Definitions for this acronym ?
The file name seems to be playing on what are legitimate file names, explorer.exe (windows explorer) and iexplore.exe (Internet Explorer). I have no such explore.exe on my system, so I have to wonder as to its legitimacy (there are instances of this explore.exe being a virus, see below) or if you made a typo in recording the file name ?
http://www.bleepingcomputer.com/startups/Explore.exe-14978.html