Please note that Studio is not compatible with machines that have the KB4055002 update on Windows 7 SP1 and Windows Server 2008 R2 SP1, and stops working. If you have this operating system version, we recommend you manually uninstall this .Net framework update and install the next version - KB 4055532.
- Windows 7 update KB 2533623 (required by OCR Activities)
- Windows 7 N
- Windows 7 SP1 Update for Universal C Runtime
- Windows 8.1
- Windows 8.1 N
- Windows 10
- Windows 10 N
- Windows Server 2008 R2 update KB 963697, KB 2999226, and the Desktop Experience feature
- Windows Server 2012 R2
- Windows Server 2016
- Citrix environments (!) - click here for the full list.
- minimum: 4.6.1
Please note that if your machine runs Windows OS in Japanese, make sure to install the corresponding language pack for the .Net framework version you are using. This is required for running Studio in Japanese.
(!) Studio can be installed in Citrix environments, but there are certain issues that arise:
- The licensing information is not persistent;
- The name of the machine changes every time it is spawned or the user logs in.
The first problem always occurs with Citrix environments, however, there are workarounds that can help:
If the machine name changes, it is possible to create a task that activates the license every time the VDI is spawned or the user logs in. Also, a shortcut can be created that activates the license using the command line and then opens Studio.
If the machine name does not change, the licensing information can be stored in a persistent place for that instance (if it exists) to which all users have access. To do this, place the full path of the persistent location in the
license.config file, under the
<LicDir> tags, as in the following screenshot:
Updated 3 months ago
|Activating your Studio License Locally|