Weird exclusions in Standard Shield

[RejZoR]

I just wanted to add some exclusions to avast! and encountered this (see image below). I don't think it should be like this...



Vlk/Igor, any thoughts what this might be?

[igor]

Can you describe what exactly did you do (i.e. what you entered, and if you remember, what was the status of the exclusions before that? - were you running on default, or did you do any changes previously?)
Thanks.

[Vlk]

Also, what does "encountered" mean, exactly?
You inserted your exclusion, and then it got messed like this, or you just opened the window to add your exclusion, and it was already like this?

BTW could you please send me the file <avast>\data\avast4.db for futher examination?

Thanks
Vlk

[RejZoR]

Nevermind, looks like something got corrupted along the way. I've reinstalled it and now it's all fine.
Sorry for false alarm

[igor]

Hmm, it might be connected to the changes in the default extensions, made in the last update. So, if there's really a problem there, we'd like to find it... but it seems to work correctly here. 
 On the other hand, it's a strange coincidence that it appeared just know, shortly after the update. Do you remember the customization you've done?

[RejZoR]

It wasn't anything special, just regular tweaks in Program Settings (not even exclusions related).
However i did have a complete system crash last night when i overclocked my memory to 1GHz (from stock 800Mhz).
It was stable for time being but it locked up sometime in the morning. So technically this could be the reason.

[Lisandro]

Just to report, everything fine with both Standard Shield and Program Exclusion lists on XP SP2 and avast 4.7.1029.