windows-installer

问题 In my powershell script, I need to run couple of msiexec commands quietly. The problem is when I try to run the command, the Windows Installer help popup shows rather than executing the command. (Below Image) The same command runs well in cmd. Below is my command. I have kept the & in the command in double quotes to consider it as a string as suggested. & msiexec /log c:\msxml.log /quiet /I "&" D:\LoadGeneratorsetup\prerequisites\msxml6\msxml6_x64.msi I tried using Start-Process -FilePath to

问题 In my powershell script, I need to run couple of msiexec commands quietly. The problem is when I try to run the command, the Windows Installer help popup shows rather than executing the command. (Below Image) The same command runs well in cmd. Below is my command. I have kept the & in the command in double quotes to consider it as a string as suggested. & msiexec /log c:\msxml.log /quiet /I "&" D:\LoadGeneratorsetup\prerequisites\msxml6\msxml6_x64.msi I tried using Start-Process -FilePath to

问题 I have three products which have their installers in .exe files. Let us say the installers for the three three products are Product_A.exe Product_B.exe Product_C.exe I want to create a msi file using wix toolset which will install these three exe installers. What is the best way to do this? I am new to these so please help. Any example would be highly appreciated I also plan to uninstall these products once I uninstall my msi. Thanks in advance for any help 回答1: Tools : There are a number of

问题 I have a COM+ application that i am trying to install manually by double clicking on the .msi file but it gives error and fails to install the COM+ application. It doesn't create any entry in Component Services as well due to this error. I tried searching in registry as well but could find any entry with the COM+ application name. How do i resolve this issue? I need to install this COM+ application on my server. I have added screenshot of the error for reference. 回答1: Admin Rights : First of

问题 I have a COM+ application that i am trying to install manually by double clicking on the .msi file but it gives error and fails to install the COM+ application. It doesn't create any entry in Component Services as well due to this error. I tried searching in registry as well but could find any entry with the COM+ application name. How do i resolve this issue? I need to install this COM+ application on my server. I have added screenshot of the error for reference. 回答1: Admin Rights : First of

问题 I have some msi applications that are installed using a exe wrapper the exe wrapper appears to be passing in msiexec /i (msifile) /L(some logging path and options) is there a way to override these logging option so that it logs to the default location of C:\windows\temp and produce a full voicewarmupx log. I've tried setting DisableLoggingFromPackage to 1 in the registry but doesn't see to have any effect. DisableLoggingFromPackage = 1 I want to receive a full verbose log in the default

问题 I have an application packaged with MSI that is made into a WiX bundle together with various required third-party tools. I have disabled modify and repair actions in the MSI du to how the application works, to require full uninstall before installing the same version again. When I run the MSI separately, it works as expected: the installer cannot be run twice. The same applies when running the exact same Bundle again. But simply by rebuilding the bundle (using same UpgradeCode and Version ),

问题 I have an application packaged with MSI that is made into a WiX bundle together with various required third-party tools. I have disabled modify and repair actions in the MSI du to how the application works, to require full uninstall before installing the same version again. When I run the MSI separately, it works as expected: the installer cannot be run twice. The same applies when running the exact same Bundle again. But simply by rebuilding the bundle (using same UpgradeCode and Version ),

问题 I am working on a Wix installer to support Windows 7 SP1, Windows 8 and higher. I can successfully verify Windows 7 with Service Pack 1, however my windows 8 launch condition continually fails. My stripped back condition for windows 8 is, <bal:Condition Message="Windows 8 or higher supported...."><![CDATA[Installed OR VersionNT >= 602]]></bal:Condition> Log Entry [0638:0D20][2015-08-28T07:47:17]i001: Burn v3.9.1208.0, Windows v6.3 (Build 9600: Service Pack 0) [0638:0D20][2015-08-28T07:47:18

问题 We have a problem that a fie is not installed upon a major update We have a major update with <MajorUpgrade Schedule="afterInstallInitialize"... We an old component with 1 file (xyz.exe Version 12.34) from a external manufacturer We have now a new file from a new manufacturer and with the same name (xyz.exe Version 2.34). The new file has a lower version number than the old one. We created a new component in the install package and removed the old component (in fact we gave it a new guid)