activities
latest
false
UiPath logo, featuring letters U and I in white

UI Automation Activities

Last updated Nov 11, 2025

About the UI Automation activity package

The UI Automation activity package contains all the basic activities used for creating automation projects.

These activities enable the robots to:

  • Simulate human interaction, such as performing mouse and keyboard commands or typing and extracting text, for basic UI automation.
  • Use technologies such as OCR or image recognition to perform Image and text automation.
  • Create triggers based on UI behavior, thus enabling the robot to execute certain actions when specific events occur on a machine.
  • Perform browser interaction and window manipulation.

To create automations, choose one of the following experiences:

  • Low-code—Use low-code automations paired with Classic, Modern, and Computer Vision activities. Low-code automations use a visual interface with drag-and-drop activities from activity packages, making it accesible for a broad user base.
  • Coded—Use coded automations, paired with UI Automation APIs. Coded automations, which utilize UiPath services (equivalent to activity packages) and their corresponding APIs (equivalent to activities), allow you to create automations using code. Moreover, coded automations can use .NET NuGet packages, and custom C# classes that you build within UiPath Studio. The UI Automation activity package supports APIs starting with v23.10.3.
Important: Automation processes that use UI Automation activities cannot run under a locked screen.
Note:
  • Starting with v20.10.5, the UI Automation Next package has been deprecated and the existing UI Automation package has been expanded to include all the modern features previously available in UI Automation Next. You are also able to install the unified UI Automation activity package even on Studio versions 2020.4.1 and lower. This displays all the classic and modern activities in the activities pane. Read more about the Modern Design Experience.
  • Starting with UiPath.UIAutomation.Activities v19.11, all Abbyy related activities have been moved to a separate package. Install the UiPath.Abbyy.Activities package if you want to use its activities for OCR, Cloud OCR, classification, and data extraction.
  • As of v18.3.6877.28298, the UiPath.Core.Activities package was split into the UI Automation and System packages. Find out more about the Core Activities Split.

Dependencies

The UI Automation activity package contains the following internally-developed dependencies:

  • UiPath.Vision - enables the functionality of OCR and Computer Vision engines.
  • UiPath - an essential library for UI Automation activities.

The UiPath.Vision dependency package includes third-party libraries. These external dependencies are used exclusively for the purpose of enabling the implementation of specific activities in the UiPath.UIAutomation.Activities package. Here are some examples:

  • AbbyyOnlineSdk.dll - used exclusively in the Abbyy Cloud OCR activity, at run-time, as a wrapper over the Abbyy online service calls.
  • Interop.FREngine.v11.dll - used exclusively in the Abbyy OCR activity, at run-time, as a wrapper over the Abbyy FineReader Engine calls.
  • Interop.MODI.dll - used exclusively in the Microsoft OCR activity, at run-time, when executed on a Windows 7 or Windows Server machine.

Particular scenarios might require management of strict UI Automation dependencies versions. For example, a language for the Tesseract OCR engine must be manually installed per UiPath.Vision version. This means that for processes using that language you need to use the corresponding UI Automation activity package. You can find out more on this page.

The table below enlists the dependencies shipped with each version of the package:

UiPath.UIAutomation.Activities

UiPath.Vision

UiPath

25.10.193.16.025.10.155.37129
25.10.163.15.025.8.152.27793
25.10.133.15.025.6.146.54041
25.10.123.15.025.6.142.41639
25.10.103.15.025.6.142.41639
25.10.83.15.025.6.140.65296
25.10.73.15.025.6.139.35746
25.10.63.15.025.4.134.4749
25.10.43.15.025.4.134.4749
25.10.33.15.025.4.134.4749

25.10.2

3.15.0

25.4.134.4749
24.10.143.14.224.10.143.28596
24.10.133.14.224.10.128.59771

24.10.12

3.14.2

24.10.128.59771

24.10.11

3.14.2

24.10.120.29399

