Would writing exclusions for archive file type extensions be a workaround for that problem, SivaSuresh? As in put *.rar in the exclusions?
I tried sometimes and it works. But, you have to manually add many kinds of archive extensions to the exclusion list. It's tidious but works.
But, as I already mentioned, I am tired of doing all these workarounds. I am just disabling the whole archive scans at the expense of some loss of security.
The only cases when we face a security breach is where we scan some folders, feel them as secure and for some reason switch off CAV and D+ to run them. It happened to me twice with two installers, since I got too many D+ alerts and slow performance if I ran them with CIS on. Only in such cases, it causes an infection. Otherwise, the CAV realtime agent would catch the malware inside an SFX archive when it executes and extracts itself in memory.
Hope this clarifies the issue to you.
I am still waiting for a proper solution from the DEVs.