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 Forum
- :
- It works
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 13, 2016
01:27 PM
InstallScript Setup Launcher Unicode has stopped working
Updated from Installshield 2015 to 2016. Now some of our customers are getting the error "InstallScript Setup Launcher Unicode has stopped working" when running our install package. See attached image. We use Installscript.
Is there a fix? Otherwise I'm going back to 2015.
Brent
Is there a fix? Otherwise I'm going back to 2015.
Brent
(7) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 17, 2016
02:46 PM
Brent,
If you are seeing this issue on Windows Vista, 2008, 7, or 2008 R2, this is likely related to this issue.
Please try the following:
[LIST=1]
Download the attached zip file
Make a backup copy of \Program Files\InstallShield\2016\Redist\Language Independent\i386\ISP\setup.exe
Extract the downloaded zip file to \Program Files\InstallShield\2016\Redist\Language Independent\i386\ISP; this should extract a new setup.exe
Open InstallShield and rebuild your InstallScript project and test on the machines where this failure is occurring
Please let me know if you have any issues.
If you are seeing this issue on Windows Vista, 2008, 7, or 2008 R2, this is likely related to this issue.
Please try the following:
[LIST=1]
Please let me know if you have any issues.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Nov 07, 2016
01:31 PM
Do you have a copy for 2015, we're starting to see this error in 2015 as well
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Nov 08, 2016
02:44 PM
The customer can now install from 2016 thanks to the below patch (I hope). Do you have a setup.exe patch for 2015 or can I use the same one in the below zip?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Nov 10, 2016
12:03 PM
At this time we would recommend using IS 2015 SP1 without hotfix IOJ-1745445 installed. This would provide functional parity with the updated setup launchers posted earlier in this thread for IS 2016.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 23, 2017
01:14 PM
joshstechnij wrote:
Brent,
If you are seeing this issue on Windows Vista, 2008, 7, or 2008 R2, this is likely related to this issue.
Please try the following:
[LIST=1]Download the attached zip file Make a backup copy of \Program Files\InstallShield\2016\Redist\Language Independent\i386\ISP\setup.exe Extract the downloaded zip file to \Program Files\InstallShield\2016\Redist\Language Independent\i386\ISP; this should extract a new setup.exe Open InstallShield and rebuild your InstallScript project and test on the machines where this failure is occurring
Please let me know if you have any issues.
Is this fix going to be rolled out to InstallShield 2015 Professional as well?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 24, 2017
05:15 PM
If I log into the Product and License Center and go to "Release Archive" and 2015 I see two entries there like these
InstallShield 2015 SP1 Professional (Full Download) - 219.3 MB - InstallShield2015SP1ProfessionalComp.exe
InstallShield 2015 SP1 Professional (Web Download) - 5 MB - InstallShield2015SP1Professional.exe
One would hope that if the fix is in SP1 Premier that it would be in SP1 Professional, too.
Might be worth a shot.
Chad
InstallShield 2015 SP1 Professional (Full Download) - 219.3 MB - InstallShield2015SP1ProfessionalComp.exe
InstallShield 2015 SP1 Professional (Web Download) - 5 MB - InstallShield2015SP1Professional.exe
One would hope that if the fix is in SP1 Premier that it would be in SP1 Professional, too.
Might be worth a shot.
Chad