This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Knowledge Base
- :
- InstallScript MSI Setup Exe Fails to Launch When Located on a Root Directory
Subscribe
- Mark as New
- Mark as Read
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
InstallScript MSI Setup Exe Fails to Launch When Located on a Root Directory
InstallScript MSI Setup Exe Fails to Launch When Located on a Root Directory
Summary
InstallScript MSI installer packages created with InstallShield 2018 SP1, fail to launch when located directly on a root folderSymptoms
When creating an InstallScript MSI release using the Traditional Style on InstallShield 2018 SP1, and then launching the installer from a root directory (e.g. C:\setup.exe), the installer will begin to launch but immediately exit. Running the installer with /debuglog parameter will show the following error in the InstallShield.log:Launch result 1, exit code -1073741819The issue will also occur if launching from the root directory on a CD, DVD, ISO, USB flash drive, or any other storage device. Launching the installer from a subfolder in the root directory does not reproduce the issue (e.g. C:\subfolder\setup.exe). This issue also does not reproduce on InstallShield 2018 (without SP1) and prior.
Cause
This problem has been reproduced and determined to be an issue in our software.Steps To Reproduce
- Create a new Installscript MSI project
- Keep the InstallScript User Interface Type setting to Traditional Style
- Build a Setup.exe installer
- Move the Setup.exe to any root directory such as C:\
- Attempt to launch the Setup.exe
Resolution
This issue has been submitted to our Engineering team as Issue# IOJ-1881479. Our Engineering team is investigating this issue, but at this moment, there is no estimated time frame for when it will be fixed.Workaround
- Downgrade to InstallShield 2018 (without Service Pack 1 applied) or any prior version.
- Use the New Style UI (InstallScript Engine as an Embedded UI Handler). More information on this topic can be found here.
No ratings