Unanswered

Failed to assume control of [Chrome/Edge/Firefox] (Communication with browser failed. Try reloading extension)

(0) Share

Report

Posted on by andrewisaac

Hello!

We have been trying to create a flow which launches outlook, finds emails, downloads a pdf from those emails, scrapes to find a link, and then tries to open that link in browser.

The flow is successfully able to find the link and open that link in browser, but crashes immediately afterword, stating that communication with the browser was unsuccessful. This issue persisted in all three browser types: Microsoft Edge, Google Chrome, & Firefox.

We have already tried many of the suggestion found in the other forums such as:

- closing Google Chrome Crash/Installer handler

- Go to Chrome's preferences document at C:>Users>(your_user_account)>AppData>Local>Google>Chrome>User Data>Default>Preferences and set the exit_type to “normal

- "ComSpec" "Environment Variable" set to C:\\WINDOWS\system32\cmd.exe

- updating/removing+readding extensions AND power automate

- running as admin

- doing all the configurations here:Install Power Automate browser extensions - Power Automate | Microsoft Learn

Not sure what to do now, any suggestions?

Categories:

Power Automate Desktop

All responses (4)

Answers (0)

Sort by

tjones0213 41 on at

Like
a
(0)

Report
Copy link

Link copied!

See the other forum posts on this subject. My issue was my flows started failing to detect the browser had opened only after I had updated Win11.

I'm using Edge and found that I needed to upgrade Power Automate Desktop and verify the latest Edge extension.
This still failed. I had a workaround I used but today I followed advise in another post that had me turn off background processing in Edge and turn on developer mode in the PAD extension and now my flow is working normally again.

Here's the link to the post I referenced: https://powerusers.microsoft.com/t5/Power-Automate-Desktop/Browser-extension-doesn-t-work-after-Win11-lates-Update-on-18th/td-p/1933316/jump-to/first-unread-message
andrewisaac 29 on at

Like
a
(0)

Report
Copy link

Link copied!

Hello! Thank you so much for your links!

However, I have already tried those methods, and the flows are still not working. I am not sure what the issue is.
waynewalls 74 on at

Like
a
(0)

Report
Copy link

Link copied!

I have also tried disabling Edge background processes and ensuring the developer mode is enabled--it has not worked for me.

As with you, my flows using web automation (with Chrome, Edge, or Firefox) stopped working after an update to Windows 11 sometime around 13 Dec 2022. My flows with web automation DO run successfully on a Windows 10 machine (with all the updates that were available on 13 Dec 2022). So it does seem to be some interaction between Power Automate Desktop and Windows 11--at least in my case.

In the last week there have been 7 separate posts describing web automation failures with Power Automate Desktop after updating. Those seven posts have garnered over 1000 views in a week. None of the seven posts have uncovered a solution that works in my case--except reverting the update to Windows.
roccolord 63 on at

Like
a
(0)

Report
Copy link

Link copied!

This solved the issue for me with latest win11 update , PAD 2.27 and latest extension.

Remove windows store version of PAD, then install with MSI installer afterwards. Link with info below.

Try installing using MSI Installer
https://learn.microsoft.com/en-us/power-automate/desktop-flows/install
https://www.reddit.com/r/MicrosoftFlow/comments/zqskyy/comment/j181q0c/