topic Chrome 140.0.7339.81 and process hanging in Product Forum

Chrome 140.0.7339.81 and process hanging

l.kiciak — Mon, 08 Sep 2025 16:34:15 GMT

Hi,

did any of you guys notice issues while automating processes in Chrome version 140.0.7339.81?
The latest version was released at the beginning of September and till then we are struggling with unexpected issues.

Processes are freezing on various stages e.g. writing or click a field. We disabled all popup like autofill or translation prompt, as a blocking factor, but they still hanging.

We noticed when a process is a warning state already, and we open VM, then suddenly it works again. And yes, we are sure that the screen does not lock etc.

Thanks!
L

MOD EDIT: We've locked this thread and moved the discussion to this post. If you're impacted, please come and join us there for the latest information.

Re: Chrome 140.0.7339.81 and process hanging

RoopkiranBevara — Mon, 08 Sep 2025 11:07:00 GMT

Hi @l.kiciak

we're facing the same issues. A lot of our UIA elements, browser mode elements are failing to identify while running, but are identifiable through the app modeler.

Best guess there was an Edge & chrome update late last week. It seems the issue is with updating of browser. Lets wait for the solution from community.

Re: Chrome 140.0.7339.81 and process hanging

zdenek.kabatek — Mon, 08 Sep 2025 12:07:46 GMT

Hi, I can confirm the same for several of our clients using UIA elements or download dialog window in MS Edge. The temporary resolution was to downgrade it to version 139.x which works well.

Regards

Zdenek

Re: Chrome 140.0.7339.81 and process hanging

l.kiciak — Mon, 08 Sep 2025 12:14:48 GMT

Hi Zdenek,

thanks for the hint!
Unfortunately, downgrade is not an option in our case. Would be nice to know, what is causing the issue.

Best,
L

Re: Chrome 140.0.7339.81 and process hanging

l.kiciak — Mon, 08 Sep 2025 12:19:45 GMT

found on another topic: [Blue Prism UI Automation Failing] - SS&C Blue Prism Community

https://support.blueprism.com/en/support/solutions/articles/7000095180-why-do-i-have-browser-automation-issues-after-updating-to-chrome-version-140-