Skip to main content

Windows GUI setup

The Thinkwise Windows GUI is launched by double clicking the shortcut to the Windows GUI executable.

Windows GUI shortcut

If the GUI is started without a configuration file the dialogue as shown below will open. Here, the correct data must then be manually entered in order to start.

Windows GUI logon dialog

For convenience, it is possible to create a configuration file (.ini) which determines the default settings used. Launching with a specific configuration file can be done as follows:

  • The configuration file can be dragged on the executable (TSF_dotNET.exe or TSF_CS.exe) icon; or
  • A shortcut can be made to the executable, where the path to the configuration file is specified as the parameter:

Shortcut with a "default.ini" configuration file


With Thinkwise ClickStart, the Thinkwise user interface can be stored centrally in a network location and end users will only need a shortcut to the ClickStart executable*. When starting the Thinkwise Windows GUI via ClickStart, it will be checked whether a local copy of the Thinkwise GUI is present and if it is the same as the version on the server. If that is not the case, then the local Thinkwise GUI will be updated. After that, the application will be started.

If a new version of the GUI has to be deployed, then it is only necessary to update the central version. All clients will automatically get the new version upon startup. The advantage of ClickStart is that the GUI can be replaced on the server even when it is in use.

If ClickStart signals that a new version of the GUI is available, but the current version is in use, then a notification will show with the question of whether the user would like to launch the old version.

Current Windows GUI is in use


When starting the ClickStart executable (TSF_CS.exe), the settings from the clickstart.ini configuration file will be loaded before the local user interface, if necessary, will be updated. In the ClickStart configuration file, the following settings, among others, can be specified:

ProgramFilesLocationPath to the local copy of the user interface. In this path, a variety of environment variables can be used:

%APPDATA% - Local Application Data directory, for example C:\Users\[user]\AppData\Local
%PROGRAMFILES% - Program Files directory, for example C:\Program Files
%TEMP% - Temporary directory
%SOURCEDIR% - Directory name of the network location that the GUI is in. If this is, for example, T:\GUI\Production, then the variable has the value Production.

Default location: %APPDATA%\Thinkwise Software\GUI\%SOURCEDIR%\
IconThe icon that is displayed in the top-left corner of the ClickStart window, for example, image.ico
LogoThe logo that is displayed in the top-right corner of the ClickStart window, for example, image.svg (100x50 pixels)
TitleThe title of the ClickStart window, for example, Thinkwise ClickStart

For a complete overview of the available settings, see the clickstart_sample.ini file provided with the Windows user interface.


The use of Clickstart is not recommended for terminal server (or virtual app) environments.

Enable logging

To enable logging:

  1. Set the WriteLogToFile extended property to 'Ýes'.

  2. Set the LogSeverity extended property to one of the following values:

    • Error: log errors only.
    • Warning: log errors and warnings.
    • Info: log all messages. This is the most detailed level.

Was this page helpful?