Help
April 2, 2026

Chrome 147 Removes UIA Workaround: Update Your Blue Prism Application Models

Action is required to ensure your Blue Prism automations continue running smoothly in Chrome-based browsers, as Google's update to Windows UI Automation (UIA) will render temporary workarounds obsolete with the release of Chrome 147 on April 7th, 2026.

Chrome 147 Removes UIA Workaround: Update Your Blue Prism Application Models

robert.nicklin
Staff
Staff
‎02-04-26 04:07 PM

Hello, I'm sharing this update today to make sure you're prepared for an important change that might affect your automations. As outlined in Google's publicly available documentation and our own documentation, Chrome-based browsers are updating their support for Windows UI Automation (UIA). This is a change Google has signalled for some time, and it now requires you to take a few steps to keep your Blue Prism processes running smoothly. In this blog, I'll break down what's changing, what you need to do, and where to find extra help and resources. Our goal is to make this transition as easy as possible for you.

What is happening and why it matters

Google changed how Windows UI Automation (UIA) works in Chrome-based browsers, starting with Chrome 138 - replacing a legacy emulation layer with a new native UIA provider. This means Blue Prism processes that use UIA automation to interact with Google Chrome are affected. Elements that were spied against the old architecture may fail to be located or behave unexpectedly when the new UIA provider is enabled.

There was a temporary enterprise policy (UiAutomationProviderEnabled) provided which allowed organisations to revert to legacy behaviour while they updated their processes.

This policy is permanently removed in Chrome 147, which is due to be released 7th April 2026, with deployment into your own environments dependent on your local organisational policy. Once Chrome 147 is deployed, the policy based workaround will no longer function and processes relying on it may cease to function if action is not taken.

What you need to do

  • Re-spy UIA elements in any Blue Prism application models that automate Chrome browsers, using Chrome 138 or later with the new UIA provider enabled.
  • If your organisation is using the UiAutomationProviderEnabled enterprise policy as a temporary fix, remove it once your models have been updated.
  • Additional workarounds may be available for this issue in your environment - for more information, please refer to the relevant Knowledge Base Article on subject.

Where to get help and further information

Our commitment to keeping you informed

The Blue Prism Product team is actively monitoring the impact of the Chrome 147 release and working closely with Customer Support to support affected customers. We will provide updates through the Support Portal, the Blue Prism Community, and directly to customers via their Customer Success Manager as the situation develops. If you have concerns or need guidance specific to your environment, please don't hesitate to reach out - we're here to help you through this transition.

Labels:
Popular Articles