Installation Results in "Setup Launcher Unicode Has Stopped Working"

[#1]

Summary

Discussion about the problem and cause during installation of message "Setup Launcher Unicode Has Stopped Working"

Symptoms

During installation the setup will display an ?Setup Launcher Unicode Has Stopped Working? error message as the product is installing.

Cause

The InstallScript engine expects values for user shell folder paths. You may experience a problem if any of these do not exist or are not available. As a next step ensure the following shell folder paths exist:

- CSIDL_PERSONAL
- CSIDL_APPDATA
- CSIDL_COMMON_APPDATA
- CSIDL_LOCAL_APPDATA
- CSIDL_FONTS
- CSIDL_PROGRAMS
- CSIDL_COMMON_PROGRAMS
- CSIDL_DESKTOPDIRECTORY
- CSIDL_COMMON_DESKTOPDIRECTORY
- CSIDL_STARTUP
- CSIDL_COMMON_STARTUP
- CSIDL_STARTMENU
- CSIDL_COMMON_STARTMENU

Resolution

In some cases we have seen an issue with CSIDL_STARTUP in particular. Please ensure this directory exists. If the directory does exist and you have the error change the path in an effort to "delete" this directory. Then manually create the path and test again.

CSIDL_STARTUP is the file system directory that corresponds to the user's Startup program group. The system starts these programs whenever the associated user logs on. A typical path is C:\Documents and Settings\username\Start Menu\Programs\Startup.

Another workaround is to create a new user on the client. When the new user is created it is expected the directories will be available.

Additional Information

Please Reference Microsoft articles:

KNOWNFOLDERID

CSIDL