24.10.103.14.224.10.113.9929
24.10.83.14.224.10.112.56016
24.10.73.14.224.10.108.16096
24.10.63.14.224.10.106.53365
24.10.53.14.224.10.106.53365
24.10.33.13.324.10.94.62718
24.10.23.13.224.10.94.62718
24.10.13.13.224.10.93.21985
24.10.03.13.224.10.93.21985
23.10.183.11.223.10.152.29655
23.10.173.11.223.10.136.23377

23.10.16

3.11.2

23.10.128.59555

23.10.15

3.11.2

23.10.120.29846

23.10.133.11.223.10.97.53968
23.10.123.11.123.10.90.55899
23.10.113.11.123.10.81.50671
23.10.93.11.123.10.71.64399
23.10.83.11.123.10.71.64399
23.10.73.11.123.10.71.64399
23.10.63.11.123.10.71.64399
23.10.33.11.123.10.69.1489
23.4.113.10.123.4.81.50665
23.4.103.10.123.4.67.58671
23.4.93.10.1

23.4.67.58671

23.4.83.10.123.4.62.63011
23.4.73.10.1

23.4.60.24910

23.4.63.10.123.4.59.15687
23.4.53.10.123.4.57.3408
23.4.43.10.123.4.57.3408
22.10.113.6.022.10.136.43035
22.10.103.6.022.10.67.59238
22.10.93.6.022.10.67.59238
22.10.83.6.022.10.60.25726
22.10.73.6.0

22.10.60.25726

22.10.63.6.022.10.59.14500
22.10.53.6.022.10.52.8892
22.10.43.6.022.10.49.23
22.10.33.6.022.10.46.47635
22.10.23.6.022.10.46.47635
22.4.123.3.222.4.67.58669
22.4.113.3.022.4.67.58669
22.4.103.3.022.4.62.58438
22.4.93.3.022.4.60.25939
22.4.83.3.022.4.52.11405
22.4.73.3.022.4.42.61951
22.4.63.3.022.4.38.42025
22.4.53.3.022.4.38.42025
22.4.43.3.022.4.38.42025
21.10.103.1.421.10.67.58666
21.10.93.1.421.10.60.24919
21.10.83.1.421.10.49.13436
21.10.73.1.421.10.42.64905
21.10.63.1.421.10.40.21933
21.10.53.1.421.10.34.30369
21.10.43.1.421.10.32.57908
21.10.33.1.421.10.30.58966
21.4.43.0.121.4.25.3292
21.4.33.0.121.4.23.31065
20.10.152.2.020.10.8676.29744
20.10.142.2.020.10.8558.20688
20.10.132.2.020.10.8363.32849
20.10.122.2.020.10.8242.23238
20.10.112.2.020.10.7992.24819
20.10.102.2.020.10.7810.17763
20.10.92.2.020.10.7641.24102
20.10.82.2.020.10.7641.24102
20.10.72.2.020.10.7641.24102
20.10.62.2.020.10.7585.27318
20.10.52.2.020.10.7585.27318
20.4.32.0.320.4.7537.15740
20.4.22.0.320.4.7472.17184
20.4.12.0.320.4.7422.14731
19.11.52.0.119.10.7601.15369
19.11.42.0.119.10.7601.15369
19.11.32.0.119.10.7452.28108
19.11.22.0.119.10.7312.25504
19.11.12.0.019.10.7312.25504
19.11.02.0.019.10.7275.19994
19.10.11.8.119.10.7243.31457
19.7.01.6.119.7.7128.27029
19.6.01.6.019.6.7108.25473
19.5.01.6.019.5.7079.28746
19.4.21.5.019.4.7068.19937
19.4.11.5.019.4.7054.14370
19.3.01.4.010.0.7004.31775
19.2.01.3.010.0.6957.21531
19.1.01.2.010.0.6957.21531
18.4.81.2.110.0.7772.19184
18.4.71.2.110.0.7445.17204
18.4.61.2.010.0.7194.26789
18.4.51.2.010.0.7020.22745
18.4.41.2.010.0.6992.20526
18.4.31.2.010.0.6929.25268
18.4.21.2.010.0.6913.22031
18.3.6962.289671.1.09.0.6962.24417
18.3.6897.225431.1.09.0.6893.27943
18.3.6877.282981.1.09.0.6877.24355

