Broken selectors after Chrome/Edge update to version 114.0.1823.37

Unfortunately that’s not the way how fixes are provided. there won’t be a new 20.10.9 version, but the fix is included in the v20.10.13 package.

As 20.10.9 and 20.10.13 has a different UiPath package dependency. So to make remote runtime work with 20.10.13 UiAutomation package you have to update the Remote Runtime installation on the remote server by copying the necessary dependencies. Check this description:



thanks for your response , well that will take a long time to update the remote runtime in server, but we have enterprise license, if we approach the UiPath support team , will they provide this update in 20.10.9 version for us


I have checked 22.10.7 and 23.4.7 dependency for UiAutomation package. I checked webpage for print option with UiExplorer and selector is not visible for Print/Save button. I described the problem in post: Active Accessibility stopped working after Chrome update

there is the webpage where I can’t see available selectors.

My Chrome version: 114.0.5735.110

I can not reverse Chrome version.

Hi UiPath Team,

Can’t find a 20.10.14 in my official feed :frowning:

Is that only on my side? Would you please help with it?

Looking forward to hearing from you,

Thanks in advance & Best regards,


Sorry. My mistake. Version 22.10.7 is working. After changing method to AA in UiExplorer selector is visible in Studio (I can pick it) but then Validation for selector has error:

When I start robot in Studio it sees selector and robot is clicking “Print” button. Validation error appear also with classic click. There is no validation error with Modern Design Click.

I didn’t test it in unattended mode from Orchestrator.

@liviu.leordeanu Do you have any information on this? We couldn’t find the version 20.10.14 in the official feed.

This is not solution, but I can confirm that I have this version available:

I checked that in Windows-Legacy project (the same as in your screen)

Hi @Amrita.Hegde ,

Indeed, for old projects using the feed, UiPath.UIAutomation.Activities version 20.10.14 didn’t appear. It was available only on the new official feed:
Now it is published in the myget feed as well. Please try again.


Hi @Yameso ,

There seems to be a problem when trying to indicate an element from Selection Window or from UI Explorer, only for the first time. But if you click once in that window and then indicate again the button, it will find it and show it as valid.
I’ve tested this workaround both with modern and classic Click activities and it works.
The problem only occurs for design time. At runtime, if you already have the good selector saved in the activity, the target will be found.
Can you please try if it works for you?


Hi @Nestor_Levytskyy ,

UiPath.UIAutomation.Activities version 20.10.14 is now also available in the myget feed. You should be able to find it. Can you please check?

Thank you,

1 Like

Hi @Luiza_Surdu-Bob,

Thanks for your help, I do confirm it’s present now in the feed :slight_smile:

Best regards,

I think its working fine, the only thing I need to do is to change UiFramework to AA because it’s not accessible other way and UiExplorer can not detect it automatically. This is not issue for me :wink: Shortkey F4 is easy enough :slight_smile:

we have installed latest version of UiPath extension and UiPath Assistant in prod server and also tried with above mentioned steps like updating UiPath.UiAutomation.Activity package to latest 23.4.7 but still facing same error that ui element not found after upgradation chrome version to 114. . And same workflow is running fine in other server.

Please help to resolve this.

Hi @bhagyashri.kasture ,

If the same workflow is running fine in other machine with Chrome v114, it could be a different issue than the one related to the Chrome/Edge update.

Does the UI Element not found error occur for selectors using <ctrl /> tags (i.e using Active Accessibility - AA)? Only that type of selectors would be affected by the Chrome/Edge update.

For first troubleshooting steps, I recommend the following:

  1. As you don’t have UiPath Studio installed on that machine, but only the UiPath Assistant, try to re-install the extension with the SetupExtensions.exe tool (see
  2. Check the troubleshooting steps described in this page:

Best regards,


I just got back from holiday to discover this issue. The workflows developed all access MS D365 and Active Accessibility provides (for this app and most others) far better selectors than Default method.

The first thing I tried was to amend the Chrome Accessibility Internals settings (chrome://accessibility/), setting ‘Web accessibility’ to checked. This also appeared to set Screen Reader Support and HTML to checked.


For me, so far at least, this has re-enabled the use of the AA Ui method.

My client is using Studio version 2022.10.5, with UiPath.UiAutomation.Activities package version 22.10.3.

UPDATE: 17/07/2023 The Accessibility Internals settings do not appear to hold and are re-set when Chrome is restarted. Client is investigating whether settings will hold if set via AD GPO…

UPDATE: 18/07/2023 GPO applied but Chrome still not keeping settings changes. Client has reverted Chrome back to previous working version - Version 113.0.5672.127 (Official Build) (64-bit) - as interim measure to avoid cost of upgrading activity packages (+testing and re-deployment) and (worse case) updating Studio if that’s also required.


I can only see UiPath.Automation.Activities package up to 22.10.7 then jumps to 23.3.4.

Can you advise please whether there I need to have upgraded any of the other activity packages - UiPath.System, for example, before 22.10.14 can be seen?

The myget URL I’m using is

The version of Studio my client is using is 2022.10.5.

Many thanks

Thanks for this information!
I have updated the package UiPath.UiAutomation.Activities to 22.4.9 and installed all dependencies and it fixed the issue. Thank you very much!

1 Like