If you find this kind of error in the log file, a simple fix would be to navigate to the Organizations Page, select the component with the issue, and check the “Never Overwrite” option.Īs previously stated, the above option does not mean it’s 100% a fix, and each MSI will differ from another, so you need to be prepared for it. Most likely the issue will appear when a file that is the key of a certain component needs to be verified to see if the component is overwritten or not. Logs can be used to uninstall software as well as install software. We need to analyze from that point backward to see what is happening. By searching for the MSI.CHM file in MSIEXEC, you can find a list of switches for logging.The return value of 3 will find the point where the error appeared in the log.For more information about these values, check this article.

Once you have your log file created, open it and search for “return value 3”.Here's what we need to do to find out why your MSI is asking for its sources: It's worth mentioning that this debugging solution is not an exact science and it is not really meant for beginners. This is the solution we recommend - try to debug the MSI to find out why it is asking for media during the upgrade or uninstall operation.įor repair operations, there is nothing to debug and you should use only one workaround for that scenario. 2 Answers Sorted by: 2 This is not a native Windows Installer UI.

Snagit msi installer