Core Activities split

Starting with the v2018.3 release, the Core Activities Package is split into two distinct packages, UiPath.System.Activities and UiPath.UIAutomation.Activities. This has been done with the intention of offering you more control over which activity versions you use in the execution of your automation projects. In correlation with the Project Dependencies feature, this split enables you to choose exactly the version of activities you want to use as a dependency for your project.

Whenever a project created with a version of Studio older than v2018.3 is opened with Studio v2018.3 or higher, the project is automatically migrated and the new System and UI Automation packages replace the old Core package.

Remember to properly migrate your processes when updating the 2018.3 UiPath Platform. The dependencies and activities installation algorithm has improved, which can cause conflicts when executing processes with packages installed from local feeds. If you encounter any issues while updating, check out possible solutions on this page. Also, remember to check out how to Open Projects Created with Previous Versions.

Note: Once the migration is performed, you cannot revert the project to use the old Core package.
Starting with Studio v2018.3 or higher, you cannot install the Core package from the Package Manager. However, rest assured that the UiPath.System.Activities and UiPath.UIAutomation.Activities packages contain all the activities that were in the old one. Additionally, from v2018.3 on, you can use any combination of activity packages regardless of what version of Studio you are using at that moment.
Note: Once a project is published with v2018.3 or higher, it can no longer be executed by using a v2018.2 or lower Robot.
Please note that the location of the tessdata folder which is used to install languages for the Google OCR engine has been moved from %ProgramFiles(x86)%\UiPath\Studio essdata to %UserProfile%\.nuget\packages\uipath.vision. You can read more about installing and changing the language for the Google OCR engine on this page.

For more information on how this change impacts Studio, you can read more here.

Core Legacy Activities

The Core Legacy Activities package (the UiPath.Core.Activities meta-package) was created as a result of the Core Activities Split to ensure compatibility between Legacy Processes and Robot versions v2018.3 or newer. The Core Legacy Activities and Legacy Processes are defined as follows:
  • Core Legacy Activities - The UiPath.Core.Activities meta-package is available starting with the v2018.3 release. It references the UiPath.System.Activities and UiPath.UIAutomation.Activities packages whenever a legacy process is executed by a v2018.3 or newer Robot.
  • Legacy Process - A process created with Studio v2018.2 or lower which uses the former UiPath.Core.Activities package as a dependency.

While the Robot is resolving dependencies, it searches for the UI Automation and System packages. If they are not available, it uses the Lowest Applicable Version runtime rule to determine what UI Automation and System package versions to use, which needs to be greater than the default one.

Using a different UI Automation package

If a different version of the UiPath.UIAutomation.Activities package is needed for executing a process, the UiPath.UIAutomation.Activities v18.3.6897.22543 package needs to be removed from the following locations and replaced with the required one:
  • The Orchestrator feed.
  • The default packages location - %Program Files (x86)%\UiPath\Studio\Packages in versions prior to 2021.4 or %Program Files%\UiPath\Studio\Packages starting with version 2021.4.
  • The NuGet cache - %userprofile%\.nuget\packages\uipath.core.activities.
If the Robot machine has access to the Internet, then the Official feed from the nuget.config file must be removed to prevent the Robot from downloading it again.

Read more about Managing Packages.

Resolving legacy processes

If you have processes created with Studio v2018.3.1 which were using the UiPath.UIAutomation.Activities v18.3.6864.20582 package, you must open them in Studio and update the UiPath.UIAutomation.Activities package.
If you ever used Studio v2018.3.1 with legacy processes, the UiPath.UIAutomation.Activities v18.3.6864.20582 package needs to be removed, as explained on this page.
  • Dependencies
  • Core Activities split
  • Core Legacy Activities
  • Using a different UI Automation package
  • Resolving legacy processes

Was this page helpful?

Support and Services
Get The Help You Need
UiPath Academy
Learning RPA - Automation Courses
UiPath Forum
UiPath Community Forum
Uipath Logo
Trust and Security
Terms of Use
Privacy Policy
Cookies Policy
© 2005-2025 UiPath. All rights reserved.