avast4.ini File Modification alert on avast.setup

[DavidR]

OK thanks, I shall worry you no further, happy in the fact it has been found and it will soon be resolved.

[Rednose]

I second that ( I just came here for the same issue )

Greetz, Red.

[Vlk]

The problem should be solved in build 1187.
http://forum.avast.com/index.php?topic=34612.msg295052#msg295052

[DavidR]

Yes the problem appears to have been solved, though the random nature of the problem it would take a few updates to be 100% sure.

Straying slightly off-topic but still related to the avast4.ini modification issue. I have however noticed another inadvertent consequence of the other changes made in the update.
 

The beta has now been updated to v4.8.1187.
<snip>
Main changes in this release:
- solved the intermittent self-defense process identification issue (resulting e.g. in random INI modification consent dialogs)
- attempt to solve a synchronization problem in the AV engine initialization
- changed the way INI modification consent dialog is shown. Now, it is shown only if notepad.exe is trying to access the file

Namely the - "changed the way INI modification consent dialog is shown. Now, it is shown only if notepad.exe is trying to access the file"

Now I tend not to use notepad as I had mentioned previously but Editpad Lite, now if I do that, yes there is no consent dialogue shown, but the file is opened as read only (see Editpad Lite warning image) and this isn't at all helpful, in fact I would say it is a worse consequence (as this replaces one pop-up with another and effectively blocks editing the avast4.ini with anything other than notepad).

[igor]

I'm afraid it's not inadvertent, but deliberate - that's what the changelog item means.

There probably will be another switch in avast4.ini where you can add another editors (to show the consent dialog for) - but yes, this will be the default behavior (i.e. you'll have to use Notepad at least to add the alternative editor filename into the new option).

[DavidR]

I would say that switch is a necessary change to allow consent in other editors, as to force all those who have chosen a better editor to use notepad spit, sucks is a little draconian. OK just for avast4.ini is a minor exception, but the sooner the switch is implemented in avast4.ini the better.

Any time scale on this, what section of avast4.ini and what the switch might be ?

[igor]

Before the final release, i.e. in a few days.

[DavidR]

Thanks.

[Vlk]

The INI option is already there.

[SelfDefense]
IniChangeConsentProcesses=notepad.exe,youreditor1.exe,youreditor2.exe

Etc...
Leave notepad.exe in the list unless you don't want it to be on that list.

Cheers
Vlk

[DavidR]

Great, will add EditPadLite.exe now.

Edit: I had to enter the new switch line and notepad.exe (followed by ,editpadlite.exe) as the line wasn't there. I assume that it wasn't there as notepad is a default action so not required in the avast4.ini file ?

Edit2: I tested the switch after the edit (in notepad) and accepted the change. However, it didn't have any impact, it still caused the alert when using editpadlite.exe. So I assume a reboot is required to have the changes take effect ?

My switch line:
IniChangeConsentProcesses=notepad.exe,EditPadLite.exe

[DavidR]

Either the option isn't there (as I have done a reboot) or the switch name is incorrect or my idea of what this switch does differs from Alwils.

I tried to open avast4.ini with editpadlite.exe and the avast4.ini file modification alert fires off. At least you can answer Yes and get in to edit rather than it being set to read only.

So is that the intended action to allow listed applications access to avast4.ini via the pop-up rather than having read only permission ?
Or should it allow direct access to avast4.ini without the pop-up ?

Having notepad.exe in the IniChangeConsentProcesses doesn't pop-up the same avast4.ini file modification alert. So that must be contained elsewhere and in effect the notepad.exe doesn't need to be on that line ?

[igor]

So is that the intended action to allow listed applications access to avast4.ini via the pop-up rather than having read only permission ?

Yes, exactly.

Having notepad.exe in the IniChangeConsentProcesses doesn't pop-up the same avast4.ini file modification alert. So that must be contained elsewhere and in effect the notepad.exe doesn't need to be on that line ?

Are you sure?
Note that notepad.exe does not open the file for writing until you really select "Save" or close it (after having done some changes).
I.e. pure opening a file in notepad doesn't trigger any warning, because it only reads the file into memory.

[DavidR]

I wasn't aware that notepad didn't initially open it for write permission. So if the file isn't opened for writing (regardless of the program opening it) that switch is ignored, as would seem to be the case as I can also open it with wordpad without the modification alert. Presumably that wordpad acts in the same way loads into memory not for writing.

I would have thought that my adding it to that line/switch would alter how avast deals with it, obviously not, as the opening to read doesn't trigger the alert. So I tried opening it with firefox and that too is read so doesn't trigger the interrogation.

If that is the case then notepad.exe isn't required on that switch and probably why there was no IniChangeConsentProcesses line in avast4.ini in the first place.

[igor]

The line wasn't there because it's new, and it has a default value used when the line is missing - so, if it's not there, it's the same as if "IniChangeConsentProcesses=notepad.exe" was there.
Without it, you wouldn't be able to save the modified .ini file from Notepad.

[DavidR]

OK thanks for the update.