Hi Francesco, As per your suggestion, I have started new topic here. My customers are facing this problem very occasionally. I have analysed this problem with multiple machine and the result are same. Finally, I am able to recreate this issue in version 18.08.0.2014 and 20.11.0.2016. Since this is n...

Hi,

Is there any workaround solution to fix this problem ?

Thanks,
Senthil

Thanks Francesco, I am using PDQ deploy(Push install tool). In which I am passing external file as parameter (components, language section and etc...) to install required feature on the target machine. So, I may not able to embed this file with MSI. Is there any option to copy files from GPOPATH dur...

Do you have any idea when this exit code 0 issue will gets fixed ? this is highly required feature in order to use 3rd party push installs. I had an another issue with exit code 0, when I pass the additional files as part of 3rd party push installs then its removes the source file from push installs...

Push installs receives the Install success state once MSI extraction process is done. This leads the wrong information to the caller. Also, noticed when logging the information using command line "Feature.msi /q /log output.log". Only logged till the point MSI gets extracted (Ignore using ...

Is there any way to create response file for .msi setup apart from creating our own custom INI file ?

Thanks Francesco,

I have updated the latest IA version 18 (18.08). Now, my problem got fixed and Arrow keys are working as expected.

Thanks,
Senthil

Dear FrancescoT,

I am currently using Installaware 18 (build 1.29.14). still I am facing the same issue. Do you have any idea when this issue will get fixed ?


Thanks,
Senthil

After adding custom message to the log file using $LOGGED$ variable, I could notice that there were some additional space added to each character except the custom line which was added in the first line of the below log file output. Once the Apply changes has been called then log information written...