Adobe Acrobat X using Adobe PDF printer to create PDFs from .DOC(X). It just starts Word and print document.
The splwow64.exe process is used to translate the driver model of a 64-bit operating system and a 32-bit program.
In case when Splwow64.exe starts in external environment thinapped Acrobat can't finish PDF generation.
Winword.exe create PDF in Desktop or MyDocuments folder, but PDF file must be created in Temp folder with name like AD3455.tmp.
Acrobat searching for the file in Temp folder infinitely. It seems like Acrobat can't send printing parameters to external application.
This happens with Thinapp 5.0, when using Thinapp 5.1 Acrobat X normally create PDF with external splwow64.exe.
I can use splwow64.exe in virtual environment but this approach has poor compatibility with other applications.
Acrobat thinapped with Thinapp 5.1 has other bugs, so now 5.0 is using.
What is standard approach to splwow64.exe, external or internal?
Why such different behavior between the same package build with 5.0 and 5.1?