Error ‘Failed to assume control of Microsoft Edge/Chrome/Firefox’

Symptom 

The user executes a Desktop flow containing a ‘Launch Edge’ or ‘Launch Chrome’ or ‘Launch Firefox’ action and the execution fails with error message ‘Failed to assume control of Microsoft Edge (Internal error or communication failure).’ or ‘Failed to assume control of Chrome (Internal error or communication failure).’ or ‘Failed to assume control of Firefox (Internal error or communication failure).’ respectively. 

Cause 

This error can be generated at least for one of the below cases: 

  • Case 1: Edge/Chrome/Firefox web extension is not installed properly or enabled.

  • Case 2: Launch of the Browser is taking longer than the default timeout of the action – 30 seconds – the automation is trying to assume control of the browser before opening and as a result the Launch browser action is failing.

Verifying issue 

Case 1 

  • Execution of a Desktop flow with one of the respective actions fails with this error message.

  • Web Recorder initiation for the specific browser generates the below messagealternate text

  • Please note that the Web extension might seem to be installed and enabled in the extension repository of the specific Browser but the execution to be unsuccessful.

Case 2 

  • Execution of a Desktop flow with one of the respective actions fails with this error message. This behavior might not be consistent (some executions could be successful).

Resolution 

Case 1 

  • Install the respective Web extension from the Power Automate Desktop designer.alternate text

  • Even if the extension seems installed and enabled, please remove it and reinstall it.

  • Restart the browser.

Case 2 

  • Insert a new ‘Launch new browser’ action as

    • Launch new Edge

    • Launch new Chrome

    • Launch new Firefox

    • Launch new Internet Explorer

  • Parameters of the action:

    • Launch mode: Launch new Instance

    • Initial URL: A default URL

    • Rest parameters can be set as desired. alternate text

  • Insert an error handling policy by:

    • Click ‘On error’ option in the action windowalternate text

    • Click on ‘Continue flow run’ and select ‘Go to next action’ in the dropdown list

    • Click on ‘Save’ alternate text

  • Insert a new ‘Launch new browser’ action of the same browser as Step 1

    • Parameters of the action:

      • Launch mode: Attach to running instance

      • Attach to browser tab: By URL

      • Tab URL: The URL inserted in Step 1

      • Variables produced: Replace the new Browser to variable to the name of the variable produced by step 1    alternate text

  • Click on ‘On error’ option

    • Enable option ‘Retry action if an error occurs’ alternate text

    • Set the number of time to 20 by clicking on the number of times

    • Set the interval in seconds to 5 by clicking on the number of seconds

    • Click on ‘Save’

  • Insert a ‘Go to Web page’ action

    • Parameters of the action:

      • Web browser instance: The variable produced by ‘Launch new browser’ action

      • Navigate: To URL

      • URL: The URL you would like to navigate to alternate text

Finally, please find some general checks that you may apply in case the above actions do not fix the error:

  • Make sure that the environmental variable "ComSpec" with value "C:\WINDOWS\system32\cmd.exe" exists on the machine.

  • Only for Chrome: Check and set the "exit_type" parameter to "normal" at %localappdata%\Google\Chrome\User Data\Default\Preferences

  • Clear the cache and cookies from the browser manually and restart the browser.

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

Thank you for your feedback!

Thank you for your feedback! It sounds like it might be helpful to connect you to one of our Office support agents.

×