The following requirements must be met on the target machine:

• Windows Vista, Windows 7, Windows 8 or 8.1, Windows 10 (both 32 bit and 64 bit versions)

• .NET Framework version 4.0 full (or above) installed

Use of Particular Actions

In case a Process includes a range of actions and you would like to produce executables of those, you would need to copy some particular files from your installation and paste them at the same location that the executable process will be launched.

Using the "Custom Dialog" action

Copy at the same folder as the executable the following file

  • C:\Program Files\WinAutomation\WinAutomation.Shared.Runtime.JsNativeResources.dll

Additionally, the settings mentioned here should be in place.

Using the "Exchange" group of actions

Copy at the same folder as the executable the following files

  • C:\Program Files\WinAutomation\Microsoft.Exchange.WebServices.Auth.dll
  • C:\Program Files\WinAutomation\Microsoft.Exchange.WebServices.dll

Using the "Chrome" or "Firefox" browsers

Install on the target workstation the Web extension that you can download from the link below

Using the "Tessaract" OCR Engine

Copy at the same folder as the executable the following files

  • C:\Program Files\WinAutomation\x86\liblept1744.dll
  • C:\Program Files\WinAutomation\x86\libtesseract400.dll
  • C:\Program Files\WinAutomation\x64\liblept1744.dll
  • C:\Program Files\WinAutomation\x64\libtesseract400.dll
  • Equivalent .traineddata for any additional language you are using within your processes which is located under C:\Program Files\WinAutomation\tessdata

NOTE: The links above apply on machines that WinAutomation has been installed on the default location, Program Files of the C drive. Feel free to change them according to your installation.


The limitations that a compiled Process has compared to a WinAutomation Process are the following:

1. Triggers and schedules are a function that WinAutomation offers, and they only run from within the WinAutomation Services; therefore, WinAutomation must be installed in order to make use of these functions. Once a process has been compiled, it is no longer a part of WinAutomation, and therefore cannot be associated with a trigger or a schedule. You could of course use the Windows Task Scheduler to trigger the compiled robot to run.

2. The Secure Screen option, as well as the password protection functionality, is something that is not carried with the executable. These are also options that WinAutomation offers to its Processes.

3. You are not able to use the Automation browser in a compiled Process, unless WinAutomation has been previously installed, at some point, on the target machine. Refer to the "Using WinAutomation > Web Automation > Actual Internet Explorer VS Automated Browser" chapter of the WinAutomation Help File for more information.

Other than the above, all other functionalities and Actions will work normally, and you will be able to configure your executable in the Compile Process window (Generate Exe).

More details on the Compiler window can be found in the "Using WinAutomation > Generate EXE > Compiler Window" chapter of the Help File.