Actually there has been an attempt to fix this issue in the latest avast version (4.6). So if your previous experiments were based on avast 4.5 (or older) and and you have 4.6, chances are the fix actually worked.