msiexec

问题 This question is asking whether one of the ICE57 validators creates a false positive error report. I am using WIX 3.9 to generate an installer. I want a per machine installation with non advertised shortcuts. This WXS example installs a text file and a shortcut to open the text file: <?xml version="1.0" encoding="UTF-8"?> <Wix xmlns="http://schemas.microsoft.com/wix/2006/wi"> <Product Id="*" Name="ShortcutTest" Language="1033" Version="1.0.0.0" Manufacturer="Widget Co" UpgradeCode="--YOUR

问题 I have been asked to only deploy files that are bundled into MSI package. MSI contains 4 files, For that I'm using this command: `msiexec /a [path to MSI] TARGETDIR =[Application folder path]` Problem with above command is that it also deploys .MSI file to specified TARGETDIR which i don't want. Is there any workaround/way that i can only deploy that 4 files? 回答1: Not to my knowledge, no. This is an administrative installation, and it is essentially just an extraction of the files embedded in

问题 I have an existing MSI package which I want to repackage to add installation options (so far the MSI has been installed through the command line with msiexec parameters in a .bat file). Are there, as of today, freeware tools available to repackage the MSI? I was stumbling over WiX but as per my understanding I need VisualStudio to complete what I wanted (I dont have VisualStudio)? Thank you! 回答1: What exactly do you want to add to the MSI package? You could use Orca to modify any table in the

问题 We install an application (MSI) using MSIEXEC with the following command line option: MsiExec.exe /x{code} /qn /liwearucmopvx+ C:\Log\UnInstall.tra MsiExec.exe /iC:\Source\App.msi /qn TARGETDIR=C:\Install ALLUSERS=1 /liwearucmopvx+ %C:\Log\Install.tra Most of the time this works, but sometimes the uninstall fails (not sure why yet, looking into the error). Anyways when this happens I get the following error during the re-install: Another version of this product is already installed.

问题 We are having a System.BadImageFormatException in our MSI installers. I have already read about the target frameworks, but we already checked and it's targeting the correct framework ( .NET Framework 4.5 same with our QA machines). We have exactly the same source codes, but the results of the msi installer compiled by our 'build team' fails, but the msi installer compiled by us 'dev' works. Question is, does the environment where an application was built and compiled affects the output

问题 We are having a System.BadImageFormatException in our MSI installers. I have already read about the target frameworks, but we already checked and it's targeting the correct framework ( .NET Framework 4.5 same with our QA machines). We have exactly the same source codes, but the results of the msi installer compiled by our 'build team' fails, but the msi installer compiled by us 'dev' works. Question is, does the environment where an application was built and compiled affects the output

问题 We're currently using a GUID to identify the application when running our uninstall script which contains msiexec. The problem I'm having is the GUID changes every time I install the latest version of the application, so I was wondering if there is a different way that I can identify our application running using msiexec? 回答1: The usual way that people get around the various ProductCode values in this situation is to start with the more constant UpgradeCode. Given the UpgradeCode, you can use

问题 I added a custom action that should kill my application using taskkill CMD when someone tries to uninstall it using the add/remove in the control panel using the following code : <Property Id="TASKKILL"> <DirectorySearch Id="SysDir" Path="[SystemFolder]" Depth="1"> <FileSearch Id="taskkillExe" Name="taskkill.exe" /> </DirectorySearch> </Property> <CustomAction Id="ServerKill" Property="TASKKILL" Execute="immediate" Impersonate="yes" Return="ignore" ExeCommand="/F /FI "IMAGENAME EQ App.exe""/>

问题 I tried msiexec /i "yarn-1.10.1.msi" TARGETDIR="C:\programs" /qb It installed but not in TARGETDIR, did I miss something ? 回答1: You can try the following command line instead: msiexec.exe /i "yarn-1.10.1.msi" INSTALLDIR="C:\programs" /qb Standards Compliance : Installing underneath %ProgramFiles% is always recommended. Creativity in deployment is generally always overrated and usually causes unnecessary problems. However, you could have an SOE setup that requires custom paths? Path Update : A

问题 When I try to install my SQL Server 2008 R2, it keeps getting stuck at SqlEngineDBStartConfigAction_install_configrc_Cpu64 I found in other issues that I should kill the msiexec process but I can't find it. What should I do? Thank you 来源： https://stackoverflow.com/questions/53363429/sql-server-2008-r2-install-stuck