I thought so. It must be the initialization of the "MAPI" unpacker. I've seen similar stuff in the past.
There's currently not an easy workaround I'm aware of. Well let me think.....
Avast reads the path to the mapi dll from the following registry location: HKEY_LOCAL_MACHINE\SOFTWARE\Clients\Mail\Microsoft Outlook, value called "DllPath".
If you patch this value (normally i think it's "mapi32.dll", so change it e.g. to "_mapi32.dll" - simply to prevent avast from finding the DLL), it should "fix" the problem.
This change should not affect Outlook in any way but may affect other programs (that work similar to avast) - e.g. some PDA/cellphone synchronization stuff etc...
This is a just a temporary solution. Just make sure to put the original value back after the next avast program update - which will fix the problem by itself. Or, use the Aavm4h.dll patching method described in my next thread below.
Thx Vlk