- 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
- ST-USG-032 - Required Tags
- ST-USG-034 - Automation Hub URL
- 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
- Automating applications running under a different Windows user
- Automating applications running in AppContainer mode
- Automating applications running as administrator
- Validation of large Windows-legacy projects takes longer than expected
Repairing Active Accessibility support
This page describes how to diagnose and repair issues caused by broken Active Accessibility support.
The Active Accessibility support can be broken after:
- Installing certain Windows updates
- Uninstalling/upgrading certain applications such as Adobe Acrobat Reader or Microsoft Office
Observed behavior
Selectors are not generated for applications relying on the IAccessible
registry entries, such as File Explorer, Internet Explorer or Microsoft Office.
For example, when using UI Explorer to indicate UI elements in Windows File Explorer, instead of individual elements, the entire area is selected.
Cause
Following a Windows update, IAccessible
registry entries were overwritten and became corrupted.
The accessibility support provided through registry configuration can also get broken when some applications (such as Adobe
Acrobat Reader) register custom implementations for IAccessible
, but don’t restore default settings on uninstall/upgrade.
Solution
Upgrading to UiPath.UIAutomation.Activities 23.4
Starting with UiPath.UIAutomation.Activities version 23.4, this issue has been permanently fixed.
The misconfiguration of these Windows Registry keys no longer interferes with automating applications using Active Accesibility.
Repairing the IAccessible registry entries
If you can't upgrade your UiPath.UIAutomation.Activities package to version 23.4 or higher, you can solve this issue by manually repairing the Windows Registry keys.
In order to check if IAccessible
registry entries became corrupted, you need to open the Windows Registry Editor and verify whether the following keys are
missing or have other values, and add/modify them if necessary.
Below are the values that should be present in the registry.
HKEY_CLASSES_ROOT\Interface\{618736E0-3C3D-11CF-810C-00AA00389B71}
Windows Registry Editor Version 5.00
[HKEY_CLASSES_ROOT\Interface\{618736E0-3C3D-11CF-810C-00AA00389B71}]
@="IAccessible"
[HKEY_CLASSES_ROOT\Interface\{618736E0-3C3D-11CF-810C-00AA00389B71}\ProxyStubClsid32]
@="{00020424-0000-0000-C000-000000000046}"
[HKEY_CLASSES_ROOT\Interface\{618736E0-3C3D-11CF-810C-00AA00389B71}\TypeLib]
@="{1EA4DBF0-3C3B-11CF-810C-00AA00389B71}"
"Version"="1.1"
Windows Registry Editor Version 5.00
[HKEY_CLASSES_ROOT\Interface\{618736E0-3C3D-11CF-810C-00AA00389B71}]
@="IAccessible"
[HKEY_CLASSES_ROOT\Interface\{618736E0-3C3D-11CF-810C-00AA00389B71}\ProxyStubClsid32]
@="{00020424-0000-0000-C000-000000000046}"
[HKEY_CLASSES_ROOT\Interface\{618736E0-3C3D-11CF-810C-00AA00389B71}\TypeLib]
@="{1EA4DBF0-3C3B-11CF-810C-00AA00389B71}"
"Version"="1.1"
HKEY_CLASSES_ROOT\WOW6432Node\Interface\{618736E0-3C3D-11CF-810C-00AA00389B71}
Windows Registry Editor Version 5.00
[HKEY_CLASSES_ROOT\Wow6432Node\Interface\{618736E0-3C3D-11CF-810C-00AA00389B71}]
@="IAccessible"
[HKEY_CLASSES_ROOT\Wow6432Node\Interface\{618736E0-3C3D-11CF-810C-00AA00389B71}\ProxyStubClsid32]
@="{00020424-0000-0000-C000-000000000046}"
[HKEY_CLASSES_ROOT\Wow6432Node\Interface\{618736E0-3C3D-11CF-810C-00AA00389B71}\TypeLib]
@="{1EA4DBF0-3C3B-11CF-810C-00AA00389B71}"
"Version"="1.1"
Windows Registry Editor Version 5.00
[HKEY_CLASSES_ROOT\Wow6432Node\Interface\{618736E0-3C3D-11CF-810C-00AA00389B71}]
@="IAccessible"
[HKEY_CLASSES_ROOT\Wow6432Node\Interface\{618736E0-3C3D-11CF-810C-00AA00389B71}\ProxyStubClsid32]
@="{00020424-0000-0000-C000-000000000046}"
[HKEY_CLASSES_ROOT\Wow6432Node\Interface\{618736E0-3C3D-11CF-810C-00AA00389B71}\TypeLib]
@="{1EA4DBF0-3C3B-11CF-810C-00AA00389B71}"
"Version"="1.1"
The above content can be written in .reg
files. After a backup of the existing registry entries, you can run the .reg
files to repair these entries automatically.