Please don't give up without at least trying 6.0.945 I have found it to be more stable than 5.1.xxx Avast has moved on to 6.0.xxx and are currently working out all the kinks before final release.

Ok, then.

Some more tests. For these tests, I’ve used two virtual apps, the minimal one as described in one of my previous posts (cmd.exe) and a full GDI one. Let’s call them MINIMAL and FULL respectively. Both packages have been created with ThinApp 4.0.4 and 4.6.0.

The results:

Avast 6.0.945 Beta + ThinApp 4.0.4:

  • MINIMAL=OK
  • FULL=OK

Avast 6.0.945 Beta + ThinApp 4.6.0:

  • MINIMAL=“The application failed to initialize properly (0x0000007b)”
  • FULL=BSOD STOP 0x00000050

Avast 5.0.507 Release + ThinApp 4.0.4:

  • MINIMAL=OK
  • FULL=OK

Avast 5.0.507 Release + ThinApp 4.6.0:

  • MINIMAL=OK
  • FULL=BSOD STOP 0x00000050

I’ve also tested the Avast 5.0.677 Release.

Avast 5.0.677 Release + ThinApp 4.0.4:

  • MINIMAL=OK
  • FULL=OK

Avast 5.0.677 Release + ThinApp 4.6.0:

  • MINIMAL=OK
  • FULL=BSOD STOP 0x0000000A

So far, the 6.0.945 seems to be based on the same branch as 5.0.x which behaves “better” than the 5.1.x stuff. Better here means that at least all ThinApp 4.0.4 packages work.

But, the problem remains in Avast 6. ThinApp 4.6.0 (or any ThinApp > 4.0.4) packages don’t work.

FYI, one of the differences between ThinApp 4.0.4 and 4.6.0 is that 4.0.4 use “stubs” to launch apps where 4.6.0 doesn’t. Those stubs may help Avast antivirus to make its job. Unfortunaly, those stubs are one of the things we want to avoid now to increase the control over virtualized applications.

Hope that may help. Good luck.

Regards,