nikhil
nikhil

Reputation: 1748

Wix installer failed to execute exe package doing quiet install

I am trying to perform a quiet install of an exe file from FTDI drivers. I am getting these drivers from here. After downloading, when I 7-zip further extract the .exe, it creates a folder with dlls and dpinst-amd64.exe just as in the screenshot below. When I try the command

dpinst-amd64.exe /q /se

On command prompt, it works fine. But doing so with Wix installer is failing to run the package. However the other packages install fine within this code.

FTDI contents

This is what I have in the Bundle.wxs

<Chain>

      <ExePackage Id="FTDIDriversInstaller"
                  SourceFile="$(var.DependencyFolder)\FTDIDrivers_Setup\dpinst-amd64.exe"
                  InstallCommand="/s /se"
                  Compressed="yes"/>
            <!--VC++ Redistributable required to ensure the ADE installer executes without errors-->
            <ExePackage Id="VCRedistributableInstaller"
                        SourceFile="$(var.DependencyFolder)\VC_redist.x64.exe"
                        InstallCommand="/quiet /norestart"
                        Compressed="yes" />
<ExePackage Id="VCRedistributable2010Installer"
                        SourceFile="$(var.DependencyFolder)\VCREDIST_2010_x64.exe"
                        InstallCommand="/quiet /norestart"
                        Compressed="yes" />
            <MsiPackage Id="LicenseGeneratorInstaller"
                        SourceFile="$(var.ReleaseFolder)\!(loc.CULTURE)\FactoryToolsInstall.msi"
                        Compressed="yes"
                        DisplayInternalUI="yes" />
            <ExePackage Id="AccessDatabaseEngineInstaller"
                        SourceFile="$(var.DependencyFolder)\AccessDatabaseEngine_X64.exe"
                        InstallCommand="/quiet"
                        Compressed="yes" />
                                
        </Chain>

This is what I see in the log file:

Upvotes: 0

Views: 73

Answers (1)

Rob Mensching
Rob Mensching

Reputation: 36006

You probably need to add all those loose files as Payload elements under the dpinst ExePackage element so they are all available when the command runs.

Upvotes: 1

Related Questions