Power Platform Community Forum Thread Details

Hello,

I'm encountering an issue with my Power Automate flow when trying to launch Chrome browser in an Azure VM. The error message I receive is:

"Problem while executing action 'LaunchChrome'. Failed to assume control of Chrome (communication with Power Automate web extension failed)."

I have already added and activated the Power Automate extension in Chrome. When I check the troubleshooting report in Power Automate Desktop, I see the following:

Troubleshooting error:

Troubleshooting report:

"Found Chrome - x64 installation,Web Automation,Success.
Chrome has no user-level Native Messaging hosts configuration.,Web Automation,Success.
Chrome native message host path is valid in 'HKEY_LOCAL_MACHINE\SOFTWARE\Google\Chrome\NativeMessagingHosts\com.microsoft.pad.messagehost',Web Automation,Success.
Chrome browser extension is allowed,Web Automation,Success
Chrome native message host is allowed,Web Automation,Success.
Microsoft Power Automate web extension is disabled in Chrome for profile 'Person 1'.,Web Automation,Warning.
"All 'Preferences' files for Chrome, have displayed issues for the Power Automate web extension.",Web Automation,Failure."

The diagnostic report indicates that the same issue appears for both Chrome and Edge browsers. However, the failure occurs only when launching the Chrome browser.

Has anyone encountered a similar problem? Can anyone provide guidance on how to resolve this issue? Your assistance would be greatly appreciated.

Categories:

Power Automate Desktop

Yes, this happens when the extension does not load in time. Also, in some versions this happens when you have the "wait for web page to load" toggle enabled in the Launch new Chrome action. You can try to disable that and then instead have a separate action to Wait for web page content in order to make sure your page has loaded.

If this doesn't solve the issue, I recommend using a different approach for launching browsers - using the Run application action to launch it, and then Launch new Chrome to attach to it. See a sample of that in my PADFramework I published on GitHub here:

https://github.com/AgniusBartninkas/power-automate-desktop-framework/tree/main/src/flows/browser-launcher

You don't need to use the full solution. You can copy the code from the BrowserLauncher utility flow and paste it into your own flow to create the actions.