- Release Notes
- Getting Started
- Setup and Configuration
- Automation Projects
- Dependencies
- Types of Workflows
- File Comparison
- Automation Best Practices
- Source Control Integration
- Debugging
- The Diagnostic Tool
- Workflow Analyzer
- About Workflow Analyzer
- ST-NMG-001 - Variables Naming Convention
- ST-NMG-002 - Arguments Naming Convention
- ST-NMG-004 - Display Name Duplication
- ST-NMG-005 - Variable Overrides Variable
- ST-NMG-006 - Variable Overrides Argument
- ST-NMG-008 - Variable Length Exceeded
- ST-NMG-009 - Prefix Datatable Variables
- ST-NMG-011 - Prefix Datatable Arguments
- ST-NMG-012 - Argument Default Values
- ST-NMG-016 - Argument Length Exceeded
- ST-DBP-002 - High Arguments Count
- ST-DBP-003 - Empty Catch Block
- ST-DBP-007 - Multiple Flowchart Layers
- ST-DBP-020 - Undefined Output Properties
- ST-DBP-023 - Empty Workflow
- ST-DBP-024 - Persistence Activity Check
- ST-DBP-025 - Variables Serialization Prerequisite
- ST-DBP-026 - Delay Activity Usage
- ST-DBP-027 - Persistence Best Practice
- ST-DBP-028 - Arguments Serialization Prerequisite
- ST-USG-005 - Hardcoded Activity Arguments
- ST-USG-009 - Unused Variables
- ST-USG-010 - Unused Dependencies
- ST-USG-014 - Package Restrictions
- ST-USG-020 - Minimum Log Messages
- ST-USG-024 - Unused Saved for Later
- ST-USG-025 - Saved Value Misuse
- ST-USG-026 - Activity Restrictions
- ST-USG-027 - Required Packages
- ST-USG-028 - Restrict Invoke File Templates
- Variables
- Arguments
- Imported Namespaces
- Recording
- UI Elements
- Control Flow
- Selectors
- Object Repository
- Data Scraping
- Image and Text Automation
- Citrix Technologies Automation
- RDP Automation
- Salesforce Automation
- SAP Automation
- VMware Horizon Automation
- Logging
- The ScreenScrapeJavaSupport Tool
- The WebDriver Protocol
- Test Suite - Studio
- Extensions
- Troubleshooting
- About troubleshooting
- Microsoft App-V support and limitations
- Internet Explorer X64 troubleshooting
- Microsoft Office issues
- Identifying UI elements in PDF with Accessibility options
- Repairing Active Accessibility support
- JxBrowser applications troubleshooting
- User Events Monitoring
- Citrix Troubleshooting
- Automating Applications Running Under a Different Windows User
Microsoft App-V support and limitations
Microsoft Application Virtualization (App-V) is a solution that delivers applications inside a virtual container, without the need to perform a traditional installation.
App-V applications are virtualized applications that run in a local, self-contained virtual environment.
They can be automated using the UiPath products, but, as they run isolated from each other and from other native applications, in some scenarios, installing the UiPath Extensions for the underlying technology requires a few extra steps, as described below.
In classic deployments, Chrome, Edge and Firefox extensions can be installed successfully for App-V browsers.
If the appropriate browser extension is not installed correctly, the registers configured during extension install might be virtualized in the App-V browser. To correctly modify the registers used by the App-V, the SetupExtensions tool needs to be run inside the virtualized environment, as described here.
For example, to install the Chrome extension, one can perform the following steps:
- Start a Command Prompt in the virtual environment using the command:
cmd.exe /appvpid:<pid>, where<pid>is the process id of the App-V browser
- Run the SetupExtensions tool to install the Chrome extension:
SetupExtensions.exe /chrome
Java applications virtualized through App-V that don’t contain the Java Runtime Environment inside the App-V bubble can be automated as if they weren't virtualized.
App-V Java applications that contain the JRE inside the App-V bubble and need the UiPath Extension for Java installed have to be re-sequenced to include the extension inside the App-V. Details on how to install the Java Extension can be found here.
By default, App-V applications write their registry key values to their virtual registry, except for Pass-through registers (like the Policies registry keys) configured by the App-V administrator.
This implies that every browser extension configuration performed from the virtualized Studio will not be visible to the virtualized browser.
To overcome this issue, the required browser extension can be installed using a native, non-virtualized SetupExtensions tool.
If the appropriate browser extension is not installed correctly, the registers configured during extension install might be virtualized in the App-V browser. To correctly modify the registers used by the App-V, the non-virtualized SetupExtensions tool needs to be run inside the virtualized environment, as described here.
For example, to install the Chrome extension one can perform the following steps:
- Start a Command prompt in the virtual environment using the command:
cmd.exe /appvpid:<pid>, where<pid>is the process id of the App-V browser
-
Run the SetupExtensions tool to install the Chrome extension:
SetupExtensions.exe /chrome
Java applications virtualized through App-V that don’t contain the Java Runtime Environment inside the App-V bubble can be automated as if they weren't virtualized.
App-V Java applications that contain the JRE inside the App-V bubble and need the Extension for Java installed, will have to be re-sequenced to include the extension inside the App-V. Details on how to install the Java Extension can be found here.
By default, App-V applications write their registry key values to their virtual registry, except for Pass-through registers (like the Policies registry keys) configured by the App-V administrator.
This implies that every browser extension configuration performed from the virtualized Studio is not visible to the native browser.
To overcome this issue, the required browser extension can be installed using a native, non-virtualized SetupExtensions tool.
