Failed to assume control of Chrome (Communication with browser failed. Try reloading extension).

(4) Share

Report

Posted on by waynewalls

Hi there --

My Environment:

Power Automate Desktop (PAD): 2.27.00186.22340

PAD Chrome Extension: 2.27.0.2

Chrome: 108.0.5359.125

Windows: Windows 11 Pro

After installing updates to Windows (KB5021234, KB5021090, KB5021954, and KB5021955) on 13 Dec 2022, my flows that use the Launch Chrome action started failing with the error, [Failed to assume control of Chrome (Communication with browser failed. Try reloading extension)]. And, not surprising, the same error is thrown with the Launch Edge action.

If I signin to my PAD account on a Windows 10 machine (with the same environment and similar updates) the Launch Chrome actions run successfully without errors.

I've tried reinstalling PAD and the browser extension (in Chrome and Edge), along with the official suggestions, and those suggestions found in this post without success.

Any other suggestions sure would be appreciated,

-- Wayne

Categories:

Power Automate Desktop

I have the same question (0)

All responses (23)

Answers (1)

1793aib 12 on at

Like (1)

Report

I'm having the same issue now.

Was this reply helpful? Yes No
waynewalls 74 on at

Like (2)

Report

Just an update...
Since my original post I tried using Firefox. Using Firefox caused PAD to throw the exact same error.

What could have happened that would prevent PAD from talking to all three browser? Did the previously mentioned Windows update change some policy (unbeknownst to me)?

@1793aib Glad to know it's not just me. Did your issues begin after a Windows Update?

Was this reply helpful? Yes No
1793aib 12 on at

Like (1)

Report

Quite possibly. Seems like a complete f'up on Microsoft's behalf here.

I've logged tickets with them, but I'm guessing this is now a global issue for most users who have updated their Windows and software.

Was this reply helpful? Yes No
andersjensenorg 28 on at

Like (0)

Report

Unfortunately, it's happening to many of us who are still running 2.26 and not allowed to update yet. I found a workaround:

1. Open the browser you want to automate
2. Deactivate the browser extension
3. Activate the browser extension
4. Refresh in the browser
5. You need to keep this browser window open to run the flows (yeah it sucks, but it works)

Have a great day, Anders

Was this reply helpful? Yes No
waynewalls 74 on at

Like (2)

Report

Hi @andersjensenorg

I'm glad you found a workaround for those who can't update from 2.26 to 2.27. But...I am running 2.27 and v2.27.0.2 or the browser extension.

Both launching a new instance (whether the browser is already open or not) or attaching to an existing instance fail for Chrome, Edge and Firefox.

I will be delighted if there is a similar workaround to yours for my situation. I am remaining hopeful.

-- Wayne

Was this reply helpful? Yes No
andersjensenorg 28 on at

Like (0)

Report

Have you tried to re-activate the extension in a browser and keep this window open while you click Run from PAD. Yeah, then you'll have two windows open and you can't do unattended, but as a workaround it might be ok.

Was this reply helpful? Yes No
waynewalls 74 on at

Like (0)

Report

@andersjensenorg

I have tried every combination of re-installing, disabling/re-enabling the extension, browser restarted (or not), browser window open (or not) that I can think of.

Another aspect of this is that PAD no longer detects that the extension is installed and enabled. For example, if you try and set up an action to extract data from a webpage, PAD offers to install the extension even though the extension is installed and enabled. This happens with Chrome, Edge, and Firefox. And it happens repeatedly.

I've also checked to ensure that the extension continues to have all the permissions it said it required during installation.

Any other suggestions will be appreciated.

-- Wayne

Was this reply helpful? Yes No
1793aib 12 on at

Like (1)

Report

I've raised a ticket with Microsoft to get this fixed. I don't do work around, it needs to be fixed - I'll check back in when I've got an update.

Was this reply helpful? Yes No
waynewalls 74 on at

Like (0)

Report

@1793aib I really appreciate your being willing to check back in once you have an update. I am using the version of PAD that comes with Office 365 for which there is no administrator and thus no ability to submit a support ticket--at least that I am aware of.

I normally don't "workaround" either but this has been disruptive enough that I would consider a temporary one. My experience with Microsoft Support--with something like this--is that they will get around to it but not in a timely manner.

Was this reply helpful? Yes No
abhishek_0144 4 on at

Like (1)

Report

Not sure if MS did something, but I did something and the error is gone and I am able to run my PAD flows without any workarounds... Here is what ID did....

- Visited the extensions page, through Tools -> Extensions - > Edge
- Removed the extension
- Logged out and then logged in using the "sign in" option on the top left
- Installed the extension using the "Get" button.
- restarted Power automate desktop..

and whooosh !!! it started working.

Let me know if this works for someone.

Was this reply helpful? Yes No