Last week a colleague of mine had the infamous "InstallScript Setup Launcher Unicode Has Stopped Working" error again. I tried to assist him by checking the said folders and we ended up creating a new admin, but this time this did not help either. I told him that there is nothing I could do at this point and we decided to use an old version of our product that was still built with IS2012 (I have to wait until next year before budget allows me to buy IS2014).
Today my colleague called me that he was able to install the new version of the software because he found out which folder was actually missing! He was using Microsoft's Process Monitor from Sysinternals to inspect the Setup.exe's file access and there it was amongst a huge pile of successfull folder checks there was one that failed due to a missing folder... Created missing folder => Setup runs! Atta boy!
That might not be a complete solution but at least a work around for the desparate ones.
The fix for Windows 8 and Windows Server 2012 and up
The info above only works on Windows 7 and below.
Originally Posted by DaveSimmons
I found nothing else on how to fix it for Windows 8 / Server 2012 so I updated on my blog.
InstallScript Setup Launcher Unicode Has Stopped Working (Windows message)
I still see the same error in Install shield 2014 as well. Any idea what to do?
Well it looks like I'm now involved in this bug. We just upgraded to Installshield 2014 from 2012 Spring. It happens all the time even if you "Run as Administrator". I double checked that those folders were there as suggested in the earlier posts. Is there any resolution on this?
Not working on Server 2012 R2
Just adding my 2 cents to this thread. We upgraded from IS2012 spring to IS2013 because it supported Windows 8.1 and Server2012R2.
We have Software-As-A-Service on Amazon Cloud instances. Most of our clients use English. We have no trouble installing to those cloud instances. But the Chinese customer is producing this error message, even though we set the regional setting for that computer to English before attempting to install. These cloud instances are all Server 2012R2.
The instances are not new. We uninstalled our previous version before attempting to upgrade. We ran the setup.exe as an administrator. The username used was the administrator of that instance.