http://bugs.winehq.org/show_bug.cgi?id=27425
--- Comment #2 from Hans Leidekker hans@meelstraat.net 2011-06-13 06:30:34 CDT --- This installer runs a subinstaller through a custom action (type 50) but doesn't specify a fully qualified path for the executable. I've sent a patch to pass the full command to CreateProcess and NULL for the app name which fixes this bug, but it was rejected.
AFAICS, the only way to make it work while passing the app name in the first parameter would be if the working directory on Windows happens to be the system directory (where msiexec.exe is located), but my testing shows that msi also runs explorer.exe from this custom action type which is not in the system directory.