OverviewTrueUpdate ServersSession VariablesThemeOptionsAdvanced
An exciting feature of TrueUpdate is the client's ability to update itself if a newer version becomes available. There are two parts in the client that may be updated: the client executable and the client data file. They are both part of the server configuration files that are updated each time a build is done. While TrueUpdate is able to update these files, they may exist in a location where the end user does not have write access. These settings allow you to configure how TrueUpdate should proceed if faced with this situation.
Tip: If the client executable or client data file is updated, the update process must be restarted. You can use the global variable _ClientRestarted to tell whether or not the client was restarted.
What should TrueUpdate do if a newer version of the client executable exists, but the folder is not writable. Choose from:
Notify the user that they do not have the appropriate permissions to update the client by showing and dialog and aborting the update process.
Ignore the new version of the client executable and continue by running the current copy.
Download the new version of the client executable to a temporary location (Windows Temp folder) and run it from there.
Note: Choosing this option may cause your update to function incorrectly if you are referencing files from your update that rely on the client's location such as _SourceFolder or %SourceFolder%.
What should TrueUpdate do if a newer version of the client data file exists, but the folder is not writable. Choose from:
Notify the user that they do not have the appropriate permissions to update the client by showing and dialog and aborting the update process.
Ignore the new version of the client data file and continue by running the current copy.
Download the new version of the client data file to a temporary location (Windows Temp folder) and run it from there.
This section specifies which requested execution level to include in the client update executable's application manifest for distribution on Windows Vista or later. Updates should generally always be built using the default "Require administrator" setting. Before changing this default setting, see Updates On Windows Vista or Later for important information concerning required changes to your update, and feature limitations.
Important Note: It is very important to make the correct decision when initially distributing your TrueUpdate client. Changing the manifest setting of the client in an update may cause it to fail. If an existing client was published using the As invoker setting, and you published again changing it to Require administrator, the automatic update of the client will fail to run the new update client.
Note: Changing the application manifest to "Highest available" or "As invoker" is only supported on Windows 2000 or later in TrueUpdate's design environment.
Note: For more information on the settings below and general Windows Vista/Windows 7/Windows 8/Windows 8.1/Windows 10 information, see Updates On Windows Vista or Later.
The update runs with the same access token as the parent process. For example, if the user is logged in as a standard user, those are the privileges they will inherit during the update. This option should only be used in special circumstances where you are certain you do not need access to protected areas of the operating system.
The update runs with the highest privileges the current user can obtain. This setting is designed for applications that can be run by all users. It is most useful for applications that require privileges above that of a limited user, but less than a full administrator.
The update requires to be run with the full access token of an administrator. Generally updates make changes to protected system locations that are typically writable to only by administrator users. This is the default setting for updates created with TrueUpdate.