In this case, unfortunately, SO didn’t tell us much that we didn’t know already (and indeed the tool we ultimately chose was not mentioned in any answer). However, I’m posting our experiences here, as they might be helpful to others later on. We (quickly) evaluated the following installer tools, mostly by looking at their websites … Read more
I believe your syntax is using the Win32_Product Class in WMI. One cause is that this class only displays products installed using Windows Installer (See Here). The Uninstall Registry Key is your best bet. HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Uninstall HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall UPDATE FOR COMMENTS: The Uninstall Registry Key is the standard place to list what is installed and what isn’t … Read more
Use TARGETDIR instead of INSTALLDIR. Note that the quote marks for TARGETDIR property are only around the path in the case of spaces. msiexec /i “msi path” TARGETDIR=”C:\myfolder” /qb Source: https://learn.microsoft.com/en-us/windows/win32/msi/targetdir
Every component has a key path; the most common is a file. Your component doesn’t have a file or other key path, so WiX gives it the default of a directory. Windows Installer then comes along and says that components with directory key paths must ensure the directory is created, even if something else will … Read more
Include this section in the program’s manifest file: <compatibility xmlns=”urn:schemas-microsoft-com:compatibility.v1″> <application> <!–The ID below indicates application support for Windows Vista –> <supportedOS Id=”{e2011457-1546-43c5-a5fe-008deee3d3f0}”/> <!–The ID below indicates application support for Windows 7 –> <supportedOS Id=”{35138b9a-5d96-4fbd-8e2d-a2440225f93a}”/> <!–The ID below indicates application support for Windows 8 –> <supportedOS Id=”{4a2f28e3-53b9-4441-ba9c-d69d4a4a6e38}”/> <!–The ID below indicates application support for Windows … Read more
The first and the last command lines are correct: msiexec /i “installer.msi” /l*v “log.log” msiexec /l*v “log.log” /i “installer.msi” And you can drop quotes in this particular case.
A much easier way than the posts above and with no extra code in your installer is to use the following: installUtil.exe /username=domain\username /password=password /unattended C:\My.exe Just ensure the account you use is valid. If not you will receive a “No mapping between account names and security id’s was done” exception
Please note that Microsoft has now released an official tool to resolve these issues, without the problems that previously existed with MSIZAP. Microsoft Fixit: Fix problems with programs that can’t be installed or uninstalled
This is a common question. I don’t do it with just a custom action. The only way I know, is to modify the .msi after it has been generated. I run a Javascript script as a post-build event to do exactly that. It inserts a new dialog in the installer wizard, with a checkbox that … Read more
Warning: The application will end up running as a high privilege account, which has security and user experience implications. To run any application after the installation is complete, Right-click on your setup project, click on Custom Actions. Then right-click on Commit, Add Custom Action, and choose the file you would like to run. (Note that … Read more