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

[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

[1793aib]

I'm having the same issue now.

[waynewalls]

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?

[1793aib]

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.

[andersjensenorg]

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

[waynewalls]

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

[andersjensenorg]

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. 

[waynewalls]

@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

[1793aib]

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.

[waynewalls]

@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.

[abhishek_0144]

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.

[waynewalls]

@abhishek_0144 , Thanks.

That did not work for me in Chrome, Edge or Firefox.  They all still fail and do not detect the presence of the extension--or at least want to install it when it is already present and enabled.

[Zulqarnain97]

While we update to the new version flows are behaving very bad.
We have report download flow it. flow run fine but we are calling another flow in this flow, which is upload file flow to upload file in sharepoint through chrome is failing. But if we run the upload file flow directly it run fine.
So, I change the upload file flow and set all activities to Edge. Then I run report download flow and when it goes to upload file flow its open chrome but as I said before, I set changes with Edge its open chrome.

[eugene-d]

The recent Windows Updates have produced exactly the same issues for me.   

Firstly it knocked out my WiFi adapter, then once I'd recovered that (a 2 day job), I noticed that PAD gives the 'Communication with browser failed.  Tried reloading extension' error when used with Edge and Firefox.

Tried all the recovery methods suggested in this forum but the PAD problems persist.

No suggestions I'm afraid, just hoping for a solution from Microsoft ASAP.

[Chadillac]

@waynewalls any luck for you? Same thing here. I've spent hours and hours creating flows that I had just gotten dialed in, then sometime around the 2nd week of December the browser connection stopped working:

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

I'm on 2.27 of PAD and the Chrome extension (also 2.27).

I've tried uninstalling and disabling the extension. I've tried using Edge. Nothing works. I don't understand how a big company like Microsoft lets this happen and can go weeks without a fix!

[waynewalls]

@Chadillac 

I have not tried it yet but the following two posts suggest that uninstalling the Microsoft Store version of PAD and then using the MSI installer has solved the problem for some users.

https://powerusers.microsoft.com/t5/Power-Automate-Desktop/ERROR-Launch-New-Microsoft-Edge/m-p/19397...

https://powerusers.microsoft.com/t5/General-Power-Automate/Unable-to-take-browser-control-after-remo...

In the second post @Zygmunt suggests a specific sequence that worked in their instance.

[Chadillac]

@waynewalls thanks. Tried those...no luck 😞

[Chadillac]

@waynewalls the reinstall worked after I restarted my pc after the uninstall. The first time, I didn't restart and it didn't work. 

[ryule]

My 2.27 is acting up as well with the new extension. It works sometimes, and sometimes it doesn't. No rhyme or reason....

[lyjxuzhou]

It happened to me today,here is what i do,and it works

1.uninstall "power automate"extension 

2.install the respective web extension from the Power Automate for desktop designer.

offical instrution-issue for cause 1:https://learn.microsoft.com/en-us/troubleshoot/power-platform/power-automate/failed-to-assume-contro...